Mark: That is what I call very cool. Let me be clear, DIRM finds available DASD from the pool (in our case MOD 9s) and gives them to the clone? For example, the clones will have volumes E150, E152... E15n, which are all named the same for each clone anyway, and find DASD for them. I want to make sure I'm clear on this.
Thanks On Mon, Jul 7, 2014 at 3:15 PM, Mark Post <mp...@suse.com> wrote: > >>> 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/ > -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A & T State University Greensboro, NC 336 334 7717 x2251 ---------------------------------------------------------------------- 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/
