Status update - erasure coding
🕑 Added 2020-10-24 00:58:18 +0000 UTCErasure coding is ready for wider testing!
I just finished reworking disk space accounting for parity blocks - they're broken out from user data now, so bcachefs fs usage will show you that overhead. And I've been fixing bugs; there shouldn't be any gaping holes, and I don't expect it to catch on fire or eat data at this point. But there will definitely bugs and performance issues to find and fix.
That's the main news, aside from a whole bunch of bug fixing. Xfstests runs are looking cleaner and cleaner, and the bug reports I've been getting are less and less serious - things are looking good!
Comments
Yelig-Nar
Thanks
Kent Overstreet
Mount with -o ec or enable it via sysfs, /sys/fs/bcachefs//options/ec
brunoais
Awesome m8! Keep up the great work!
How does one enable erasure coding on an existing or new bcachefs pool? I haven't found any documentation for that (not even in https://wiki.archlinux.org/index.php/Bcachefs). Also - would that allow operations on failing drives (specifically `evacuate` and `remove`)? This is the main issue I have with BTRFS - once a device starts failing, it is not possible to remove it as the remove operation always fail - one has to disconnect the drive and remount the array in degraded mode to have any chance of recovery.