[guenthert]

Hmmh, under "Why bcachefs?" we find

- Stability but also

- Constant refactorings

and later

"Disclaimer, my personal data is stored on ZFS"

A bit troubling, I find

"RAID0 behavior is default when using multiple disks" never have I ever had the need for RAID0 or have I seen a customer using it. I think it was at one time popular with gamers before SSDs became popular and cheap.

"RAID 5/6 (experimental)

    This is referred to as erasure coding and is listed as “DO NOT USE YET”, "

Well, you got to start somewhere, but a comparison with btrfs and ZFS seems premature.

[nextaccountic]

> "Disclaimer, my personal data is stored on ZFS"

> A bit troubling, I find

I appreciated the candor

The approach of bcachefs developers is that they will only recommend it's usage if it's absolutely, 100% stable and won't eat your data. Bcachefs isn't in that state yet and the developers don't pretend it is.

This avoids the kind of trust issues that btrfs has

[GrayShade]

Does it? From the btrfs docs:

> The RAID56 feature provides striping and parity over several devices, same as the traditional RAID5/6. There are some implementation and design deficiencies that make it unreliable for some corner cases and the feature should not be used in production, only for evaluation or testing. The power failure safety for metadata with RAID56 is not 100%.