Exporting volume group to another guest - not working

[Ranga Nathan]

I was able to export a volume group from a guest but could not
successfully import into another guest. It seems that LVM is expecting
same dasd identifiers such as /dev/dasdh1 etc for its PVs. These dasd
identifiers are sequentially allocated based on new device discovery.
I am not sure how to find a way around it. I would like a portable
volume group. No, not an NFS mount!
TIA

--
__
Ranga Nathan
Work: 714-442-7591


--
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
begin:vcard
fn:Ranga Nathan
n:Nathan;Ranga
email;internet:[EMAIL PROTECTED]
tel;work:714-442-7591
version:2.1
end:vcard

Re: Exporting volume group to another guest - not working

[Vic Cross]

On 23/05/2006, at 7:59am, Ranga Nathan wrote:


It seems that LVM is expecting
same dasd identifiers such as /dev/dasdh1 etc for its PVs.


I and my colleagues have done this operation several times and never
experienced what you describe.  We have exported from a system with
less than ten DASDs and imported to a system with hundreds of DASDs
-- so the device nodes were very definitely different...

I've even moved a VG from system to system without doing the vgexport
(although I do concede that I was VERY lucky with that one).

Possibly you didn't do the vgscan after attaching the DASD to the
new system (and before you do vgimport)?  It should come back and
tell you that an exported VG was found.  You may also have trouble if
the VG you are importing has the same name as a VG that previously
existed on the system (but I would have thought vgscan would sort
that out).

Cheers,
Vic Cross

--
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