On Tuesday October 20, gmsoft@xxxxxxxxxxxx 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@xxxxxxx> 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 > > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
