Mark Zelden wrote:
So it looks like it has to be mounted read only by reading the above.
Right. And, just to make sure we're both on the same page, the quoted information says: "... all non-owning systems must access read-write file systems through the remote owning system" and "each system can access read-only file systems locally, and do not need to contact the owning system".
So, the determination of whether access, by a non-owning system, is local or remote is based on the R/O vs R/W status of the file system and *not* whether the individual request is a read or a write.
However, I thought I read somewhere else that the system was smart enough to handle a read request locally. Still looking...
To make that work, they would need to have some sort of cross-system buffer synchronization/invalidation, block-level owning token, serialization, or other integrity/consistency mechanism to keep the file system from returning the "wrong" data. They don't have such a thing for HFS/zFS ... yet. ;-)
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
