From: William Heaton <acroporas@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm: too-old timestamp on backup-metadata
Date: Tue, 17 Aug 2010 19:23:35 -0400 [thread overview]
Message-ID: <4C6B19F7.3070603@gmail.com> (raw)
In-Reply-To: <20100818090921.71bbabda@notabene>
On 08/17/2010 07:09 PM, Neil Brown wrote:
> On Tue, 17 Aug 2010 16:00:01 -0400
> William Heaton<acroporas@gmail.com> wrote:
>
>
>> *I am not on the mailing list. Please include acroporas@gmail.com in
>> any replies.*
>>
>> I had a 4-disk RAID5. I added a 5th disk and at the same time converted
>> it to RAID6.
>>
>> Things started out looking good, but after about a day, the reshape
>> appeared to have stalled. After waiting more than 24 hours without
>> seeing any progress I rebooted the computer. Immediately before the
>> rebooting the array was running and all data was accessible. But after
>> reboot, the array would not start. Can anyone help me get the array
>> restarted? Thanks
>>
>> ~$ uname -a
>> Linux pholidochromis 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28
>> 05:14:15 UTC 2010 x86_64 GNU/Linux
>>
>> ~$ mdadm --version
>> mdadm - v3.1.2 - 10th March 2010
>>
>>
>> ~$ sudo mdadm --assemble /dev/md0 /dev/sd[bcdel]1 -vv -f --backup-file
>> /media/Backup/rb
>> mdadm: looking for devices for /dev/md0
>> mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 4.
>> mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 2.
>> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 0.
>> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
>> mdadm: /dev/sdl1 is identified as a member of /dev/md0, slot 3.
>> mdadm:/dev/md0 has an active reshape - checking if critical section
>> needs to be restored
>> mdadm: too-old timestamp on backup-metadata on /media/Backup/rb
>> mdadm: Failed to find backup of critical section
>> mdadm: Failed to restore critical section for reshape, sorry.
>>
>>
> cd /tmp
> git clone git://neil.brown.name/mdadm
> make
> sudo ./mdadm --assemble /dev/md0 /dev/sd[bcdel]1 -vv -f --backup-file /media/Backup/rb
>
> If that still doesn't work.
>
> sudo sh
> export MDADM_GROW_ALLOW_OLD=1
> ./mdadm --assemble /dev/md0 /dev/sd[bcdel]1 -vv -f --backup-file /media/Backup/rb
>
> NeilBrown
>
>
$ sudo sh
# export MDADM_GROW_ALLOW_OLD=1
# ./mdadm --assemble /dev/md0 /dev/sd[bcdel]1 -vv -f --backup-file
/media/Backup/rb
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdl1 is identified as a member of /dev/md0, slot 3.
mdadm:/dev/md0 has an active reshape - checking if critical section
needs to be restored
mdadm: accepting backup with timestamp 1281747660 for array with
timestamp 1282072264
mdadm: restoring critical section
mdadm: added /dev/sde1 to /dev/md0 as 1
mdadm: added /dev/sdc1 to /dev/md0 as 2
mdadm: added /dev/sdl1 to /dev/md0 as 3
mdadm: added /dev/sdb1 to /dev/md0 as 4
mdadm: added /dev/sdd1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 4 drives (out of 5).
Looks like that did the trick. Thanks
prev parent reply other threads:[~2010-08-17 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 20:00 mdadm: too-old timestamp on backup-metadata William Heaton
2010-08-17 23:09 ` Neil Brown
2010-08-17 23:23 ` William Heaton [this message]
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=4C6B19F7.3070603@gmail.com \
--to=acroporas@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).