From: NeilBrown <neilb@suse.de>
To: NeilBrown <neilb@suse.de>
Cc: Richard Herd <2001oddity@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Please Help! RAID5 -> 6 reshapre gone bad
Date: Tue, 7 Feb 2012 14:10:23 +1100 [thread overview]
Message-ID: <20120207141023.22cce706@notabene.brown> (raw)
In-Reply-To: <20120207133947.5c4b9a59@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
On Tue, 7 Feb 2012 13:39:47 +1100 NeilBrown <neilb@suse.de> wrote:
> > I tried to assembe the array, to see if it would continue the reshape:
> >
> > root@raven:/# mdadm -Avv --backup-file=/usb/md0.backup /dev/md0
> > /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sdf1 /dev/sdg1
> >
> > Unfortunately mdadm had decided that the backup-file was out of date
> > (timestamps didn't match) and was erroring with: Failed to restore
> > critical section for reshape, sorry..
> >
> > Chances are things were in such a mess that backup file wasn't going
> > to be used anyway, so I blocked the timestamp check with: export
> > MDADM_GROW_ALLOW_OLD=1
> >
> > That allowed me to assemble the array, but not run it as there were
> > not enough disks to start it.
>
> You probably just need to add "--force" to the assemble line.
> So stop the array (mdamd -S /dev/md0) and assemble again with --force as well
> as the other options.... or maybe don't.
>
> I just tested that and I didn't do what it should. I've hacked the code a
> bit and can see what the problem is and think I can fix it.
>
> So leave it a bit. I'll let you know when you should grab my latest code
> and try that.
Ok, that should work..
If you:
git clone git://neil.brown.name/mdadm
cd mdadm
make
export MDADM_GROW_ALLOW_OLD=1
./mdadm -Avv --backup-file=/usb/md0.backup /dev/md0 ..list.of.devices.. --force
it should restart the grow. Once device will be left failed. If you think
it is usable then when the grow completes you can add it back in.
If you get another failure it will die again and you'll have to restart it.
If you get a persistent failure, you might be out of luck.
Please let me know how it goes.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-07 3:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 1:34 Please Help! RAID5 -> 6 reshapre gone bad Richard Herd
2012-02-07 2:15 ` Phil Turmel
[not found] ` <CAOANJV955ZdLexRTjVkQzTMapAaMitq5eqxP0rUvDjjLh4Wgzw@mail.gmail.com>
2012-02-07 2:57 ` Phil Turmel
2012-02-07 3:10 ` Richard Herd
2012-02-07 3:24 ` Keith Keller
2012-02-07 3:38 ` Phil Turmel
2012-01-31 6:31 ` rebuild raid6 after two failures Keith Keller
2012-02-01 4:42 ` Keith Keller
2012-02-01 5:31 ` NeilBrown
2012-02-01 5:48 ` Keith Keller
2012-02-03 16:08 ` using dd (or dd_rescue) to salvage array Keith Keller
2012-02-04 18:01 ` Stefan /*St0fF*/ Hübner
2012-02-05 19:10 ` Keith Keller
2012-02-06 21:37 ` Stefan *St0fF* Huebner
2012-02-07 3:44 ` Keith Keller
2012-02-07 4:24 ` Keith Keller
2012-02-07 20:01 ` Stefan *St0fF* Huebner
2012-02-08 7:13 ` Please Help! RAID5 -> 6 reshapre gone bad Stan Hoeppner
2012-02-07 3:04 ` Fwd: " Richard Herd
2012-02-07 2:39 ` NeilBrown
2012-02-07 3:10 ` NeilBrown [this message]
2012-02-07 3:19 ` Richard Herd
2012-02-07 3:39 ` NeilBrown
2012-02-07 3:50 ` Richard Herd
2012-02-07 4:25 ` NeilBrown
2012-02-07 5:02 ` Richard Herd
2012-02-07 5:16 ` 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=20120207141023.22cce706@notabene.brown \
--to=neilb@suse.de \
--cc=2001oddity@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).