From: David Greaves <david@dgreaves.com>
To: Neil Brown <neilb@suse.de>
Cc: Kyle Stuart <kstuart@sisna.com>, linux-raid@vger.kernel.org
Subject: Re: Bad drive discovered during raid5 reshape
Date: Tue, 30 Oct 2007 11:17:57 +0000 [thread overview]
Message-ID: <472712E5.10806@dgreaves.com> (raw)
In-Reply-To: <18214.53051.652280.492087@notabene.brown>
Neil Brown wrote:
> On Monday October 29, kstuart@sisna.com wrote:
>> Hi,
>> I bought two new hard drives to expand my raid array today and
>> unfortunately one of them appears to be bad. The problem didn't arise
> Looks like you are in real trouble. Both the drives seem bad in some
> way. If it was just sdc that was failing it would have picked up
> after the "-Af", but when it tried, sdb gave errors.
Humble enquiry.... :)
I'm not sure that's right?
He *removed* sdb and sdc when the failure occurred so sdc would indeed be non-fresh.
The key question I think is: will md continue to grow an array even if it enters
degraded mode during the grow?
ie grow from a 6 drive array to a 7-of-8 degraded array?
Technically I guess it should be able to.
In which case should he be able to re-add /dev/sdc and allow md to retry the
grow? (possibly losing some data due to the sdc staleness)
David
next prev parent reply other threads:[~2007-10-30 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 7:10 Bad drive discovered during raid5 reshape Kyle Stuart
2007-10-30 6:29 ` Neil Brown
2007-10-30 11:17 ` David Greaves [this message]
2007-10-30 11:43 ` Neil Brown
2007-10-30 12:35 ` David Greaves
2007-10-31 0:08 ` Kyle Stuart
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=472712E5.10806@dgreaves.com \
--to=david@dgreaves.com \
--cc=kstuart@sisna.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.