From: NeilBrown <neilb@suse.de>
To: Sam Clark <sclark_77@hotmail.com>
Cc: Phil Turmel <philip@turmel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID5 - Disk failed during re-shape
Date: Mon, 13 Aug 2012 09:35:54 +1000 [thread overview]
Message-ID: <20120813093554.600d46c2@notabene.brown> (raw)
In-Reply-To: <BLU401-EAS3343C9BB7296EA68990FF2294B20@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
On Sat, 11 Aug 2012 10:42:01 +0200 Sam Clark <sclark_77@hotmail.com> wrote:
> Thanks for the response Phil.
>
> I was thinking that 'toast' was the case, and have been looking into my backups (not so great, though the critical data is fine).
>
If you've got backups, then that is likely the most reliable solution - sorry.
> I think you are toast, as I saw nothing in the metadata that would give
> you a precise reshape restart position, even if you got Neil to work up
> a custom mdadm that could use it. The 11.4% could be converted into an
> approximate restart position, perhaps.
>
> Neil, is there any way to do some combination of "create
> --assume-clean", start a reshape held at zero, then skip 11.4% ?
The metadata might contain the precise reshape position - but "mdadm
--examine" won't be displaying it.
If you can grab the last 128K of the device (probably using 'dd' with
'skip=xxx' I would be able to check and see.
If you can tell me:
exactly how big the devices are (sectors)
what the chunk size of the array was (probably 64K)
and get me that last 128K of a few devices, then I can provide you a shell
script that will poke around in sysfs and activate the array in read-only
mode which might allow you to mount it and copy out any important data.
After that you would need to re-create the array.
I don't think it is really practical to get the array fully working again
with recreating from scratch once you have all the important data.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-08-12 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 8:38 RAID5 - Disk failed during re-shape Sam Clark
2012-08-10 22:36 ` Phil Turmel
2012-08-11 1:21 ` Dmitrijs Ledkovs
2012-08-11 8:42 ` Sam Clark
2012-08-12 23:35 ` NeilBrown [this message]
[not found] ` <BLU153-ds10943E39726EDC983C484594B00@phx.gbl>
2012-08-14 2:38 ` NeilBrown
2012-08-14 13:40 ` Sam Clark
2012-08-14 21:05 ` NeilBrown
2012-08-15 16:32 ` Sam Clark
2012-08-15 22:38 ` 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=20120813093554.600d46c2@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=sclark_77@hotmail.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).