From: Mike Hardy <mhardy@h3c.com>
To: Bruno Seoane <stickman@ole.com>, linux-raid@vger.kernel.org
Subject: Re: raid5 disaster
Date: Tue, 23 May 2006 14:07:24 -0700 [thread overview]
Message-ID: <4473798C.2060208@h3c.com> (raw)
In-Reply-To: <200605232245.27660.stickman@ole.com>
Bruno Seoane wrote:
> mdadm -C -l5 -n5
> -c=128 /dev/md0 /dev/sdb1 /dev/sdd1 /dev/sde1 /dev/sdc1 /dev/sda1
>
> I took the devices order from the mdadm output on a working device. Is this
> the way it's supposed to be the command assembled?
>
> Is there anything alse I should consider or any other valid solution to gain
> access to my data?
If you create the array, it will immediately start resyncing unless you
list one of the devices in your command line as "missing". Just pick one
(ideally one of the ones that isn't getting picked up anyway) and put
'missing' in its place.
Using "missing" is the only way to have it be read-only in the data
regions. That'll let you make a mistake and still be able to recover
data after you find the right command line.
-Mike
prev parent reply other threads:[~2006-05-23 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 20:45 raid5 disaster Bruno Seoane
2006-05-23 21:07 ` Mike Hardy [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=4473798C.2060208@h3c.com \
--to=mhardy@h3c.com \
--cc=linux-raid@vger.kernel.org \
--cc=stickman@ole.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).