It's the "assuming of course" part that will bite you :) One false move and wham, all is gone. And how to keep the directory in sync is another bit of the fun. The future promises to solve this for us. In the meantime, you can use CSE. Or wait...
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 1:08 PM To: [email protected] Subject: [IBMVM] Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux gues= ts spread across three VM lpars. All DASD is defined as shared. All of the = linux guests have been defined as TCPIP Layer 2; so that we can easily mo= ve guests between lpars for performance/maintenance reasons. Each guests has= unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable= to share the full volumes that these mini-disks reside on, across VM lpar= s; assuming of course, that a linux guest is completely shutdown and logged = off of one lpar before it is restarted on another ? Bob
