On 2015-11-20 06:39, Dmitry Katsubo wrote:
Actually, I really like this idea, one of the questions I get asked when I show people BTRFS is the difference between System and Metadata, and it's not always easy to explain to somebody who doesn't have a background in filesystem development. For some reason, people seem to have trouble with the concept that the system tree is an index of the other trees. In general, it doesn't make sense for most non-debugging cases to have it listed separate from the Metadata (they always have the same profile unless you're part way through a conversion, and it really is metadata, just slightly higher level than the usual metadata chunks).If I may add:Information for "System" System, DUP: total=32.00MiB, used=16.00KiB is also quite technical, as for end user system = metadata (one can call it "filesystem metadata" perhaps). For simplicity the numbers can be added to "Metadata" thus eliminating that line as well. For those power users who really want to see the tiny details like "System" and "GlobalReserve" I suggest to implement "-v" flag: # btrfs fi usage -v
On 2015-11-19 03:16, Duncan wrote:Qu Wenruo posted on Thu, 19 Nov 2015 08:42:13 +0800 as excerpted:Although the metadata output is showing that you still have about 512M available, but the 512M is Global Reserved space, or the unknown one.Unknown here, as the userspace (btrfs-progs) is evidently too old to show it as global reserve, as it does in newer versions...The output is really a little confusing. I'd like the change the output by adding global reserved into metadata used space and make it a sub item for metadata.Thanks for the clarification. It's most helpful, here. =:^) I've at times wondered if global reserve folded into one of the other settings. Apparently it comes from the metadata allocation, but while metadata is normally dup (single-device btrfs) or raid1 (multi-device), global reserve is single. It would have been nice if that sort of substructure was described a bit better when global reserve first made its appearance, at least in the patch descriptions and release announcement, if not then yet in btrfs fi df output, first implementations being what they are. But regardless, now at least it should be clear for list regulars who read this thread anyway, since the above reasonably clarifies things. As for btrfs fi df, making global reserve a metadata subentry there would be one way to deal with it, preserving the exposure of the additional data provided by that line (here, the fact that global reserve is actually being used, underlining the fact that the filesystem is severely short on space). Another way of handling it would be to simply add the global reserve into the metadata used figure before printing it, eliminating the separate global reserve line, and changing the upthread posted metadata line from 8.48 GiB of 9 GiB used, to 8.98 of 9 GiB used, which is effectively the case if the 512 MiB of global reserve indeed comes from the metadata allocation. This would more clearly show how full metadata actually is without the added complexity of an additional global reserve line, but would lose the fact that global reserve is actually in use, that the broken out global reserve line exposes. I'd actually argue in favor of the latter, directly folding global reserve allocation into metadata used, since it'd both be simpler, and more consistent if for instance btrfs fi usage didn't report separate global reserve in the overall stats, but fail to report it in the per- device stats and in btrfs dev usage. Either way would make much clearer that metadata is actually running out than the current report layout does, since "metadata used" would then either explicitly or implicitly include the global reserve.
smime.p7s
Description: S/MIME Cryptographic Signature
