vgdisplay - invalid lv in extent map

[Ratzie]

We just recently rebuilt a RH ES3 to RH 4.
Everything is working fine, database is working on these LV's, things are getting written too, except for vgdisplay.

Now everything is under /dev/mapper instead of /dev/vg01
But, from further reading this should not be an issue.

I believe this is also causing an issue when we try to create a lv for snap shot backup.

Error:
[root@server ~]# vgdisplay
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" doesn't exist
--- Volume group ---
VG Name vg00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 6
Open LV 6
Max PV 0
Cur PV 1
Act PV 1
VG Size 33.77 GB
PE Size 4.00 MB
Total PE 8644
Alloc PE / Size 5888 / 23.00 GB
Free PE / Size 2756 / 10.77 GB
VG UUID knNrX5-yWNG-PxYh-Ra9c-VBaQ-5NYn-Dt3UoI


Error on Backup:
$LVCREATE --size 1000M --snapshot -n backup1 /dev/vg01/lvdb1

invalid lv in extent map
Couldn't fill logical volume maps.
invalid lv in extent map
Volume group for uuid not found: QjeRKVX0rmt9Pb1adWv8jXuP8LfwwsUE0000000000000000000000000
0000002
Failed to suspend origin lvdb1


[root@server ~]# df -h
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 66M 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/acdb
/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/db1
/dev/mapper/vg01-lvdb2
9.9G 2.9G 6.6G 31% /opt/app/oracle/oradata/db2
/dev/mapper/vg01-lvdb3
9.9G 4.6G 4.8G 49% /opt/app/oracle/oradata/db3
/dev/mapper/vg01-lvmob
15G 14G 306M 98% /opt/app/oracle/oradata/mol
/dev/mapper/vg01-lvsstrs
5.0G 2.8G 2.0G 59% /opt/app/oracle/oradata/ssst
/dev/mapper/vg01-lvwfrpt
5.0G 1.1G 3.7G 22% /opt/app/oracle/oradata/wfrt
/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

[Steven E. Protter]

Shalom,

How about:

vgdisplay /dev/mapper/vg01

or

vgdisplay -v /dev/mapper/vg01

I'm just feeling my way around with lvm on Linux but I'm thinking my command should work.

SEP

[Ratzie]

All poop out.

[root@server ~]# vgdisplay /dev/mapper/vg01
Invalid volume group name: mapper/vg01
[root@server ~]# vgdisplay -v /dev/mapper/vg01
Using volume group(s) on command line
Invalid volume group name: mapper/vg01
[root@server ~]# vgdisplay /dev/mapper/vg01-lvdb1
Invalid volume group name: mapper/vg01-lvdb1

[Ivan Ferreira]

Run vgcfgbackup -f /etc/lvm/backup/vg01-lvm.bak vg01

Then run

vgcfgrestore vg01

To try to fix the LVM database configuration.

[Ratzie]

Will this harm the data on the logical volume?

Any precautions?

[Ivan Ferreira]

Always have a good backup before any changes related to disk. The command should not generate any problems, at maximum should fail.

[Jeroen Peereboom]

lvm on linux is more or less the same as on HP-UX.

On HP-UX I would try vgscan -v.
Ypu may even need vgimport.
Check the man pages...

JP

[Ratzie]

I can not run vgcfgbackup or any vg command. I have opened up a trouble with RedHat.