Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID grow and disk failure
Date: Fri, 25 Jun 2010 07:57:51 +1000	[thread overview]
Message-ID: <20100625075751.4429f224@notabene.brown> (raw)
In-Reply-To: <20100624181213.GB9038@lazy.lzy>

On Thu, 24 Jun 2010 20:12:13 +0200
Piergiorgio Sartor <piergiorgio.sartor@nexgo.de> wrote:

> Hi all,
> 
> I was wondering, let's say a RAID-6 has an HDD
> added and a grow is performed.
> 
> What will happen if one of the HDD of the RAID,
> possibly the newly added, will faili, i.e. die?
> 
> Will the RAID continue the grow using all the
> available parity or it will result in a
> catastrophic failure for the array?

Assuming the code doesn't have any bugs, the reshape will stop, then
immediately restart picking up where it left off.
You will of course end up with a degraded array.

I have tested this so I think the code is fine.
It is fairly easy to set up a free smallish /dev/loop devices and experiment
yourself.  Not only will this give you confidence that it works, but it will
also give you familiarity with with the mdadm commands so there will be less
room for surprises once you do it for-real.

It might be nice in these circumstances to abort the reshape and revert back
the the previous number of devices - particularly if it was the new device
that failed.  However that currently isn't supported.

> 
> As side question, assuming the above RAID volume
> is a PV (LVM physical volume), what would be the
> correct procedure to grow it and extend the PV:
> 
> 1)
> mdadm --grow ...
> mdadm --wait
> pvresize

Yes.

> 
> 2)
> mdadm --grow
> pvresize

No.
Until the reshape has completed, the extra space is not available.

NeilBrown


> 
> Thanks,
> 
> bye,
> 


  reply	other threads:[~2010-06-24 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 18:12 RAID grow and disk failure Piergiorgio Sartor
2010-06-24 21:57 ` Neil Brown [this message]
2010-06-26 13:12   ` Piergiorgio Sartor
2010-06-28 23:49     ` Neil Brown

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=20100625075751.4429f224@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    /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