From: John Robinson <john.robinson@anonymous.org.uk>
To: Mike Myers <mikesm559@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Need urgent help in fixing raid5 array
Date: Sat, 03 Jan 2009 16:14:25 +0000 [thread overview]
Message-ID: <495F8EE1.3030007@anonymous.org.uk> (raw)
In-Reply-To: <432505.65026.qm@web30805.mail.mud.yahoo.com>
On 03/01/2009 15:49, Mike Myers wrote:
> Ugh. This would explain a lot! i'll try this out and see if it can help get md1 back online.
Good luck; the rest of that thread's probably worth a read before
starting in too, just to see whether you need to mention your two dirty
members first or last.
As Guy suggested earlier in this thread, you might try doing your
reassemble while missing out the one with the apparently completely
hosed superblock, to at least get the thing up in degraded mode, then
test fsck it (e.g. `e2fsck -n`) and mount it read-only to see if you've
still got any data. And perhaps take a backup then.
> Is the only way to regenerate a superblock on a member doing a a create with the assume-clean option?
I'm not sure, but I expect so. Seconding what Justin said much earlier
in this thread, personally I'd wait until one of the gurus arrives, in
their shining armour and on their white charger, before trying this.
Cheers,
John.
next prev parent reply other threads:[~2009-01-03 16:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <451872.61166.qm@web30802.mail.mud.yahoo.com>
2009-01-01 15:40 ` Need urgent help in fixing raid5 array Justin Piszcz
2009-01-01 17:51 ` Mike Myers
2009-01-01 18:29 ` Justin Piszcz
2009-01-01 18:40 ` Jon Nelson
2009-01-01 20:38 ` Mike Myers
2009-01-02 6:19 ` Mike Myers
2009-01-02 12:10 ` Justin Piszcz
2009-01-02 18:12 ` Mike Myers
2009-01-02 18:22 ` Justin Piszcz
2009-01-02 18:46 ` Mike Myers
2009-01-02 18:57 ` Justin Piszcz
2009-01-02 20:46 ` Mike Myers
2009-01-02 20:56 ` Mike Myers
2009-01-02 21:37 ` Mike Myers
2009-01-03 4:19 ` Mike Myers
2009-01-03 4:43 ` Guy Watkins
2009-01-03 5:02 ` Mike Myers
2009-01-03 12:46 ` John Robinson
2009-01-03 15:49 ` Mike Myers
2009-01-03 16:14 ` John Robinson [this message]
2009-01-03 16:47 ` Mike Myers
2009-01-03 19:03 ` Mike Myers
2009-01-05 22:11 ` Neil Brown
2009-01-05 22:22 ` Mike Myers
2009-01-05 22:53 ` NeilBrown
2009-01-06 2:46 ` Mike Myers
2009-01-06 4:00 ` NeilBrown
2009-01-06 5:55 ` Mike Myers
2009-01-06 23:23 ` Neil Brown
2009-01-06 6:24 ` Mike Myers
2009-01-06 23:31 ` Neil Brown
2009-01-06 23:54 ` Mike Myers
2009-01-07 0:19 ` NeilBrown
2009-01-13 5:38 ` Mike Myers
2009-01-13 5:57 ` Mike Myers
2009-01-01 15:31 Mike Myers
-- strict thread matches above, loose matches on Subject: below --
2008-12-05 17:03 Mike Myers
2008-12-06 0:18 ` Mike Myers
2008-12-06 0:24 ` Justin Piszcz
2008-12-06 0:47 ` Mike Myers
2008-12-06 0:51 ` Justin Piszcz
2008-12-06 0:58 ` Mike Myers
2008-12-06 19:02 ` Mike Myers
2008-12-06 19:30 ` Mike Myers
2008-12-06 20:14 ` Mike Myers
2008-12-06 0:52 ` David Lethe
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=495F8EE1.3030007@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mikesm559@yahoo.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).