From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Possible project idea
Date: Thu, 5 Nov 2015 11:29:18 -0500 [thread overview]
Message-ID: <563B83DE.7070002@gmail.com> (raw)
[-- 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 --]
reply other threads:[~2015-11-05 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563B83DE.7070002@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).