From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Another Sillyname <anothersname@googlemail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID6 Array crash during reshape.....now will not re-assemble.
Date: Sat, 5 Mar 2016 11:47:55 +0100 [thread overview]
Message-ID: <20160305104755.GA3541@EIS> (raw)
In-Reply-To: <CAOS+5GEd4E2wzYhw0rPdrZnjK6UwAUdKCQLLTxXrdPO8d7hS7w@mail.gmail.com>
On Wed, Mar 02, 2016 at 03:46:48AM +0000, Another Sillyname wrote:
> As all the drives are showing Reshape pos'n 0 I'm assuming the reshape
> never got started (even though cat /proc/mdstat showed the array
> reshaping)?
I fixed such a thing by editing RAID metadata to no longer be in
reshape state... incomplete instructions:
https://bpaste.net/show/2231e697431d
The example above used 1.0 superblock I think; in order to adapt this
successfully to your situation you should refer to
https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-1_superblock_format_on-disk_layout
If current mdadm/kernel has a way to get out of this ditch directly of
course that would be so much better...
Apart from that, the other alternative that comes to mind is using
--create but for that to be successful, you have to be sure to get all
variables right (superblock version, data offset, raid level, chunk
size, disk order, ...) and use --assume-clean and/or missing disks
to prevent resyncs and verify the results in read-only mode.
Regards
Andreas
next prev parent reply other threads:[~2016-03-05 10:47 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
[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 [this message]
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=20160305104755.GA3541@EIS \
--to=andreas.klauer@metamorpher.de \
--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 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).