linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Tobias McNulty <tobias@caktusgroup.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: reshape failure
Date: Thu, 17 Feb 2011 07:32:47 +1100	[thread overview]
Message-ID: <20110217073247.2dbc9299@notabene.brown> (raw)
In-Reply-To: <AANLkTikniCc3NNxgf9tW8Gb4qvUM-UfCJDazYC6Th1jZ@mail.gmail.com>

On Wed, 16 Feb 2011 10:46:32 -0500 Tobias McNulty <tobias@caktusgroup.com>
wrote:

> Hi,
> 
> I tried to start a reshape over the weekend (RAID6 -> RAID5) and was
> dismayed to see that it was going to take roughly 2 weeks to complete:
> 
> md0 : active raid6 sdc[0] sdh[5](S) sdg[4] sdf[3] sde[2] sdd[1]
> 5860543488 blocks super 0.91 level 6, 64k chunk, algorithm 2 [5/5]
> [uuuuu] [>....................] reshape = 0.0% (245760/1953514496)
> finish=21189.7min speed=1536K/sec
> 
> The disk that contained the backup file began experiencing SATA errors
> several days into the reshape, due to what turned out to be a faulty
> SATA card.  The card has since been replaced and the RAID1 device that
> contains the backup file successfully resync'ed.
> 
> However, when I try to re-start the reshape now, I get the following error:
> 
> nas:~# mdadm --assemble /dev/md0 --backup-file=md0.backup /dev/sdc
> /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh
> mdadm: Failed to restore critical section for reshape, sorry.
> 
> Is my data lost for good?  Is there anything else I can do?

Try above command with --verbose.
If a message about "too-old timestamp" appears, run

 export MDADM_GROW_ALLOW_OLD=1

and run the command again.

In either case, post the output.

NeilBrown

  reply	other threads:[~2011-02-16 20:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 15:46 reshape failure Tobias McNulty
2011-02-16 20:32 ` NeilBrown [this message]
2011-02-16 20:41   ` Tobias McNulty
2011-02-16 21:06     ` NeilBrown
2011-02-17 21:39       ` Tobias McNulty
2011-05-11 18:06         ` Tobias McNulty
2011-05-11 21:12           ` NeilBrown
2011-05-11 21:19             ` Tobias McNulty
     [not found]             ` <BANLkTi=3-PgTqeGqyu5fPZMporA1vk6-Tw@mail.gmail.com>
2011-05-11 21:34               ` NeilBrown
2011-05-12  0:46                 ` Tobias McNulty
  -- strict thread matches above, loose matches on Subject: below --
2023-09-03 21:39 Reshape Failure Jason Moss
2023-09-04  1:41 ` Yu Kuai
2023-09-04 16:38   ` Jason Moss
2023-09-05  1:07     ` Yu Kuai
2023-09-06 14:05       ` Jason Moss
2023-09-07  1:38         ` Yu Kuai
2023-09-07  5:44           ` Jason Moss
     [not found]             ` <79aa3cf3-78d4-cfc6-8d3b-eb8704ffaba1@huaweicloud.com>
2023-09-07  6:19               ` Jason Moss
2023-09-10  2:45                 ` Yu Kuai
2023-09-10  4:58                   ` Jason Moss
2023-09-10  6:10                     ` Yu Kuai

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=20110217073247.2dbc9299@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=tobias@caktusgroup.com \
    /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).