All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Larry Schwerzler <larry@schwerzler.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Raid selection questions (10 vs 6, n2 vs f2) on an 8 drive array
Date: Sat, 19 Feb 2011 14:59:53 +1100	[thread overview]
Message-ID: <20110219145953.24fb31f0@notabene.brown> (raw)
In-Reply-To: <AANLkTi=2xjjuvT3tTs1Y9Qfrn6HxWS3hwzF-Q0ZhPFVM@mail.gmail.com>

On Fri, 18 Feb 2011 12:55:05 -0800 Larry Schwerzler <larry@schwerzler.com>
wrote:

> 2. One problem I'm having with my current setup is the esata cables
> have been knocked loose which effectively drops 4 of my drives. I'd
> really like to be able to survive this type of sudden drive loss. if
> my drives are /dev/sd[abcdefgh] and abcd are on one esata channel
> while efgh are on the other is there what drive order should I create
> the array with? I'd guess /dev/sd[aebfcgdh] would that give me
> survivability if one of my esata channels went dark?

Yes, in md/raid10 the multiple copies are an 'adjacent' devices (in the
sequence given to --create).

Of course, you wouldn't actually use the string  /dev/sd[aebfcgdh]
as that expands matches in alphabetical order.:


$ echo  /dev/sd[aebfcgdh]
/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh

Instead use this:

$ echo /dev/sd{a,e,b,f,c,g,d,h}
/dev/sda /dev/sde /dev/sdb /dev/sdf /dev/sdc /dev/sdg /dev/sdd /dev/sdh

NeilBrown

      parent reply	other threads:[~2011-02-19  3:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 20:55 Raid selection questions (10 vs 6, n2 vs f2) on an 8 drive array Larry Schwerzler
2011-02-18 23:44 ` Stan Hoeppner
2011-02-19  0:54   ` Keld Jørn Simonsen
2011-02-19  1:53     ` Larry Schwerzler
2011-02-19  4:33       ` Stan Hoeppner
2011-02-20  9:57         ` Simon Mcnair
2011-02-19  1:50   ` Larry Schwerzler
2011-02-19  1:12 ` Joe Landman
2011-02-19  1:33   ` Larry Schwerzler
2011-02-19  3:59 ` NeilBrown [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=20110219145953.24fb31f0@notabene.brown \
    --to=neilb@suse.de \
    --cc=larry@schwerzler.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 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.