Revisiting How We Put Together Linux Systems

Re:Revisiting How We Put Together Linux Systems by rdtsc on Saturday March 04, 2017 @12:26AM (#13789451)

> 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".

[ Parent | on HN ]

Re:Revisiting How We Put Together Linux Systems by newman314 on Saturday March 04, 2017 @12:59AM (#13789544)

"mostly OK" and storage should not ever mix.

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

[ Parent | on HN ]

Re:Revisiting How We Put Together Linux Systems by rdtsc on Sunday March 05, 2017 @01:17AM (#13794842)

Exactly! You phrased it better than me. Storage of customers' data and "mostly ok" should be very far from each other.

[ Parent | on HN ]

Re:Revisiting How We Put Together Linux Systems by cmurf on Saturday March 04, 2017 @02:25AM (#13789800)

None of those are default configurations that you'd get with mkfs. And there is no UI in any installer to enable raid56.

[ Parent | on HN ]