Hans van Kranenburg posted on Tue, 21 Jun 2016 02:25:20 +0200 as excerpted:
> On 06/21/2016 01:30 AM, Marc Grondin wrote: >> >> I have a btrfs filesystem ontop of a 4x1tb mdraid raid5 array and I've >> been getting confusing output on metadata usage. Seems that even tho >> both data and metadata are in single profile metadata is reporting >> double the space(as if it was in dupe profile) > > I guess that's a coincidence. Yes. > From the total amount of space you have (on top of the mdraid), there's > 3 GiB allocated/reserved for use as metadata. Inside that 3 GiB, 1.53GiB > of actual metadata is present. > >>[...] >> Metadata,single: Size:3.00GiB, Used:1.53GiB >> /dev/mapper/storage2 3.00GiB > >> Metadata, single: total=3.00GiB, used=1.53GiB [Explaining a bit more than HvK or ST did.] Btrfs does two-stage allocation. First it allocates chunks, separately for data vs. metadata. Then it uses the space in those chunks, until it needs to allocate more. It's simply coincidence that the actual used metadata space within the allocation happens to be approximately half of the allocated metadata chunk space. Tho unlike data, metadata space should never get completely full -- it'll need to to allocate a new chunk before it reports full, because the global reserve space (which is always zero usage unless the filesystem is in severe straits, if you ever see global reserve usage above zero you know the filesystem is in serious trouble, space-wise) comes from metadata as well. So in reality, you have 3 gigs of metadata chunks allocated, 1.53 gigs of it used for actual metadata, and half a gig (512 MiB) reserved as global- reserve (none of which is used =:^), so in actuality, approximately 2.03 GiB of the 3.00 GiB of metadata chunks are used, with 0.97 GiB of metadata free. Now metadata chunks are nominally 256 MiB (quarter GiB) each, while data chunks are nominally 1 GiB each. However, that's just the _nominal_ size. On TB-scale filesystems they may be larger. In any case, you could balance the metadata and possibly reclaim a bit of space, but with usage including the reserve slightly over 2 GiB, you could only get down to 2.25 GiB metadata allocation best-case, and may be stuck with 2.5 or even the same 3 GiB, depending on actual metadata chunk size. But I'd not worry about it yet. Once unallocated space gets down to about half a TB, or either data or metadata size becomes multiple times actual usage, a balance will arguably be useful. But the numbers look pretty healthy ATM. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
