>>> On 10/23/2013 at 11:35 AM, "Diep, David (OCTO-Contractor)" >>> <[email protected]> wrote: > Thanks for the feedback. > > Let me understand this... so, if the system that has RW (call this the > master) to the volume crashes, the system that has RO (call this the client) > will not have access to the serve the data housed in that volume?
It will have access, just not necessarily to valid content. If the "owning" system has it read-write it is doing a lot of caching of file system data and metadata which the read-only system won't see unless/until it gets written to disk. The basic rule is, if you want to share disks between z/VM guests, _all_ systems sharing it must _only_ share it read-only. That rules out any "live" updates while the sharing is happening. > I want the content and the servers to be live simultaneously, but any > updates to the data can only be completed through master system (through > samba or ftp). But as for the content, it can be accessed by either server. Then you're looking at a high availability with clustered file system setup. Red Hat doesn't offer that for System z itself. Sine Nomine Associates has partnered with them to provide the software and support. SUSE (if you're willing to consider alternatives) provides an HA product as part of the basic subscription cost for System z. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
