Description of problem:
During OS installation it is alarmingly common to find multiple VGs with the same name -- often, some of these VGs are also incomplete. Managing this in the context of trying to lay down a sane storage configuration for a new OS installation is impossible when the only way to specify a VG is by name.
Version-Release number of selected component (if applicable):
lvm2-2.02.99
How reproducible:
always
Steps to Reproduce:
1. install system with LVM autopart on system with 2 HDDs
2. install system again with LVM autopart but only with one of those HDD available
3. boot the system with both HDDs present and try to specify which of the two identically-named VGs you want lvm to act on.
Actual results:
problems due to there being no way to differentiate the duplicate VGs when running LVM commands
Expected results:
A way to specify a VG in a way that can reasonably be expected to be unique.
Additional info:
For now, it would suffice to add this ability to lvs, vgchange, and vgremove.
Yes - we have long term outstanding RFE Bug #449832.
If during the installation process various disks are present to the lvm2 tools - it's probably the best to add some salt to vgname created by installer then,
since no validation could prevent in duplicate name creation.
But anyway specifically in this case the only tool which is designed and does fully work with UUIDs is the vgrename tool i.e.:
vgrename Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 VolGroup00_tmp
*** This bug has been marked as a duplicate of bug 449832 ***