From: Phil Turmel <philip@turmel.org>
To: Mike Hartman <mike@hartmanipulation.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID showing all devices as spares after partial unplug
Date: Sun, 18 Sep 2011 09:23:40 -0400 [thread overview]
Message-ID: <4E75F0DC.3010206@turmel.org> (raw)
In-Reply-To: <CAB=7dh=xshrAfZzSaekPL0kJe0M2mKbOaupaFyeWVC6SnkT6=g@mail.gmail.com>
Hi Mike,
On 09/17/2011 11:59 PM, Mike Hartman wrote:
> On Sat, Sep 17, 2011 at 11:07 PM, Mike Hartman
> <mike@hartmanipulation.com> wrote:
>> Yikes. That's a pretty terrifying prospect.
*Don't do it!*
"mdadm --create" in these situations is an absolute last resort.
First, try --assemble --force.
If needed, check the archives for the environment variable setting that'll temporarily allow mdadm to ignore the event counts for more --assemble and --assemble --force tries.
(I can't remember the variable name off the top of my head.)
Only if all of the above fails do you fall back to "--create", and every single "--create" attempt *must* include "--assume-clean", or your data is in grave danger.
Based on the output of the one full mdadm -E report, your array was created with a recent version mdadm, so you shouldn't have trouble with data offsets. Please post the full "mdadm -E" report for each drive if you want help putting together a --create command.
I'd also like to see the output of lsdrv[1], so there's a good record of drive serial numbers vs. device names.
HTH,
Phil
[1] http://github.com/pturmel/lsdrv
next prev parent reply other threads:[~2011-09-18 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB=7dhk0AV1dKL2cngt1eZXJwCVrfixfLE5z=J1i-7tqdL-6QA@mail.gmail.com>
2011-09-17 20:39 ` RAID showing all devices as spares after partial unplug Mike Hartman
2011-09-17 22:16 ` Mike Hartman
[not found] ` <CAB=7dhmFQ=Rtagj2j_22cnoS0A2yoKvJgaTM+ZiqDBqhPRooDQ@mail.g mail.com>
2011-09-18 1:16 ` Jim Schatzman
2011-09-18 1:34 ` Mike Hartman
[not found] ` <CAB=7dh=PymkpqRLTWiNzD-+n=XwEWnPN8nQwXg1=UmiJmZ1b1w@mail.g mail.com>
2011-09-18 2:57 ` Jim Schatzman
2011-09-18 3:07 ` Mike Hartman
[not found] ` <CAB=7dh=9UcEWJjLbOvPLu1Ubij0X4i6+SQ-6L9VE5gHLvcJVcw@mail.gmail.com>
2011-09-18 3:59 ` Mike Hartman
2011-09-18 13:23 ` Phil Turmel [this message]
2011-09-18 16:07 ` Mike Hartman
2011-09-18 16:18 ` Phil Turmel
[not found] ` <20110920010054.8DFFE581F7A@mail.futurelabusa.com>
2011-09-20 4:33 ` Phil Turmel
2011-09-18 23: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=4E75F0DC.3010206@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mike@hartmanipulation.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).