From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: james harvey <jamespharvey20@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: N-Way (traditional) RAID-1 development status
Date: Tue, 20 Oct 2015 08:45:29 -0400 [thread overview]
Message-ID: <56263769.3030903@gmail.com> (raw)
In-Reply-To: <CA+X5Wn7C-0O5TRn6fpBFdst6=-cJ2zdn0RPQD3n97MR7NrZxsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On 2015-10-19 23:13, james harvey wrote:
> Wanted to see if there's active development on N-Way (traditional) RAID-1.
>
> By this, I mean that RAID-1 across "n" disks traditionally means "n"
> copies of data, but btrfs currently implements RAID-1 as "2" copies of
> data. So, unlike traditional RAID-1, losing 2 drives in a many drive
> array might cause data loss. It's been mentioned before that N-Way
> (traditional) RAID-1 should eventually be implemented through btrfs.
Before I go any further, I would like to point out that most traditional
hardware RAID controllers only support two disks for RAID-1
configurations, and the only one I've seen that doesn't does RAID-1 like
BTRFS (two copies total of each block). The whole 'RAID-1 on n disks is
n copies' thing actually started with Linux's MD-RAID subsystem, and
just happens to have been popular enough that other software RAID
implementations adopted those semantics as well.
OK, with that historical rant out of the way, back to your actual
question: Based on what has been said in the past, N-way replication is
planned for development after the raid56 code is considered stable.
Based on that and past experience, I'd say to expect it no sooner than
4.8, or if we're _really_ lucky, 4.7. On top of that, based on past
experience with BTRFS\, I would not suggest actually trying it for
anything other than testing until at least one release after the initial
release.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-10-20 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 3:13 N-Way (traditional) RAID-1 development status james harvey
2015-10-20 12:45 ` Austin S Hemmelgarn [this message]
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=56263769.3030903@gmail.com \
--to=ahferroin7@gmail.com \
--cc=jamespharvey20@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.