vgcfgbackup fails - invalid lv in extent map

[Ratzie]

We installed RH ES 4. Previous was RH AS 3.
New OS install went on vg00, we left vg01 data alone because it contained data.
The install went fine. And everything is working.
But, we can not take a snap shot of vg01.

[root@server backup]# ll
total 16
-rw------- 1 root root 2494 Mar 11 12:13 vg00
-rw------- 1 root root 5184 Mar 22 11:24 vg01


I tried to do a vgcfgbackup and it fails.
vgcfgbackup -f /etc/lvm/backup/vg01-lvm.bak vg01
invalid lv in extent map
Couldn't fill logical volume maps.
invalid lv in extent map
Couldn't fill logical volume maps.
Volume group "vg01" not found


# vgdisplay --partial --verbose
Partial mode. Incomplete volume groups will be activated read-only.
Finding all volume groups
Finding volume group "vg01"
invalid lv in extent map
Couldn't fill logical volume maps.
Wiping cache of LVM-capable devices
invalid lv in extent map
Couldn't fill logical volume maps.
Volume group "vg01" doesn't exist


Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg00-root
1008M 143M 814M 15% /
/dev/sda2 99M 13M 82M 14% /boot
/dev/mapper/vg01-lvappbk
20G 3.4G 16G 18% /dbck
none 2.0G 0 2.0G 0% /dev/shm
/dev/mapper/vg01-lvhome
5.0G 3.1G 1.7G 66% /home
/dev/mapper/vg00-opt 4.0G 67M 3.7G 2% /opt
/dev/mapper/vg01-lvoracle
4.0G 2.0G 1.8G 53% /opt/app/oracle
/dev/mapper/vg01-lvarchlog
3.0G 33M 2.8G 2% /opt/app/oracle/archivelog/db
/dev/mapper/vg01-lvdbbk
30G 33M 28G 1% /opt/app/oracle/backup
/dev/mapper/vg01-lvdb1
9.9G 7.3G 2.1G 78% /opt/app/oracle/oradata/db/db1
/dev/mapper/vg01-lvdb2
9.9G 2.9G 6.6G 31% /opt/app/oracle/oradata/db/db2
/dev/mapper/vg01-lvdb3
9.9G 4.6G 4.8G 49% /opt/app/oracle/oradata/db/db3
/dev/mapper/vg01-lvmobb
15G 14G 306M 98% /opt/app/oracle/oradata/mobb
/dev/mapper/vg01-lvsstrss
5.0G 2.8G 2.0G 59% /opt/app/oracle/oradata/sstrss
/dev/mapper/vg01-lvwfrptt
5.0G 1.1G 3.7G 22% /opt/app/oracle/oradata/wfrptt
/dev/mapper/vg00-tmp 2.0G 36M 1.9G 2% /tmp
/dev/mapper/vg00-usr 9.9G 699M 8.7G 8% /usr
/dev/mapper/vg00-var 2.0G 65M 1.9G 4% /var

[Ratzie]

I have opened a ticket with RedHat.

I will post my results

[Ratzie]

First support guy wanted us to reinstall RedHat.
Took a few days, and finally a telephone call.

Followed the instructions below, and with in 2 minutes everything was fixed!

********************
The LVM metadata format changed between RHEL3 and RHEL4. RHEL 3 used lvm1, and RHEL4 uses LVM2. The two formats are not compatible.

It is possible to convert a lvm1 volume to lvm2.

See this kbase article:

http://kbase.redhat.com/faq/FAQ_96_5844.shtm

And follow the instructions from "If you are attempting to recover or import an LVM1 volume" on...