On 02/08/11 1:34 AM, John Hodrien wrote: > On Tue, 8 Feb 2011, Dr. Ed Morbius wrote: > >> *OR* as a special case, if access is *only* read-only (or read-only to >> all but one initiator). > I get the all read-only case, but wouldn't the read-only clients end up > caching filesystem data that has since been changed by the read-write client? > I'd have thought the read-only initiators would get pretty quickly confused. indeed, and when the writer IS updating directory structures and such, there's no guarantee the writes will be in an order that makes sense to someone else who slips in and reads said data.