maybe 'vgchange -ay vg00' ? Scott
2009/6/4 van Sleeuwen, Berry <[email protected]> > Actually, the three guests were created identical (build the first guest > and then DDR it to the remaining two). So indeed (*blush*) the PV's had > identical UUID's. So while I removed the old LVM on the disks and > created a new LVM on those PV's, the UUID remained the same. > > I misread the error: "Found duplicate PV > GMLtsU5ZIqIjBRPx7WOQFegPPe9CbYOf: using /dev/dasdu1 not /dev/dasdq1" > pointed to the UUID and not to the /dev/dasd[xyz]. > > Now I have taken this a step back. I also removed the PV's and recreated > the LVM starting with the pvcreate. And now I do get both the old vg01 > and the new vg00 when I execute vgdisplay -v. > > Close but not quite there yet. While vgdisplay does find both LVM's I do > not have the vg00 in my /dev/ directory. /dev/vg01 is available. The > lvdisplay shows the LV status for the new volumes in /dev/vg00/v[x] as > "NOT Available". So I can't mount the new volumes. What can I do to get > also the new vg to be availabe for mounting the volumes? > > Regards, Berry. > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Richard Troth > Sent: donderdag 4 juni 2009 1:02 > To: [email protected] > Subject: Re: How to copy LVM system > > <snip> > > > It is extremely unlikely that you have duplicate UUIDs unless you image > copied DASD to DASD. > > > -- R; <>< > > > ---------------------------------------------------------------------- > 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
