linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: jahammonds prost <gmitch64@yahoo.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Failed Array Rebuild advice Please
Date: Wed, 11 Apr 2012 14:43:02 +1000	[thread overview]
Message-ID: <20120411144302.35f13f3d@notabene.brown> (raw)
In-Reply-To: <1334117647.68845.YahooMailNeo@web125505.mail.ne1.yahoo.com>

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

On Tue, 10 Apr 2012 21:14:07 -0700 (PDT) jahammonds prost
<gmitch64@yahoo.com> wrote:

> One other question as the badblocks progresses.
>  
> >  It will then recovery both devices in parallel.
> 
> How many additional devices can be done at the same time? I presume that I am going to have to replace the 2 failed devices before I try and grow the array by adding 3 additional drives? I so, how many additional drives can be rebuilt concurrently with a grow? Could I add 5 devices and not see too much of a performance hit? Or would it be more sensible to add them one at a time?
> 

I think it is best to recover, and then reshape later.  I cannot promise that
doing them both at once will work .... it might but I have a feeling that
there might be problems.

Adding three additional drives at once should work well enough in terms of
performance.
However I would only do it if I were very very confident of the drives.
If you hit bad blocks you start losing drives, and if you have 3 drives that
you haven't used before, the chance of losing them all during the reshape -
while still small - becomes a little too high for comfort.

But if you have run heavy bad-blocks tests on them all and they appear to
work, then adding 3 drives at once should be fine.

NeilBrown

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

  reply	other threads:[~2012-04-11  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 22:32 Failed Array Rebuild advice Please jahammonds prost
2012-04-10 23:02 ` NeilBrown
2012-04-10 23:46   ` jahammonds prost
2012-04-11  4:14   ` jahammonds prost
2012-04-11  4:43     ` NeilBrown [this message]
2012-04-12  2:10       ` jahammonds prost
2012-04-12  2:25         ` NeilBrown

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=20120411144302.35f13f3d@notabene.brown \
    --to=neilb@suse.de \
    --cc=gmitch64@yahoo.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).