On Thursday, 06/08/2006 at 08:12 AST, Michael MacIsaac/Poughkeepsie/[EMAIL PROTECTED] wrote: > 1) when you need to write to a disk that others have R/O, all others > should unmount the disk, > 2) then the master can mount it, write to it and unmount it. > 3) then all others can mount it R/O again. > > This is a good, maybe even best, practice.
It's stronger than that, Mike. It's a *requirement* of the technology. Secretly changing a disk used by a running Linux image is no different than changing a disk used by CMS (ERROR 3 READING FILE). Or VSE, or MVS, or AIX, or Windows, or Solaris, or ..... Only when an explicit sharing arrangement is created can you safely change the disk. E.g. SFS, NFS, AFS, GFS, .... Even in MVS you have to configure GRS to perform reserve/release for ENQ operations. I know some people will be shocked, but z/VM can't perform miracles. <thud>. :-) Though I am forced to admit that it does a pretty good imitation! Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
