From: "aboster" <aboster@at-sd.com>
To: linux-raid@vger.kernel.org
Subject: Raid 10 reassembly issue
Date: Fri, 23 Jul 2004 14:07:03 -0700 [thread overview]
Message-ID: <000201c470f9$03e51950$cd03a8c0@archnet2.atgsd.com> (raw)
Running vanilla Red Hat 9, I assembled a raid 10, a stripe whose two
components were themselves raid 1's, and did a silly thing.
The raid1 components were md8 and md9. Since md7 was free, I stupidly
assigned that to be the raid0 concatenation of md8 and md9.
The system happily worked for quite sometime. Now we've rebooted.
It appears to me (of course, I could be wrong about this) that what has
happened is that when it got to md7 during the boot process where it's
assembling the raids, md7's components were not started yet, so it has
removed md7 from the configuration.
As far as I know, the components (md8 and 9) have not been touched.
I need to reassemble the raid0, preferably with a different device number
(md20, say), without destroying the filesystem that I think might still be
intact (if the stripe were gently reassembled).
Can anyone take a minute to help?
Thanks!
Alex
reply other threads:[~2004-07-23 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000201c470f9$03e51950$cd03a8c0@archnet2.atgsd.com' \
--to=aboster@at-sd.com \
--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).