All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid10 physical layout?
Date: Fri, 24 May 2013 15:13:41 -0400	[thread overview]
Message-ID: <519FBBE5.7050802@turmel.org> (raw)
In-Reply-To: <20130524184930.GA9609@septictank.raw-sewage.fake>

On 05/24/2013 02:49 PM, Matt Garman wrote:
> 
> I'm looking into building a six-disk raid10.  The six disks are
> comprised of three from one manufacturer, and three from another.

> But based on what I've been reading, looks like mdadm's more
> sophisticated raid10 layout schemes give better performance.  For
> example, can I create a raid10,f2 set in such a way as to meet my
> "redundant copies on different manufacturer" criteria?

Just alternate the manufacturers when you list the devices in the
"--create" operation.  MD lays out raid10,f2 redundant data on adjacent
disks.  (Wraps around.)

Phil

  reply	other threads:[~2013-05-24 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 18:49 raid10 physical layout? Matt Garman
2013-05-24 19:13 ` Phil Turmel [this message]
2013-05-25 13:31   ` Roy Sigurd Karlsbakk

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=519FBBE5.7050802@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=matthew.garman@gmail.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 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.