From: Neil Brown <neilb@suse.de>
To: Nagilum <nagilum@nagilum.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help RAID5 reshape Oops / backup-file
Date: Fri, 12 Oct 2007 09:51:08 +1000 [thread overview]
Message-ID: <18190.46828.156191.300754@notabene.brown> (raw)
In-Reply-To: message from Nagilum on Thursday October 11
On Thursday October 11, nagilum@nagilum.org wrote:
> Ok, after looking in "Grow.c" I can see that the backup file is
> removed once the critial section has passed:
>
> if (backup_file)
> unlink(backup_file);
>
> printf(Name ": ... critical section passed.\n");
>
> Since I had passed that point I'll try to find out where
> Grow_restart() stumbles. By looking at it I'm not even sure it's able
> to "resume" and not just restart. :-/
>
It isn't a problem that you didn't specify a backup-file.
If you don't, mdadm uses some spare space on one of the new drives.
After the critical section has passed, the backup file isn't needed
any longer.
The problem is that mdadm still wants to find and recover from it.
I throughly tested mdadm restarting from a crash during the critical
section, but it looks like I didn't properly test restarting from a
later crash.
I think if you just change the 'return 1' at the end of Grow_restart
to 'return 0' it should work for you.
I'll try to get this fixed properly (and tested) and release a 2.6.4.
NeilBrown
next prev parent reply other threads:[~2007-10-11 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:25 Help RAID5 reshape Oops / backup-file Nagilum
2007-10-11 23:51 ` Neil Brown [this message]
2007-10-12 6:43 ` Nagilum
2007-10-14 16:55 ` Nagilum
2007-10-14 23:31 ` Neil Brown
2007-10-15 11:55 ` Nagilum
2007-10-15 12:08 ` Nagilum
2007-10-16 1:16 ` Neil Brown
2007-10-16 12:50 ` Nagilum
2007-10-17 13:13 ` Nagilum
-- strict thread matches above, loose matches on Subject: below --
2007-10-09 18:58 Nagilum
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=18190.46828.156191.300754@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=nagilum@nagilum.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