On Wed, Jan 13, 2010 at 04:46:20PM -0500, Christoph Hellwig wrote: > On Wed, Jan 13, 2010 at 09:29:23AM -0500, Chris Mason wrote: > > This is more than just df being inaccurate, it's a way to find out how > > much space is used by each of the raid modes. We've had a ton of > > feature requests for this, and it really helps identify drives that have > > a ton of free space tied up for data vs metadata. > > Which again is not a fs specific feature. Much better to add a statfs > revision to the core that does this for everone. Is anyone else splitting metadata and raid levels up like btrfs is? As far as I know we're the only snowflake in the kernel working like this. I'm not against a generic revision, but I think btrfs needs to send out significantly more data than the others. > That would also > have the nice side effect that we could actually make it statvfs and > could get rid of the braindamage in glibc's current statvfs wrapper. > -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
