From: NeilBrown <neilb@suse.com>
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: Mon, 14 Mar 2016 12:08:06 +1100 [thread overview]
Message-ID: <87r3fdx3wp.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAOS+5GEu0xku0bjf=SAbx8=bkjn33wLg-1c1YK4DK5fOs_QhTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
On Sat, Mar 12 2016, Another Sillyname wrote:
> Neil
>
> Thanks for the insight, much appreciated.
>
> I've tried what you suggested and still get stuck.
>
>>:losetup /dev/loop0 /tmp/foo/sdb1
>>:losetup /dev/loop1 /tmp/foo/sdc1
>>:losetup /dev/loop2 /tmp/foo/sdd1
>>:losetup /dev/loop3 /tmp/foo/sde1
>>:losetup /dev/loop4 /tmp/foo/sdf1
>>:losetup /dev/loop5 /tmp/foo/sdg1
>>:losetup /dev/loop6 /tmp/foo/sdh1
>
>
>>:mdadm --assemble --force --update=revert-reshape --invalid-backup /dev/md127 /dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6
> mdadm: /dev/md127: Need a backup file to complete reshape of this array.
> mdadm: Please provided one with "--backup-file=..."
> mdadm: (Don't specify --update=revert-reshape again, that part succeeded.)
>
> As you can see it 'seems' to have accepted the revert command, but
> even though I've told it the backup is invalid it's still insisting on
> the backup being made available.
>
> Any further thoughts or insights would be gratefully received.
Try giving it a backup file too.
It doesn't matter what the contents of the file are because you have
told it the file is invalid. But I guess it thinks it might still need
a file to write new backups to temporarily.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-03-14 1:08 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
2016-03-09 0:23 ` NeilBrown
2016-03-12 11:38 ` Another Sillyname
2016-03-14 1:08 ` NeilBrown [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=87r3fdx3wp.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--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).