From: Martin Steigerwald <ms@teamix.de>
To: linux-btrfs@vger.kernel.org
Subject: Can BTRFS use Forward Correction Codes?
Date: Tue, 27 Aug 2013 15:20:15 +0200 (CEST) [thread overview]
Message-ID: <1865492918.2145268.1377609615453.JavaMail.zimbra@teamix.de> (raw)
In-Reply-To: <1242390564.2145156.1377608853484.JavaMail.zimbra@teamix.de>
Hi!
I just read
http://www.amplidata.com/pdf/The-RAID-Catastrophe.pdf
According to that – well marketing white paper – it offers huge advantages over just replicating the data several times.
What do you think about it?
Can BTRFS use Forward Correction Codes to allow scenarios like 4 out of 12 drives can fail? And can this provide an advantage over regular replication?
Ciao,
--
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
parent reply other threads:[~2013-08-27 13:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1242390564.2145156.1377608853484.JavaMail.zimbra@teamix.de>]
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=1865492918.2145268.1377609615453.JavaMail.zimbra@teamix.de \
--to=ms@teamix.de \
--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).