From: Phil Turmel <philip@turmel.org>
To: plug bert <plugbert@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about RAID10 near and far layouts
Date: Mon, 11 Jun 2012 08:28:22 -0400 [thread overview]
Message-ID: <4FD5E466.4050409@turmel.org> (raw)
In-Reply-To: <1339377964.38410.YahooMailClassic@web190004.mail.sg3.yahoo.com>
On 06/10/2012 09:26 PM, plug bert wrote:
> hi peeps,
>
> i've been reading through
>
> http://en.wikipedia.org/wiki/Non-standard_RAID_levels
>
> and just wanted to verify if my understanding is correct.
>
> Is "near" safer than "far"?
>
> e.g. given 4 drives in RAID10 array, n2:
>
> 4 drives
>
> 1 2 3 4
> --------------
> A1 A1 A2 A2
> A3 A3 A4 A4
> A5 A5 A6 A6
> A7 A7 A8 A8
>
> you'd lose the array if either 1&2 or 3&4 goes down at the same time.
>
>
> With 4 drives in RAID10 array, f2:
>
> 4 drives
> 1 2 3 4
> --------------------
> A1 A2 A3 A4
> A5 A6 A7 A8
> A9 A10 A11 A12
> .. .. .. ..
> A4 A1 A2 A3
> A8 A5 A6 A7
> A12 A9 A10 A11
>
> ...there seems to be a lot more combinations that can result in a trashed array(1&2, 2&3, 3&4).
>
> Is my analysis correct? Inputs are more than welcome, tia
I think wikipedia might have this layout wrong. I was under the
impression that a four-disk far2 layout would be:
> 1 2 3 4
> --------------------
> A1 A2 A3 A4
> A5 A6 A7 A8
> A9 A10 A11 A12
> .. .. .. ..
> A2 A1 A4 A3
> A6 A5 A8 A7
> A10 A9 A12 A11
I haven't checked the code, though.
Phil
next prev parent reply other threads:[~2012-06-11 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 1:26 question about RAID10 near and far layouts plug bert
2012-06-11 12:28 ` Phil Turmel [this message]
2012-06-13 4:55 ` metadata versions: 0.90 vs 1.2 plug bert
2012-06-13 5:46 ` Mikael Abrahamsson
2012-06-13 14:46 ` Emmanuel Noobadmin
2012-06-13 15:17 ` Phil Turmel
2012-06-13 17:29 ` Emmanuel Noobadmin
2012-06-13 9:31 ` David Brown
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=4FD5E466.4050409@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=plugbert@yahoo.com \
/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