[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] LVM ate my data!



On Mon, 25 Feb 2002, Heinz J . Mauelshagen wrote:

> In case *all* your PVs making up your VG are accessable, your LVM metadata
> looks toasted.

The bootup should just run "vgchange -ay", ah well!

> You need to "pvcreate -ff" your PVs and vgcfgrestore a metadata backup
> to all of them.
> Before doing so, you can save your actual metadata for recovery in case
> something goes badly wrong with:

OK, metadata saved.

> So, assuming /dev/hda[34] are all your PVs which belonged to the missing VG
> (otherwise add those), figure out the recent metadata backup in /etc/lvmconf.
> Say /etc/lvmconf/VG.conf would be the one.
> 
> Then run:
Using the 1.0.3 versions...

> pvcreate -yff /dev/hda[34]

pvcreate -- WARNING: forcing physical volume creation on "/dev/hda3" of
volume group "pvg"
pvcreate -- physical volume "/dev/hda3" successfully created
pvcreate -- WARNING: forcing physical volume creation on "/dev/hda4" of
volume group "pvg"
pvcreate -- physical volume "/dev/hda4" successfully created

> vgcfgrestore -n YourVGName /dev/hda3
vgcfgrestore -- INFO: using backup file "/etc/lvmconf/pvg.conf"
vgcfgrestore -- ERROR: different structure size stored in
"/etc/lvmconf/pvg.conf" than expected in file vg_cfgrestore.c [line 139]
vgcfgrestore -- ERROR "vg_cfgrestore(): read" restoring volume group "pvg"

Hmm. Same for ./vgcfgrestore -f /etc/lvmconf/pvg.conf*

> vgcfgrestore -n YourVGName /dev/hda4
> vgscan
> vgchange -ay
> 
> Please upgrade to LVM 1.0.3 and do the pvcreate + vgcfgrestore above.

Got 1.0.3 Should I try the vgcfgresore with the old tools (v0.9)???

BTW, thanks very much for getting back so rapidly!

Thanks,
    Bill




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]