From: Neil Brown <neilb@suse.de>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 to raid 6 reshape failure after reboot
Date: Thu, 22 Oct 2009 10:44:53 +1100 [thread overview]
Message-ID: <19167.40181.250468.925659@notabene.brown> (raw)
In-Reply-To: message from Guy Martin on Tuesday October 20
On Tuesday October 20, gmsoft@tuxicoman.be wrote:
>
> Hi Neil,
>
> Here is the output I've got :
>
> bleh mdadm # ./mdadm --assemble /dev/md0 /dev/sd[bdef]1 --backup-file
> backup -v mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 0.
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 3.
> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> mdadm:/dev/md0 has an active reshape - checking if critical section
> needs to be restored mdadm: too-old timestamp on backup-metadata on
> backup mdadm: Failed to find backup of critical section
Ahhh... I wondered a bit about that as I was adding the fprintf there,
but it was along the lines of "this cannot happen", not "this is where
the bug might be" :-)
I see now what is happening. I need to update the mtime every time I
write the backup metadata (of course!). I never tripped on this
because I never let a reshape run for more than a few minutes.
I have checked in a patch which updated the mtime properly, so it
should now word for you.
Thanks for helping make mdadm even better!
NeilBrown
> mdadm: Failed to restore critical section for reshape, sorry.
>
> The backup file is of course the one I've been using for the grow
> command.
>
> The values I've got :
> - info->array.utime : 1256026602
> - bsb.mtime : 1256020033
>
> My timezone is Europe/Brussels if that matters.
>
> Removing this check makes the reshape continue and the array start
> correctly.
>
> Let me know if you want me to do some more tests.
>
> HTH,
> Guy
>
>
> On Tue, 20 Oct 2009 16:54:43 +1100
> "NeilBrown" <neilb@suse.de> wrote:
>
> > I tried to reproduce this and failed - it works perfectly for me.
> >
> > I have added some more tracing messages to --assemble which are
> > enabled by --verbose.
> > Could you please pull the latest devel-3.1 branch from my git tree and
> > try the same assemble command but with --verbose at the end and
> > report the result.
> >
> > Thanks.
> > NeilBrown
> >
next prev parent reply other threads:[~2009-10-21 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 16:10 Raid 5 to raid 6 reshape failure after reboot Guy Martin
2009-10-18 20:14 ` NeilBrown
2009-10-19 13:53 ` Guy Martin
2009-10-19 20:05 ` NeilBrown
2009-10-20 5:54 ` NeilBrown
2009-10-20 8:37 ` Guy Martin
2009-10-21 23:44 ` Neil Brown [this message]
2009-10-22 9:29 ` Guy Martin
2009-10-29 4:55 ` Neil Brown
2009-10-22 14:20 ` Guy Martin
2009-10-29 3:32 ` 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=19167.40181.250468.925659@notabene.brown \
--to=neilb@suse.de \
--cc=gmsoft@tuxicoman.be \
--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).