From: Colin Faber <cfaber@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Having problems recovering LV
Date: Fri, 23 Jan 2009 11:14:00 -0700 [thread overview]
Message-ID: <497A08E8.7060303@gmail.com> (raw)
Hi,
Re-sending because I'm not sure this ever made it out to the list.
Hoping someone can give me some advise here.
So I managed to recover my raid, now I have what I think is a complete
md0 and md1. However when I pvscan I get different results depending on
whether md0 is online or not.
Here is an example of what I'm referring to:
# pvscan
Warning: Volume Group raid is not consistent
PV /dev/md0 VG raid lvm2 [1.82 TB / 1.82 TB free]
Total: 1 [1.82 TB] / in use: 1 [1.82 TB] / in no VG: 0 [0 ]
that is what I get when I have md0 and m1 enabled. However if I disable md0:
# mdadm -S /dev/md0
mdadm: stopped /dev/md0
# pvscan
Couldn't find device with uuid 'oI1oXp-NOSk-BJn0-ncEN-HaZr-NwSn-P9De9b'.
Couldn't find device with uuid 'oI1oXp-NOSk-BJn0-ncEN-HaZr-NwSn-P9De9b'.
PV unknown device VG raid lvm2 [1.82 TB / 0 free]
PV /dev/md1 VG raid lvm2 [1.36 TB / 0 free]
Total: 2 [3.18 TB] / in use: 2 [3.18 TB] / in no VG: 0 [0 ]
So that said md0 exists (temporarily ) across 3 USB mass storage
devices. After the initial rebuild I suspected that the device order was
mixed up (yeay for random USB device assignments). I verified that this
was in fact the case with the first and last 64k of the array containing
no PV label and the middle one containing the label. I've since
corrected it so the disks are (should be) in the right order again. So I
guess what I'm asking is what I should do next here, my experience with
LVM is limited. Am I hosed here? Is my data recoverable?
-cf
next reply other threads:[~2009-01-23 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 18:14 Colin Faber [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 19:18 [linux-lvm] Having problems recovering LV Colin Faber
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=497A08E8.7060303@gmail.com \
--to=cfaber@gmail.com \
--cc=linux-lvm@redhat.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 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.