3 ms·
By the time future-bcachefs has feature parity with present-btrfs, who knows what more will be in future-btrfs? For your specific example, bcachefs's erasure c
by bhaney 3y ago
By the time future-bcachefs has feature parity with present-btrfs, who knows what more will be in future-btrfs?
For your specific example, bcachefs's erasure coding is very experimental and currently pretty much unusable, while btrfs is actively working towards fixing the raid56 write hole with the recent addition of the raid-stripe-tree. By the time bcachefs has a trustworthy parity profile, btrfs's may be just as good.
- curt15 3y agoBcachefs has not advertised erasure coding as production ready only to renege on that claim later. So nobody has been unwittingly burned yet.
- throw0101d 3y ago> For your specific example My specific example says that the bcachefs are "actively working towards fixing the raid56 write hole" as well—or rather, their way of doing things doesn't have one in the first place.
- bhaney 3y ago> bcachefs are "actively working towards fixing the raid56 write hole" as well Yep, that's my point. Neither btrfs nor bcachefs have a write-hole-less parity raid profile implementation yet, and both are working towards one. We don't know if one will be finished and battle tested significantly before the other, or if one will prove to be more performant or reliable. Just have to wait and see.