>>> On 6/3/2009 at 9:21 AM, "van Sleeuwen, Berry" <[email protected]> wrote:
> Now I have recreated an lvm in one machine, using the same volumes > because that lvm was still empty. Next I linked this new lvm into the > second machine. Vgscan finds a new vg00 but it expects the physical > volumes to be on the same dasd devices as the current vg01. That doesn't > work because these volumes are still in use on the (soon to be) old > vg01. The new LVM should now be on dasdu, -v, -w and -x. And when the > copy is completed these volumes should return to dasdq, -r, -s and -t. I've never seen a case where LVM cared about device names, just that it can find the UUIDs it writes out. Actual steps taken, and error messages received might be in order. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
