Help! VG corrupted?

Hello,

I am running Mandrake 8.1 which installs Linux LVM 0.9. I've read posts that mention that 0.9 is "bad for your health." While I'm not totally sure why or how, it seems to be the case for me as well.

I installed the OS and ran find with one IDE HD partition dedicated (/dev/hda9, one VG on one PV) to LVM and two LV's (/usr and /var). Yesterday, I added another partition (/dev/hda7) and added its PEs to the VG. I thhen added the newly added PE's to the /usr LV. Everything was great. Then I rebooted. Upon reboot, I got:

[root@cray]# vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- found inactive volume group "vg0"
vgscan -- reading data of volume group "vg0" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
data of volume group "vg0" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating
"/etc/lvmtab" and "/etc/lvmtab.d"
[root@cray]#

I then tried the vgcfgrestore, which ran sucessfully. Now I get vgscan reporting no volumes. Found a reference on how to fix this (using dd and reading uuids from pv's, then writing them back to the disk). That procedure brings me back to the starting point.

It seems the data is there because pvscan reports:

[root@cray]# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/ide0/host0/bus0/target0/lun0/part7" is
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide0/host0/bus0/target0/lun0/part9" is
associated to an unknown VG (run vgscan)
pvscan -- total 2 [12.02 GB] / in use: 2 [12.02 GB] / in no VG: 0 [0]
[root@cray]#

One more note of interest: My partitions on disk are out of order. hda7 occupies cylinders 2848-3736 and hda9 occupies cylinders 2168-2847.

[root@cray]# fdisk /dev/hda
Command (m for help): p

Disk /dev/hda: 255 heads, 63 sectors, 3763 cylinders Units = cylinders of 16065 * 512 bytes

   Device Boot     Start       End      Blocks    Id  System
/dev/hda1  *           1       934     7502323+    b  Win95 FAT32
/dev/hda2            935      3736    22507065     5  Extended
/dev/hda5  *         935      1874     7550518+    7  HPFS/NTFS
/dev/hda6           1875      2135     2096451    83  Linux
/dev/hda7           2848      3736     7140861    8e  Linux LVM
/dev/hda8           2136      2167      256977    82  Linux swap
/dev/hda9           2168      2847     5462037    8e  Linux LVM

Partition table entries are not in disk order

So, can anyone help me? Would recreating the VG and adding the PV's to it restore access to my data? Or would I just blow it all away in the attempt?

Please send responses directly to [email protected]

Thanks for any help!
-Ben K
[email protected]

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Ben,

what does vgck(8) tell you about the health of your LVM on disk metadata?
BTW: it is recommended that you upgrade to LVM 1.0.1

Quoted 79 lines · Ben

Hello,

I am running Mandrake 8.1 which installs Linux LVM 0.9. I've read posts that mention that 0.9 is "bad for your health." While I'm not totally sure why or how, it seems to be the case for me as well.

I installed the OS and ran find with one IDE HD partition dedicated (/dev/hda9, one VG on one PV) to LVM and two LV's (/usr and /var). Yesterday, I added another partition (/dev/hda7) and added its PEs to the VG. I thhen added the newly added PE's to the /usr LV. Everything was great. Then I rebooted. Upon reboot, I got:

[root@cray]# vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- found inactive volume group "vg0"
vgscan -- reading data of volume group "vg0" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
data of volume group "vg0" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating
"/etc/lvmtab" and "/etc/lvmtab.d"
[root@cray]#

I then tried the vgcfgrestore, which ran sucessfully. Now I get vgscan reporting no volumes. Found a reference on how to fix this (using dd and reading uuids from pv's, then writing them back to the disk). That procedure brings me back to the starting point.

It seems the data is there because pvscan reports:

[root@cray]# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/ide0/host0/bus0/target0/lun0/part7" is
associated to an unknown VG (run vgscan)
pvscan -- inactive PV "/dev/ide0/host0/bus0/target0/lun0/part9" is
associated to an unknown VG (run vgscan)
pvscan -- total 2 [12.02 GB] / in use: 2 [12.02 GB] / in no VG: 0 [0]
[root@cray]#

One more note of interest: My partitions on disk are out of order. hda7 occupies cylinders 2848-3736 and hda9 occupies cylinders 2168-2847.

[root@cray]# fdisk /dev/hda
Command (m for help): p

Disk /dev/hda: 255 heads, 63 sectors, 3763 cylinders Units = cylinders of 16065 * 512 bytes

   Device Boot     Start       End      Blocks    Id  System
/dev/hda1  *           1       934     7502323+    b  Win95 FAT32
/dev/hda2            935      3736    22507065     5  Extended
/dev/hda5  *         935      1874     7550518+    7  HPFS/NTFS
/dev/hda6           1875      2135     2096451    83  Linux
/dev/hda7           2848      3736     7140861    8e  Linux LVM
/dev/hda8           2136      2167      256977    82  Linux swap
/dev/hda9           2168      2847     5462037    8e  Linux LVM

Partition table entries are not in disk order

So, can anyone help me? Would recreating the VG and adding the PV's to it restore access to my data? Or would I just blow it all away in the attempt?

Please send responses directly to [email protected]

Thanks for any help!
-Ben K
[email protected]

Quoted 5 lines

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Regards,
Heinz -- The LVM Guy --

*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf Germany
[email protected] +49 2626 141200

                                                       FAX 924446

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

I will try to get a newer version of LVM installed this week and give you the response from vgck.

BTW, is it safe for me to just use the 1.0.1rc4 utils and kernel on a VG created with the 0.9 release?