From: Roman Mamedov <rm@romanrm.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID1 3+ drives
Date: Sat, 28 Jun 2014 16:13:47 +0600 [thread overview]
Message-ID: <20140628161347.2097d308@natsu> (raw)
In-Reply-To: <pan$b64f$b234655e$f16fd679$34acdd2f@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Sat, 28 Jun 2014 04:26:43 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> Russell Coker posted on Sat, 28 Jun 2014 10:51:00 +1000 as excerpted:
>
> > On Fri, 27 Jun 2014 20:30:32 Zack Coffey wrote:
> >> Can I get more protection by using more than 2 drives?
> >>
> >> I had an onboard RAID a few years back that would let me use RAID1
> >> across up to 4 drives.
> >>
> > Currently the only RAID level that fully works in BTRFS is RAID-1 with
> > data on 2 disks.
>
> Not /quite/ correct. Raid0 works, but of course that isn't exactly
> "RAID" as it's not "redundant". And raid10 works. But that's simply
> raid0 over raid1. So depending on whether you consider raid0 actually
> "RAID" or not, which in turn depends on how strict you are with the
> "redundant" part, there is or is not more than btrfs raid1 working.
Also depending on what you consider "fully works", RAID1 may not qualify too,
as neither the read-balancing, nor write-submission algorithms are ready for
production use, performance-wise.
(RAID1 writes to two disks sequentially, not at the same time; and reads are
satisfied from in effect a random device, not from the least-busy device).
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-06-28 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 0:30 RAID1 3+ drives Zack Coffey
2014-06-28 0:51 ` Russell Coker
2014-06-28 4:26 ` Duncan
2014-06-28 6:28 ` Russell Coker
2014-06-28 7:38 ` Martin Steigerwald
2014-06-28 7:43 ` Hugo Mills
2014-06-28 11:38 ` Duncan
2014-06-28 13:40 ` Russell Coker
2014-06-28 18:15 ` Chris Murphy
2014-06-28 10:13 ` Roman Mamedov [this message]
2014-06-29 2:30 ` Duncan
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=20140628161347.2097d308@natsu \
--to=rm@romanrm.net \
--cc=1i5t5.duncan@cox.net \
--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.