From: Maxwell Bottiger <sleepylight@jive-turkey.net>
To: linux-raid@vger.kernel.org
Subject: recovery of software raid0 - continued
Date: 16 Jun 2002 20:47:33 -0400 [thread overview]
Message-ID: <1024274853.2688.13.camel@jive-turkey.net> (raw)
The attempt to recover my missing raid arrays continues...
I have 3 arrays. md0 is composed of sdd1 and sde1, md1 is composed of
sdd2 and sde2 and md2 is composed of sdd3 and sde3. md0 is mounted
under /usr, md1 _should_ be mounted under /home and md2 _should_ mounted
/mnt/shared.
The problem I have right now is that md1 says that it is composed of
sdd2 and sde2, however it is not the right size. The same is true of
md2. It looks like the data and size of the two arrays have been
reversed, even though they say the are composed of the right physical
partitions. Everything on /home looks fine, but /mnt/shared is empty
save the lost+found directory.
My questions are, first, what is wrong with the RAID mapping, and
second, is it possible that my data in /mnt/shared (aka md2) is still in
place?
reply other threads:[~2002-06-17 0:47 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=1024274853.2688.13.camel@jive-turkey.net \
--to=sleepylight@jive-turkey.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.