As Mark said, LVM doesn't care about the physical devices. It uses the UUID stamped onto each PV, along with grouping info, to recognize them and to instantiate the volume group(s). It's like mounting by label (which is popular with some shops, but problematic for others).
So ... this sounds a lot like a problem we ran into at my place, where we had to use a different volume group name because "rootvg" and "rootvg" collided. Is that your problem? Because you mentioned "vg01" with "vg00" as the new vol group. It turns out that you can have two volume groups with the same name, but you have to manage one of them under chroot (the "inner", or second) and manually remove the device files for the first (the "outer", so to speak). I will skip further details unless this is what you want to know about. Back to your question: If vg01 resides on [dasdq, dasdr, dasds, dasdt] then you should be able to bring vg00 online with [dasdu, dasdv, dasdw, dasdx]. We do stuff like this all the time. What error message are you getting? Does another virtual machine have these disks linked? 'vgscan' should reveal both volume groups. Maybe try a 'pvscan'. It is extremely unlikely that you have duplicate UUIDs unless you image copied DASD to DASD. -- R; <>< 2009/6/3 van Sleeuwen, Berry <[email protected]>: > Hello listers, > > We have a few identical SLES10 guests with LVM. Each LVM is configured > with 4 dasdvolumes, dasdq, dasdr, dasds and dasdt. When vgscan runs it > finds vg01 and its volumes. But the LVM's were configured wrong. So I > want to recreate them and copy the content into a newly created LVM. > Just like I would copy a single DASD volume I expected to mount the new > filesystem under /mnt and then copy the lvm filesystem to the new lvm. > > 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. > > How can I mount a new identical LVM into a guest and copy the existing > filesystem into that new lvm? > > > Met vriendelijke groet/With kind regards, > Berry van Sleeuwen > Flight Forum 3000 5657 EW Eindhoven > > ( +31 (0)6 22564276 > > > > > > Atos Origin <http://www.atosorigin.com/> > > MO OC Mainframe Services > > > > > > > > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
