Revert to using df to get free space for btrfs pools


Recommended Posts

I believe it was used before but due to unreliable values it stopped being used, on newer kernels it should work reliably, and better than current method for some situations.

 

There are frequent posts on the forum from users using two different size devices in a pool, because free space is incorrectly reported and they run out of it, e.g. a pool made of 32GB + 64GB devices default raid1

 

image.png.9dfa28d1e5a8ed679eb217a1b2ee7f40.png

 

Usable space will be around 32GB, GUI reports 47GB, df reports correctly:

image.png.1fc7c137b3a7a59bd1290789fff8e494.png

 

Also starting with even newer kernels, like the one on v6.9-beta1 is started correctly reporting free space for raid5/6 profiles, pool made of four 64GB devices using raid6

 

image.png.1dfa9d2afbc8ba911c8e50908a978c91.png

 

With df:

image.png.3427b2aba1989e611683fb04fcb822d4.png

 

Please change this for v6.9, with multiple pools it will likely affect more users.

 

  • Thanks 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.