Hacker News new | ask | show | jobs
by rdtsc 3398 days ago
> it doesn't really make sense at all that 'btrfs developers say it's not ready'. This just doesn't square.

Just looked at this page: https://btrfs.wiki.kernel.org/index.php/Status and I can see how they would interpret that as "not ready". There a good number of "mostly OK" ones, one is unstable. With comments like "write hole still exists, parity not checksummed", "auto-repair and compression may crash ", and others.

It might be good enough for some but I can see many customers of Redhat would not want to trust their crown jewels to anything that stays "mostly OK".
2 comments
newman314 3398 days ago
"mostly OK" and storage should not ever mix.

That's like the ¯\_(ツ)_/¯ of storing things. Scary.

link
rdtsc 3397 days ago
Exactly! You phrased it better than me. Storage of customers' data and "mostly ok" should be very far from each other.
link
cmurf 3398 days ago
None of those are default configurations that you'd get with mkfs. And there is no UI in any installer to enable raid56.
link