From: David Greaves <david@dgreaves.com>
To: Neil Brown <neilb@suse.de>, Kyle Stuart <kstuart@sisna.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Bad drive discovered during raid5 reshape
Date: Tue, 30 Oct 2007 12:35:42 +0000 [thread overview]
Message-ID: <4727251E.5030705@dgreaves.com> (raw)
In-Reply-To: <18215.6378.912706.274201@notabene.brown>
Neil Brown wrote:
> On Tuesday October 30, david@dgreaves.com wrote:
>> 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?
>
> Yes, md can grow to a degraded array. If you get a single failure I
> would expect it to abort the growth process, then restart where it
> left off (after checking that that made sense).
I read that he aborted it, then removed both drives before giving md a chance to
restart.
He said:
After several minutes dmesg indicated that mdadm gave up and
the grow process stopped. After googling around I tried the solutions
that seemed most likely to work, including removing the new drives with
mdadm --remove --force /dev/md1 /dev/sd[bc]1 and rebooting
and *then* he: "ran mdadm -Af /dev/md1."
>> 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)
>
> He only needs one of the two drives in there. I got the impression
> that both sdc and sdb had reported errors. If not, and sdc really
> seems OK, then "--assemble --force" listing all drives except sdb
> should make it all work again.
Kyle - I think you need to clarify this as it may not be too bad. Apologies if I
misread something and sdc is bad too :)
It may be an idea to let us (Neil) know what you've done and if you've done any
writes to any devices before trying this assemble.
David
next prev parent reply other threads:[~2007-10-30 12:35 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
2007-10-30 11:43 ` Neil Brown
2007-10-30 12:35 ` David Greaves [this message]
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=4727251E.5030705@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 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).