From: Alex Matviychuk <alex@opensolutions.ws>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM metadata recovery
Date: Sun, 08 May 2005 11:51:46 -0700 [thread overview]
Message-ID: <427E5FC2.6070900@opensolutions.ws> (raw)
Hello,
I've been searching the net and this mailing list for quite some time
for a way to recover metadata without having access to any backups. I
completely screwed up and forgot to backup or export my lvm settings
when I reinstalled my operating system. Now I can see my volume group,
but when I try to activate it I get:
Volume group vg00 metadata is inconsistent
Volume group for uuid not found:
fhRVK5ZTwTOdTQpgF8oyAESEj8LYNRJy1P1jjdkNCV1WhYwfv9rxpnExXvNu13T6
0 logical volume(s) in volume group "vg00" now active
If I run pvscan I get:
PV /dev/hda3 VG vg00 lvm2 [128.54 GB / 0 free]
PV /dev/hdd1 VG vg00 lvm2 [74.52 GB / 0 free]
PV /dev/hdb1 VG vg00 lvm2 [186.30 GB / 29.36 GB free]
Total: 3 [389.36 GB] / in use: 3 [389.36 GB] / in no VG: 0 [0 ]
and vgscan returns:
Reading all physical volumes. This may take a while...
Found volume group "vg00" using metadata type lvm2
What are my options if any?
Thanks for your time,
Alex Matviychuk
p.s. Here is some more debug output:
vgdisplay:
--- Volume group ---
VG Name vg00
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 13
VG Access read/write
VG Status resizable
MAX LV 255
Cur LV 1
Open LV 0
Max PV 255
Cur PV 3
Act PV 3
VG Size 389.36 GB
PE Size 4.00 MB
Total PE 99676
Alloc PE / Size 92160 / 360.00 GB
Free PE / Size 7516 / 29.36 GB
VG UUID fhRVK5-ZTwT-OdTQ-pgF8-oyAE-SEj8-LYNRJy
lvdisaply:
--- Logical volume ---
LV Name /dev/vg00/home
VG Name vg00
LV UUID 1P1jjd-kNCV-1WhY-wfv9-rxpn-ExXv-Nu13T6
LV Write Access read/write
LV Status NOT available
LV Size 360.00 GB
Current LE 92160
Segments 3
Allocation contiguous
Read ahead sectors 0
pvdisplay:
--- Physical volume ---
PV Name /dev/hda3
VG Name vg00
PV Size 128.54 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 32905
Free PE 0
Allocated PE 32905
PV UUID Ivsdja-iGRK-RJhK-CODr-XaEB-tlag-tEcVOv
--- Physical volume ---
PV Name /dev/hdd1
VG Name vg00
PV Size 74.52 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 19077
Free PE 0
Allocated PE 19077
PV UUID SY7qDO-YtlS-mZBw-5Pi2-53nF-vXOu-9mZI7t
--- Physical volume ---
PV Name /dev/hdb1
VG Name vg00
PV Size 186.30 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 47694
Free PE 7516
Allocated PE 40178
PV UUID 5GBueV-Rmxu-thR6-jaoU-00Yg-49gs-A0slTr
reply other threads:[~2005-05-08 18:50 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=427E5FC2.6070900@opensolutions.ws \
--to=alex@opensolutions.ws \
--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.