On 2017-02-09 08:25, Adam Borowski wrote:
On Wed, Feb 08, 2017 at 11:48:04AM +0800, Qu Wenruo wrote:
Just don't believe the vanilla df output for btrfs.
For btrfs, unlike other fs like ext4/xfs, which allocates chunk dynamically
and has different metadata/data profile, we can only get a clear view of the
fs from both chunk level(allocated/unallocated) and extent
level(total/used).
Actually, df lies on ext4 too. sysvfs-derived filesystems have statically
allocated inodes, which means that if you try to store small files, at some
point you'll run out of space despite df claiming you have plenty left.
Which is why the `-i` option for df exists.
That said, not having any more space is not the same as not being able
to create more files, and that's been the case since long before Linux
even existed. Most people don't think about this though because ext4
and most other filesystems that use static inode tables allocate insane
numbers of inodes at mkfs time so it (usually) doesn't ever become an issue.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
