News for hackers. Stuff that matters.
Re:Btrfs Allocator Hints by ghostly_s on Friday July 11, 2025 @01:49PM (#44535100)
Yes, my story with btrfs is quite similar- used it for a couple years, suddenly threw some undocumented error and refused to mount, asked about it on the dev irc channel and was told apparently it was a known issue with no solution, have fun rebuilding from backups. No suggestion that anyone was interested in documenting this issue, let alone fixing it.

These same people are the only ones in the world suggesting btrfs is "basically" stable. I'll never touch this project again with a ten foot pole, afaic it's run by children. I'll trust adults with my data.

Re:Btrfs Allocator Hints by sandreas on Friday July 11, 2025 @02:33PM (#44535531)
Ok, thank you. At least I'm not alone with this. However, I'm not too much into it and would not go as far to say it's not a recommendable project, but boy was I mad it just died without any way to recover ANYTHING :-)
Re:Btrfs Allocator Hints by taskforcegemini on Tuesday July 15, 2025 @11:57AM (#44572505)
probably depends on where the issue is located, but is this not normally the case with encrypted drives?
Re:Btrfs Allocator Hints by sandreas on Friday July 18, 2025 @04:25PM (#44609411)
No. Encrypted drives should be recoverable as long as you have the valid decryption values.

I think it had nothing to do with the encryption layer... the FS layer was the problem.

Re:Btrfs Allocator Hints by amy214 on Friday July 11, 2025 @11:52PM (#44539143)
I ran it on opensuse and it would 100% lock out a core on some sort of crontab tree structure rebalancing (?) .. I mean.. hello? online algorithm? Dynamic rebalancing? scheduled FS restructuring, really? ReiserFS dancing trees from 20 years ago? If thats how they think, "meh, the user just has to deal", no wonder this is how they handle bugs.