From: Wols Lists <antlists@youngman.org.uk>
To: Another Sillyname <anothersname@googlemail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID6 Array crash during reshape.....now will not re-assemble.
Date: Wed, 2 Mar 2016 13:20:03 +0000 [thread overview]
Message-ID: <56D6E883.50801@youngman.org.uk> (raw)
In-Reply-To: <CAOS+5GEd4E2wzYhw0rPdrZnjK6UwAUdKCQLLTxXrdPO8d7hS7w@mail.gmail.com>
On 02/03/16 03:46, Another Sillyname wrote:
> Any help and guidance would be appreciated, the drives showing clean
> gives me comfort that the data is likely intact and complete (crossed
> fingers) however I can't re-assemble the array as I keep getting the
> 'critical information for reshape, sorry' warning.
>
> Help???
Someone else will chip in what to do, but this doesn't seem alarming at
all. Reshapes stuck at zero is a recent bug, but all the data is
probably safe and sound.
Wait for one of the experts to chip in what to do, but you might find
mdadm --resume --invalid-backup will get it going again.
Otherwise it's likely to be an "upgrade your kernel and mdadm" job ...
Cheers,
Wol
next prev parent reply other threads:[~2016-03-02 13:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 3:46 RAID6 Array crash during reshape.....now will not re-assemble Another Sillyname
2016-03-02 13:20 ` Wols Lists [this message]
[not found] ` <CAOS+5GHof=F94x58SKqFojV26hGpDSLF85dFfm8Xc6M43sN6jA@mail.gmail.com>
2016-03-02 13:42 ` Fwd: " Another Sillyname
2016-03-02 15:59 ` Another Sillyname
2016-03-03 11:37 ` Another Sillyname
2016-03-03 12:56 ` Wols Lists
[not found] ` <CAOS+5GH1Rcu8zGk1dQ+aSNmVzjo=irH65KfPuq1ZGruzqX_=vg@mail.gmail.com>
2016-03-03 14:07 ` Fwd: " Another Sillyname
2016-03-03 17:48 ` Sarah Newman
2016-03-03 17:59 ` Another Sillyname
2016-03-03 20:47 ` John Stoffel
2016-03-03 22:19 ` Another Sillyname
2016-03-03 22:42 ` John Stoffel
2016-03-04 19:01 ` Another Sillyname
2016-03-04 19:11 ` Alireza Haghdoost
2016-03-04 20:30 ` Another Sillyname
2016-03-04 21:02 ` Alireza Haghdoost
2016-03-04 21:52 ` Another Sillyname
2016-03-04 22:07 ` John Stoffel
2016-03-05 10:28 ` Another Sillyname
2016-03-05 10:47 ` Andreas Klauer
2016-03-09 0:23 ` NeilBrown
2016-03-12 11:38 ` Another Sillyname
2016-03-14 1:08 ` NeilBrown
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=56D6E883.50801@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=anothersname@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.