4 ms·
At least disk management is far easier with btrfs. You can restripe at will while zfs has severe limitations around resizing, adding and removing devices. Gran
by the8472 7y ago
At least disk management is far easier with btrfs. You can restripe at will while zfs has severe limitations around resizing, adding and removing devices.
Granted, at enterprise scale this hardly matters because you can just send-receive to rebuild pools if you have enough spares, but for consumer-grade deployments it's a non-negligible annoyance.
- HorstG 7y agoActually, this matters a lot in many enterprises. Beancounters hate excess capacities, so there are never enough spares and everything is always almost full. Maybe SV is different...
- p_l 7y agoRestriping is source of unsafety, though. A lot of ZFS data safety comes from the fact it doesn't support overwriting anything, making it so that normal operation can't introduce unrecoverable corruption. In fact, all writes are done through snapshots.
- the8472 7y agoZFS wanted to have that too (the mythical block pointer rewrite) but it never happend, instead they add clunky workarounds like indirection tables for.
- p_l 7y agoIt was treated more like "ok, yet another person complaining about it - here's what you need to implement, and why you won't". The indirection tables are survivable for fixing short term mistakes, though.