* Possible project idea
@ 2015-11-05 16:29 Austin S Hemmelgarn
0 siblings, 0 replies; only message in thread
From: Austin S Hemmelgarn @ 2015-11-05 16:29 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
I'd been looking at the wiki page with project ideas, and I realized
that there were no listed ideas that suggested the adding support for
arbitrary erasure coding methods. Ceph for example has an option that
allows you to set arbitrary erasure coding such that you use n devices
to store the data, and can tolerate loss of any m devices out of it.
Technically, this would be covered as a special case by the whole
copies/stripes/parity thing that was discussed a while back before
raid56 code made it into the kernel (I've tried to find the thread for
reference, but haven't been unable to locate it), but I didn't see that
'project' listed anywhere on the page either.
IMHO, this would be an excellent feature to differentiate BTRFS from
bcachefs and ZFS (although I would not be surprised if they both copied
it themselves).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-11-05 16:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-05 16:29 Possible project idea Austin S Hemmelgarn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).