Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Andread Mayrhoff <repro@spoilbase.eu>, linux-raid@vger.kernel.org
Subject: Re: Help needed: array inactive after grow attempt
Date: Thu, 28 Apr 2016 23:12:39 +0100	[thread overview]
Message-ID: <57228AD7.1050408@youngman.org.uk> (raw)
In-Reply-To: <7cfbdd22b8c20acdb95fababfa1a04a6@spoilbase.eu>

On 28/04/16 20:50, Andread Mayrhoff wrote:
> I might add
> 
> ~/tmp # mdadm --stop /dev/md127
> mdadm: stopped /dev/md127
> ~/tmp # mdadm --assemble --scan
> mdadm: Failed to restore critical section for reshape, sorry.
>        Possibly you needed to specify the --backup-file
> 
> Thanks for helping me out of this...

Have you got the latest mdadm? See the "stuck reshape operation" thread
for details.

You could also try adding the --invalid-backup option to mdadm. It
shouldn't need a backup if you're adding more disk, though, so that
looks slightly odd to me.

Beyond those tips I'll not stray - my raid-fu is not the best and while
I'm confident of this information I don't believe in encouraging others
to take risks. If those don't work I'll let a better expert than me
chime in.

Cheers,
Wol

  parent reply	other threads:[~2016-04-28 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 19:27 Help needed: array inactive after grow attempt Andread Mayrhoff
2016-04-28 19:50 ` Andread Mayrhoff
2016-04-28 20:02   ` Andread Mayrhoff
2016-05-03 18:47     ` Phil Turmel
2016-04-28 22:12   ` Wols Lists [this message]
2016-04-28 22:43     ` Adam Goryachev
     [not found]     ` <c98c947ff2759669bcb5ccf87c3dd245@spoilbase.eu>
2016-04-28 23:30       ` Wols Lists

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=57228AD7.1050408@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=repro@spoilbase.eu \
    /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