If the user wants to give the Linux guest a full volume mini disk, you can also use the DEVNO format of the MDISK statement in the directory. This avoids any concern regarding the real volume's volume serial number.
HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Friday, August 22, 2008 9:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Assigning 3390 DASD for Use in a zLinux Filesystem What the others have said, plus: if you're using an MDISK you shouldn't ATTACH the DASD. That's why the cylinder zero label would have changed when the Linux guest formatted the volume. If this is indeed what you did you'll want to remove the volume from the Linux guest and start again. Otherwise, that volume won't be available to the Linux guest the next time it logs off and on. Of course, you could change the MDISK to reflect the new label or change from an MDISK to a DEDICATE, but whatever you do should probably be consistent with all the other DASD allocations you do. Brian Nielsen On Fri, 22 Aug 2008 11:21:02 -0400, Robert J McCarthy <[EMAIL PROTECTED]> wrote: > We are faily new in z/VM and zLinux and have a need to add additional >DASD to a linux guest. I initialized the volumes under VM, attached them >to the guest, and notified the linux adminstrator. He formatted the >volumes under linux in preparation for use when the filesystem is >expanded. Once the volumes were formatted, I noticed that the linux >format had changed the volsers. Normally I format a volume under VM, add >it to user direct with a MDISK statement with the beginning disk >location at cylinder 1. We then recycle the guest, and the linux admin >does his thing. In order to save downtime that will be required when we >expand the filesystem, we would like to perform the linux formatting >while the guest is up. I know that there is a "DEFINE MDISK" command, >but it is a class A command and none of my linux guests are class A >users. Any suggestions ?
