From: Jean Jordaan <jean@upfrontsystems.co.za>
To: linux-raid@vger.kernel.org
Subject: Re: Recovering RAID5 array
Date: Tue, 20 Jan 2004 09:17:51 +0200 [thread overview]
Message-ID: <400CD61F.9010502@upfrontsystems.co.za> (raw)
In-Reply-To: <16396.53737.911347.812076@notabene.cse.unsw.edu.au>
Hi Neil
Thanks for the answer!
> mdadm --detail /dev/md0
> didn't tell you??
It probably tried, but I was too rattled to parse all the
lun/target/part stuff at that point .. :(
> mdadm --assemble /dev/md0 --force /dev/hd[abc]3
OK, I'll try it on the copy, and if that doesn't work on
the original data, since it isn't really an option to
send the originals for recovery ..
--
Jean Jordaan
http://www.upfrontsystems.co.za
next prev parent reply other threads:[~2004-01-20 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 6:54 Recovering RAID5 array Jean Jordaan
2004-01-20 6:59 ` Neil Brown
2004-01-20 7:17 ` Jean Jordaan [this message]
2004-01-20 8:08 ` Jean Jordaan
2004-01-20 9:59 ` Neil Brown
2004-01-20 10:40 ` Jean Jordaan
2004-01-20 12:10 ` Maarten v d Berg
2004-01-20 12:23 ` Jean Jordaan
2004-01-20 12:57 ` Maarten v d Berg
2004-01-20 13:28 ` Jean Jordaan
2004-01-20 10:44 ` Jean Jordaan
2004-01-20 7:22 ` Guy
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=400CD61F.9010502@upfrontsystems.co.za \
--to=jean@upfrontsystems.co.za \
--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).