From: NeilBrown <neilb@suse.de>
To: "C.J. Adams-Collier KF7BMP" <cjac@colliertech.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Re-assembling faulty array
Date: Tue, 15 May 2012 10:09:31 +1000 [thread overview]
Message-ID: <20120515100931.15d12053@notabene.brown> (raw)
In-Reply-To: <1336765276.10557.30.camel@foxtrot.cjac.ntr.f5net.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Fri, 11 May 2012 12:41:16 -0700 "C.J. Adams-Collier KF7BMP"
<cjac@colliertech.org> wrote:
> Hey all,
>
> I've got an array that seems to have failed while I was re-synchronizing
> one of the disks. sde fell out when I moved six disks from one chassis
> to another. I re-added it and it was 98.8% done with 300 minutes left
> in the process when I went to sleep last night. When I woke up, the
> array was in a FAILED state, sdg was marked failed and sde was marked
> spare. I removed sdg from the array and re-booted and now the array
> won't start.
>
> Is there a way to re-add sdg back in to slot 5 rather than having it
> added as a spare? AFAICT, no writes have been made to sdg or md0 since
> I removed it from the array, so it should be pretty close to its active
> state. sde must be nearly ready to be added in as an active participant
> in the array, too.
>
> Is there anything I can do to re-build the array at this point?
>
>
Maybe. However I cannot quite intuit the state of the arrays from your
description.
Could you report the output of "mdadm -E" on each member device please?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-15 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 19:41 Re-assembling faulty array C.J. Adams-Collier KF7BMP
2012-05-15 0:09 ` NeilBrown [this message]
2012-05-15 22:59 ` NeilBrown
2012-05-16 5:16 ` C.J. Adams-Collier
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=20120515100931.15d12053@notabene.brown \
--to=neilb@suse.de \
--cc=cjac@colliertech.org \
--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).