From: NeilBrown <neilb@suse.de>
To: Jan Kasprzak <kas@fi.muni.cz>
Cc: linux-raid <linux-raid@vger.kernel.org>,
John Robinson <john.robinson@anonymous.org.uk>
Subject: Re: RAID-10 explicitly defined drive pairs?
Date: Sat, 7 Jan 2012 07:55:26 +1100 [thread overview]
Message-ID: <20120107075526.59ed433c@notabene.brown> (raw)
In-Reply-To: <20120106150823.GX25976@fi.muni.cz>
[-- Attachment #1: Type: text/plain, Size: 2619 bytes --]
On Fri, 6 Jan 2012 16:08:23 +0100 Jan Kasprzak <kas@fi.muni.cz> wrote:
> John Robinson wrote:
> : On 12/12/2011 11:54, Jan Kasprzak wrote:
> : > 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 ...
>
> OK, this works, thanks!
>
> : 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.
>
> I am aware of that. I don't think the whole shelf will fail,
> but who knows :-)
>
> : 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.
>
> On the older hardware I have a majority of writes, so the far
> layout is probably not good for me (reads can be cached pretty well
> at the OS level).
>
> After some experiments with my new hardware, I have discovered
> one more serious problem: I have simulated an enclosure failure,
> so half of the disks forming the RAID-10 volume disappeared.
> After removing them using mdadm --remove, and adding them back,
> iostat reports that they are resynced one disk a time, not all
> just-added disks in parallel.
>
> Is there any way of adding more than one disk to the degraded
> RAID-10 volume, and get the volume restored as fast as the hardware permits?
> Otherwise, it would be better for us to discard RAID-10 altogether,
> and use several independent RAID-1 volumes joined together using LVM
> (which we will probably use on top of the RAID-10 volume anyway).
>
> I have tried mdadm --add /dev/mdN /dev/sd.. /dev/sd.. /dev/sd..,
> but it behaves the same way as issuing mdadm --add one drive at a time.
I would expect that to first recover just the first device added, then
recover all the rest at once.
If you:
echo frozen > /sys/block/mdN/md/sync_action
mdadm --add /dev/mdN /dev......
echo recover > /sys/block/mdN/md/sync_action
it should do them all at once.
I should teach mdadm about this..
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-01-06 20:55 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
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 [this message]
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=20120107075526.59ed433c@notabene.brown \
--to=neilb@suse.de \
--cc=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).