linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Evans <mjevans1983@gmail.com>
To: Andrew Klaassen <clawsoon@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID10 - Ensure mirrors aren't on same JBOD
Date: Mon, 26 Apr 2010 12:58:09 -0700	[thread overview]
Message-ID: <u2r4877c76c1004261258t317657f7radd2d52f2fac3cdf@mail.gmail.com> (raw)
In-Reply-To: <406003.10607.qm@web65416.mail.ac4.yahoo.com>

On Mon, Apr 26, 2010 at 11:57 AM, Andrew Klaassen <clawsoon@yahoo.com> wrote:
> --- On Mon, 4/26/10, Michael Evans <mjevans1983@gmail.com> wrote:
>
>> > --- On Mon, 4/26/10, Michael Evans <mjevans1983@gmail.com>
>> wrote:
>> > However, it doesn't say what happens with a larger
>> > number of drives.  I'm looking for the kind of control I
>> > can get with RAID 1+0, where I can specify which drives are
>> > mirrors of each other.  Is that possible with RAID10?
>>
>> No, not predictably; the only provided guarantee is that
>> the data will
>> /not/ be duplicated on the same block-device (usually
>> drive).  In
>> practice you will quickly be able to determine where a
>> particular
>> version with a given range of input causes data to be
>> stored, but
>> there is no requirement that future versions produce the
>> precise same
>> alignment and offsets.
>
> Ah.  So if I want this level of control, I have to sacrifice the advantages of RAID 10 and go with RAID 1+0.
>
> Good to know.  Thanks.
>
> Andrew
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Or write your own program to generate mdadm headers on uninitialized
devices.  Or if it's just a one time thing, write the headers, stop
the array, make sure it says what you want, and then force a resync
before writing any data.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-26 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2h4877c76c1004261144h1019e9afkf05396996ea77a99@mail.gmail.com>
2010-04-26 18:57 ` RAID10 - Ensure mirrors aren't on same JBOD Andrew Klaassen
2010-04-26 19:58   ` Michael Evans [this message]
2010-04-26 20:20     ` Andrew Klaassen
2010-04-26 21:30       ` Michael Evans
2010-04-27 13:27   ` Keld Simonsen
2010-04-26 16:15 Andrew Klaassen
2010-04-26 18:18 ` Michael Evans
2010-04-26 18:36   ` Andrew Klaassen
2010-04-27 13:44   ` Keld Simonsen

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=u2r4877c76c1004261258t317657f7radd2d52f2fac3cdf@mail.gmail.com \
    --to=mjevans1983@gmail.com \
    --cc=clawsoon@yahoo.com \
    --cc=linux-raid@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).