Hi, Craig, --
For FBA, you are correct to dispense with 'dasdfmt'. (Will detail
that in a following note.)
You still need to stamp a bootstrap onto the FBA disk, and the
bootstrap is different for FBA than for CKD.
> ... We've altered the script to
> identify the FBA devices, format them with 'mkfs' and then use the 'dd' to
> perform the block copy. ...
Right there is a conflict. (Either that, or I have misunderstood your note.)
You can 'dd' the filesystem. So if you 'dd' the filesystem as one
whole chunk, why would you 'mkfs' beforehand?
I presume you want to use the first (and only) partition to hold
filesystems, eg: /dev/dasda1 instead of /dev/dasda. If that is
correct, then I recommend that you CMS FORMAT and RESERVE the disks
before copying to them. Let's say /dev/dasdx is a CKD source and
/dev/dasdy is an FBA target. You should ...
IPL CMS
FORMAT whatever addr is /dev/dasdy
RESERVE that same disk
boot Linux
dd if=/dev/dasdx1 of=/dev/dasdy1
If it is bootable, then also ...
mount /dev/dasdy1 /mnt
zipl -d /mnt
umount /mnt
Repeat this for all disks, except that the boot disk is the only one
you will mount and 'zipl'.
I am leaving out some details for brevity. Does this help?
-- R; <><
Rick Troth
Velocity Software
http://www.velocitysoftware.com/
On Wed, Mar 2, 2011 at 12:39, Craig Collins <grizl...@gmail.com> wrote:
> We're walking through the IBM doc "Sharing and Maintaining SLES11 Linux
> under z/VM using DCSSs and an NSS" but using EDEV FBA devices instead of
> native CKD devices. We've move to the point where we are making our first
> cloned copy and are running into issues.
>
> The original script identifies the CKD disk mount points, then uses
> 'dasdfmt' to format the destination CKD devices and 'dd' to do a block copy
> from the source to the destination devices. We've altered the script to
> identify the FBA devices, format them with 'mkfs' and then use the 'dd' to
> perform the block copy. When we try to boot the cloned copy, we don't even
> get the boot menu, it just fails with HCPGIR453W CP entered; program
> interrupt loop.
>
> If we copy the devices from within CMS using DDR, the destination server
> boots successfully following the copy.
>
> Does anyone successfully clone servers using scripts run from within a
> running linux clone server for EDEV FBA devices?
>
> I'd also be interested in hearing from anyone who has used EDEV FBA devices
> to generate sles11 servers which share read-only portions of the boot & root
> partitions without DCSS & NSS related to what they segment off for each
> server to use read-write locally. We think that's more likely the scenario
> we would want to go with, but we are walking through the above named
> document to get familiar with that method as a possibility.
>
> Craig Collins
> State of WI, DOA, DET
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
