Before cloning, make sure that /etc/fstab doesn't contain any entries that look like:
/dev/disk/by-id/<somebig string> or /dev/dasd<something> You will need to change them to: /dev/disk/by-path/ccw-0.0.<disk address>-part1 The first form will change on a clone, the second form I've had problems with the drive letter changing. Chuck Tribolet trib...@us.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Mark Post <mp...@suse.com> To: LINUX-390@vm.marist.edu, Date: 07/07/2014 12:16 PM Subject: Re: Using DIRMAINT to copy an existing guest Sent by: Linux on 390 Port <LINUX-390@vm.marist.edu> >>> On 7/6/2014 at 07:19 PM, Cameron Seay <cws...@gmail.com> wrote: > Es claro. For my edification, how does the system handle the cloning of > the minidisks of the cloned-from guest? Are they physically the same > ones? Does it grad available DASD for the cloned user? Thanks! DIRMAINT will use available space from the various DASD volumes you've told it to manage. That means the cloning does involve actual copying, and not some sort of thin provisioning. Mark Post ---------------------------------------------------------------------- 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/
