linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Jan Kasprzak <kas@fi.muni.cz>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID-10 explicitly defined drive pairs?
Date: Mon, 12 Dec 2011 15:33:02 +0000	[thread overview]
Message-ID: <4EE61EAE.20101@anonymous.org.uk> (raw)
In-Reply-To: <20111212115459.GC20730@fi.muni.cz>

On 12/12/2011 11:54, Jan Kasprzak wrote:
> 	Hello, Linux RAID gurus,
>
> I have a new server with two identical external disk shelves (22 drives each),
> which will be connected to the server with a pair of SAS cables.
> I want to use RAID-10 on these disks, but I want it to be configured
> so that the data will always be mirrored between the shelves.
> I.e. I want to be able to overcome complete failure of a single shelf.
>
> 	Is there any way how to tell mdadm explicitly how to set up
> the pairs of mirrored drives inside a RAID-10 volume?

If you're using RAID10,n2 (the default layout) then adjacent pairs of 
drives in the create command will be mirrors, so your command line 
should be something like:

# mdadm --create /dev/mdX -l10 -pn2 -n44 /dev/shelf1drive1 
/dev/shelf2drive1 /dev/shelf1drive2 ...

Having said that, if you think there's a real chance of a shelf failing, 
you probably ought to think about adding more redundancy within the 
shelves so that you can survive another drive failure or two while 
you're running on just one shelf.

If you are sticking with RAID10, you can potentially get double the read 
performance using the far layout - -pf2 - and with the same order of 
drives you can still survive a shelf failure, though your use of port 
multipliers may well limit your performance anyway.

Hope this helps!

Cheers,

John.


  reply	other threads:[~2011-12-12 15:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 11:54 RAID-10 explicitly defined drive pairs? Jan Kasprzak
2011-12-12 15:33 ` John Robinson [this message]
2012-01-06 15:08   ` Jan Kasprzak
2012-01-06 16:39     ` Peter Grandi
2012-01-06 19:16       ` Stan Hoeppner
2012-01-06 20:11       ` Jan Kasprzak
2012-01-06 22:55         ` Stan Hoeppner
2012-01-07 14:25           ` Peter Grandi
2012-01-07 16:25             ` Stan Hoeppner
2012-01-09 13:46               ` Peter Grandi
2012-01-10  3:54                 ` Stan Hoeppner
2012-01-10  4:13                   ` NeilBrown
2012-01-10 16:25                     ` Stan Hoeppner
2012-01-12 11:58                   ` Peter Grandi
2012-01-12 12:47               ` Peter Grandi
2012-01-12 21:24                 ` Stan Hoeppner
2012-01-06 20:55     ` NeilBrown
2012-01-06 21:02       ` Jan Kasprzak
2012-03-22 10:01       ` Alexander Lyakas
2012-03-22 10:31         ` NeilBrown
2012-03-25  9:30           ` Alexander Lyakas
2012-04-04 16:56             ` Alexander Lyakas
2014-06-09 14:26               ` Alexander Lyakas
2014-06-10  0:11                 ` NeilBrown
2014-06-11 16:05                   ` Alexander Lyakas

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=4EE61EAE.20101@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=kas@fi.muni.cz \
    --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).