I took a drive from an ailing machine to suck the data out of it. This
drive used to be part of a single drive LVM. Now, when I connect it to
my machine, I realized I had named that vg the same name I had used in
the vg I have in my desktop associated with just one drive,
vgdisplay export
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
--- Volume group ---
VG Name export
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 465.76 GiB
PE Size 4.00 MiB
Total PE 119234
Alloc PE / Size 102400 / 400.00 GiB
Free PE / Size 16834 / 65.76 GiB
VG UUID fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB
We see that UUID fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB is the drive/vg
in use while UUID SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D is the extra
drive I just attached to my machine. So I thought on using vgrename to
change the name of the extra drive's vg so I can mount it:
vgrename SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D export1
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
WARNING: Duplicate VG name export:
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
Volume group "export" still has active LVs
What am I missing here? I thought if I told it to rename the vg with a
given uuid I would be golden. As you can see, that is not the case.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
