Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @steph@fedi.steph.tools
mia@mia@movsw.0x0.st (2026-10-11 18:40:49)
@steph @sanek @sun btrfs end user documentation is bad, the tools are bad, disaster recovery is horrible and largely undocumented (the devs will basically tell you to never use the repair option)

in your case it sounds like metadata space exhaustion and one way to fix that is to temporarily add more disk space (can be on RAM if nothing else is available) and then rebalance.

the first-gen jolla phone shipped with btrfs and that was a bad idea (old kernel and limited space). mine eventually got into a state where i could no longer even remove files to free up space and none of the tools could do anything about it, and back then there was no documentation on how to deal with this so it took me a couple hours to figure it out

i’ve always treated btrfs with suspicion because it was an enormous amount of code written in a very short time and there was just no way it didn’t have glaring bugs and design flaws

basically btrfs is what i imagine would happen if someone tried to vibecode a zfs clone
---Reply---
Blurry Moon@sun@shitposter.world (2026-10-11 20:37:49)
@mia @steph @sanek btrfs raid is shit too