From: mike.czajka@utoronto.ca
To: linux-lvm@redhat.com
Subject: [linux-lvm] FS recovery from lost vg, pv data
Date: Mon, 23 Aug 2004 16:50:44 -0400 [thread overview]
Message-ID: <1093294244.412a58a4dbdc9@webmail.utoronto.ca> (raw)
Hello;
I have a (probably common and detested) LVM1 recovery question: how can i get
the data off my /dev/hda3 (LVM partition) which previously housed a VG and a few
LVs whose metadata is now lost, having done a 'pvcreate -ff /dev/hda3' and a
'vgcreate vg /dev/hda3'? The actual data is in a few reiserfs3 partitions of
unknown sizes (unknown number of LVs, approximately 4).
I removed my /dev/hdb PV using vgreduce, after attempting a pvmove (but it
seemed that it wasn't used). After a reboot I couldn't mount my root LV (it was
a very bad idea to make a root lv), and after booting using a bootCD vgscan
exited with 'error pv_read_pe can't get data of volume group from physical
volume' (roughly). So this is when I tried 'pvcreate -ff' and created a new vg.
However, I cannot guess at the LV information.
Any help would be greatly appreciated.
Thanks,
-Mike
reply other threads:[~2004-08-23 20:51 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=1093294244.412a58a4dbdc9@webmail.utoronto.ca \
--to=mike.czajka@utoronto.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox