[linux-lvm] duplicate names
Curtis Doty
Curtis at GreenKey.net
Mon Aug 7 23:52:25 UTC 2006
I stuck two drives in a recovery server. Each is a separate default Fedora
install; with a big monster VolGroup00/LogVol00 root filesystem. However,
since they were each separate systems the above VG/LV names collide.
I'd like to mount them up simultaneously and move data between them. But I
would also like to avoid modifying the labels/UUIDs so they will still
work back in their original systems. Is there a FAQ on this?
Also, to this n00b, the output below seems inconsistent:
# pvdisplay /dev/sdb2
--- Physical volume ---
PV Name /dev/sdb2
VG Name VolGroup00
PV Size 233.66 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 7477
Free PE 1
Allocated PE 7476
PV UUID 6kTTcS-jTbH-XN4x-SqUg-fnlS-Et0k-qlmJAC
# pvdisplay /dev/sdc2
--- Physical volume ---
PV Name /dev/sdc2
VG Name VolGroup00
PV Size 69.12 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 2212
Free PE 1
Allocated PE 2211
PV UUID jkBXwB-OpnB-IefX-LdBK-Hr0m-eDg8-uIIZJD
Which is fine and clear. But look at this: ?!?
# pvdisplay /dev/sd{b,c}2
--- Physical volume ---
PV Name /dev/sdb2
VG Name VolGroup00
PV Size 233.66 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 7477
Free PE 1
Allocated PE 7476
PV UUID 6kTTcS-jTbH-XN4x-SqUg-fnlS-Et0k-qlmJAC
--- NEW Physical volume ---
PV Name /dev/sdc2
VG Name
PV Size 69.14 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID jkBXwB-OpnB-IefX-LdBK-Hr0m-eDg8-uIIZJD
Obviously, only the first PV is the one associated with the VolGroup00 in
the kernel. But how does one address the second PV/VG/LV (possibly with
temporary names)?
Lastly, pvscan is also annoyingly blind:
# pvscan
PV /dev/sdb2 VG VolGroup00 lvm2 [233.66 GB / 32.00 MB free]
Total: 1 [233.66 GB] / in use: 1 [233.66 GB] / in no VG: 0 [0 ]
Which is inconsistent with the man page: "scans all supported LVM block
devices in the system for physical volumes" Maybe it should say "scans
only those LVM block devices that can be address by the current kernel"?
Or am I overlooking something in the documentation?
../C
More information about the linux-lvm
mailing list