linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Bryan Bush <bbushvt@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 6 rebuild
Date: Fri, 6 Apr 2012 18:28:20 +1000	[thread overview]
Message-ID: <20120406182820.6d734eb3@notabene.brown> (raw)
In-Reply-To: <CAJ72viMGQ-MesqGcXkwxjLH4Bt-4rXU1KT=mAgux5JhjKd0VYg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On Fri, 6 Apr 2012 03:01:26 -0400 Bryan Bush <bbushvt@gmail.com> wrote:

> If you have 2 failed drives in a raid 6 array, will it rebuild them
> both at the same time or in serial?

Maybe.

Probably not, but it can be coaxed to.

The next release of mdadm will contain

http://neil.brown.name/git?p=mdadm;a=commitdiff;h=9f58469128c99c0d7f434d28657f86789334f253

which will ensure that if you:

  mdadm /dev/md0 --add /dev/foo /dev/bar

then both will be added before the recovery starts, so both will be recovered
at the same time.

Alternately you could:

 echo freeze > /sys/block/md0/md/sync_action
 mdadm /dev/md0 --add /dev/foo /dev/bar
 echo idle > /sys/blcok/md0/md/sync_action

you might even be able to leave of the first step.
The "add" will cause a recovery to start on just one device, but then when
you write 'idle', it will abort  the recovery, automatically restart, but
this time will use all available spares.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-04-06  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  7:01 Raid 6 rebuild Bryan Bush
2012-04-06  8:28 ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-11 18:11 Gallas, William N
2014-02-11 18:46 ` Chris Murphy

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=20120406182820.6d734eb3@notabene.brown \
    --to=neilb@suse.de \
    --cc=bbushvt@gmail.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).