koverstreet / bcachefs

Other
633 stars 69 forks source link

QUESTION: Erasure coding status? #657

Closed TurkeyMan closed 4 months ago

TurkeyMan commented 4 months ago

Sorry to post a question to the issue tracker.

Where are we at with erasure coding? I'm upgrading a media server, which is a large storage pool of relatively low importance data. I want to move away from ZFS since it's so inflexible, and I want tiered access. Is bcachefs ready to try out, or still too early? I have 6x 16tb drives to start with, intending to use 2 parity in a raid-6 style configuration, and the intention is to expand it progressively. I'll also add an SSD as a promote target.

If something goes catastrophically wrong, the data isn't particularly sensitive. Should I try this?

nrdxp commented 4 months ago

I noticed that, even with erasure coding turned on, that parity was always listed as 0 with bcachefs fs usage, and I found the CONFIG_BCACHEFS_ERASURE_CODING kernel config option which is not set, so I assume it is disabled at the kernel level by default, and given the warning at the cli level: --erasure_code Enable erasure coding (DO NOT USE YET), I'd assume it's not ready for production yet (as of 6.8 kernel at least).

koverstreet commented 4 months ago

yeah. Code wise it's close, but I am swamped with other things, it needs thorough testing and I can't handle the additional debugging load right now