The images didn't come through as they are blocked. Are these EDEVs or standard SCSI
devices?
Change the directory on COPYCLN1 to make the root device and swap device the same device
numbers as on MSTRLCON. Make sure to log off and log on COPYCLN1 after the change.
On 02/13/2011 10:17 AM, Rakesh Krishnakumar wrote:
Hi All,
We are trying clone one Linux image running on system Z to another. Below
is the process we have adopted for the same. But while booting the cloned
image we are facing an issue that cloned root and swap partitions are
pointing to master image and not cloned image.Below are steps we have
followed. Any help in changing the pointers of root and swap partitions to
cloned image would be helpful.
Steps below illustrates the problem encountered while IPLing the new guest
after the clone process.
Here MSTRCLON is the Master Linux Copy. The target is COPYCLN1.
1 - As shown in the fig. below MDISK 200 is assigned to MSTRCLON
Linux
Guest.
- This contains Linux /boot partition.
- MDISK 300 is assigned to COPYCLN1 guest.
- DDR COPY from MDISK 200 to MDISK 300 is successful.
(Embedded image moved to file: pic08728.jpg)
2 - As shown below, A 32 GB LUN with LUN Number 00AF000000000000 is
attached to MSTRCLON Linux Guest.
- This LUN contains 26 GB / (root) partition, 6 GB Swap
Partition.
- A 32 GB LUN with LUN Number 00AE000000000000 is attached to
COPYCLN1 Linux Guest.
- From z/VM DDR COPY ALL command has been run to clone the
content of LUN 00AF000000000000 to 00AE000000000000.
- The DDR copy is successfull.
(Embedded image moved to file: pic11302.jpg)
3 - The Problem
- While IPL-ing new Guest, COPYCLN1 the boot device 300 which is
correct.
- IPL is successful only if the ' / ' and 'Swap' device is
00AF000000000000,
- This device belongs to the MSTRCLON.
- We are unable to IPL the guest with ' / ' and 'Swap' device
00AE000000000000,
Regards
Rakesh
--
Rich Smrcina
Velocity Software, Inc.
http://www.velocitysoftware.com
Catch the WAVV! http://www.wavv.org
WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
