From: Nicolas Jungers <nicolas@jungers.net>
To: linux-raid <linux-raid@vger.kernel.org>
Cc: "Tor Arne Vestbø" <torarnv@gmail.com>
Subject: Re: RAID5 disk failure during rebuild of spare, any chance of recovery when one of the failed devices is suspected to be intact?
Date: Mon, 16 Aug 2010 08:12:35 +0200 [thread overview]
Message-ID: <4C68D6D3.6070906@jungers.net> (raw)
In-Reply-To: <AANLkTim9gUa95AR1KZcyBp7qM8_PeO1O7Bh99R2P8ON9@mail.gmail.com>
On 08/16/2010 07:54 AM, Tor Arne Vestbø wrote:
> Hey Nicolas!
>
> On Mon, Aug 16, 2010 at 7:29 AM, Nicolas Jungers<nicolas@jungers.net> wrote:
>> I'd try to recreate the array with a copy of the disks
>>
>> do a ddrescue of the 3 good disks and then try a mdadm -C with the exact
>> parameters of the array creation with the same mdadm version (use missing
>> for slot 2). It saved my raid10 array.
>
> You mean you sdc and sde plus either sdb or sdd, depending on which
> one I think is more sane a this point?
I'd try both. Do a ddrescue of the failing one and try that (with copy
of the others) and check what's coming out.
>
> mdadm -E before http://pastebin.com/f46EWXEA vs after
> http://pastebin.com/Kp145Mkx indicates sdb1 is missing a few events,
> dunno if that's too much to be usable at this point?
Did write happen during the reconstruction? You'll lose not only what
was on the write but also everything on the same strip, including
directories. That's a reason to try with a copy of sdd.
> Can the create-process be done "read-only", so that I don't have to
> use extra disks? If I've understood things correctly --create will
> only overwrite the superblocks, not touch the data?
yes, but I'd not do it. And beside, you should not trust the failing
one (sdd).
>
> So I could do:
>
> mdadm -C /dev/md0 /dev/sdb1 /dev/sdc1 misssing /dev/sde1
or even
mdadm -C /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
with copies.
>
> I suppose the 33% restored spare sdf1 won't help any in this situation?
I suppose not.
N.
>
> Tor Arne
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-16 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 18:52 RAID5 disk failure during rebuild of spare, any chance of recovery when one of the failed devices is suspected to be intact? Tor Arne Vestbø
2010-08-15 20:06 ` Tor Arne Vestbø
2010-08-15 22:33 ` Tor Arne Vestbø
2010-08-16 5:29 ` Nicolas Jungers
2010-08-16 5:59 ` Tor Arne Vestbø
[not found] ` <AANLkTim9gUa95AR1KZcyBp7qM8_PeO1O7Bh99R2P8ON9@mail.gmail.com>
2010-08-16 6:12 ` Nicolas Jungers [this message]
2010-08-16 8:43 ` Tim Small
2010-08-16 16:27 ` Tor Arne Vestbø
2010-08-16 16:37 ` Nicolas Jungers
2010-08-16 12:13 ` Tor Arne Vestbø
2010-08-16 5:49 ` Tor Arne Vestbø
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=4C68D6D3.6070906@jungers.net \
--to=nicolas@jungers.net \
--cc=linux-raid@vger.kernel.org \
--cc=torarnv@gmail.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