Red Hat Bugzilla – Bug 443728
Problems with vgimport if you specify 'vgnamePV_EXP' instead of just 'vgname'
Last modified: 2009-06-19 09:44:35 EDT
It seems there is a bug with vgimport if you import the volume group with the
'vgnamePV_EXP' name instead of just the original 'vgname' name. I was able to
replicate this bug like so:
Create a volume group called, say, vgname. Then ...
vgchange -an vgname
- displays vgnamePV_EXP
vgimport vgnamePV_EXP <physical_volume> <---- this is where the bug is
- displays vgnamePV_EXP instead of vgname
- still reports that the PVs are 'in EXPORTED VG "vgname"'
However if I use:
vgimport vgname <physical_volume>
- displays vgname
- shows normal/expected vgname information
Solution to the mess created:
vgrename vgnamePV_EXP vgname
... vgscan and pvscan show consistent information again.
There is a bug in RHEL3 lvm if you use 'vgimport vgnamePV_EXP <physical_volume>'
instead of 'vgimport vgname <physical_volume>'
Rhel3 is in maintenance phase and only security bugs will be fixed.
Upstream LVM does not have this bug, neither does RHEL4 or RHEL5.