From: Bryon Roche <kain@kain.org>
To: linux-raid@vger.kernel.org
Subject: Re: differnet UUIDs and no of spares :(
Date: Wed, 21 Jan 2009 18:04:08 +0000 (UTC) [thread overview]
Message-ID: <gl7o2n$6et$2@ger.gmane.org> (raw)
In-Reply-To: 35147.127.0.0.1.1232535970.squirrel@localhost
On Wed, 21 Jan 2009 11:06:10 +0000, eamonn wrote:
> I don't suppose anybody else has any ideas? I've been holding off
> attempting anything in the hope of somebody handing me a silver bullet,
> but failing that ... ;)
No silver bullets. your best chance is to use the logs like you mention
to do a forced read-only assemble. For this reason, it's also usually a
good idea to save the arguments you used for mdadm --create somewhere,
especially if you made the array with a non-default layout. At least
this will let you stream the data of the array onto something else.
A forced assembly necessarily destroys the superblock and any metadata
that could be used to resume the build. Your best bet here will be to
make sure you got the device order correct, probably in accordance to the
oldest list. This assumes that you didn't start rebuilding onto any
disks in such a way as to change that order.
prev parent reply other threads:[~2009-01-21 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 17:26 differnet UUIDs and no of spares :( Eamonn Hamilton
2009-01-14 22:50 ` Bill Davidsen
2009-01-14 23:15 ` Eamonn Hamilton
2009-01-21 11:06 ` eamonn
2009-01-21 18:04 ` Bryon Roche [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='gl7o2n$6et$2@ger.gmane.org' \
--to=kain@kain.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).