Hi again, Le 21/12/2019 à 13:00, Qu Wenruo a écrit :
A known regression introduced in v5.4. The new metadata over-commit behavior conflicts with an existing check in btrfs_statfs(). It is completely a runtime false behavior, and had*no* other bad effect.
I'm painfully unable to understand how the same said « metadata over-commit » would allow, on my system, “df” to work properly on some filesystems and fail miserably on others.
AND show “100% full” filesystems with still more than 600 GB free... That would make quite much of an overcommit isn't it ?
So I wonder if there isn't something else or if the “overcommit” calculation is not really completely broke in the first place...
ॐ -- Swâmi Petaramesh <swami@xxxxxxxxxxxxxx> PGP 9076E32E
