From: "Lever, Charles" <Charles.Lever@netapp.com>
Subject: RE: NFS mount option - noac forces sync even if async is sp
	ecified, and no warning is given
Date: Wed, 5 Feb 2003 14:21:50 -0800
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <6440EA1A6AA1D5118C6900902745938E07D552A3@black.eng.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: nfs@lists.sourceforge.net
To: "'Heflin, Roger A.'" <Roger.A.Heflin@conocophillips.com>
Errors-To: nfs-admin@lists.sourceforge.net

> > ah, but Solaris noac doesn't disable *data* caching.  data is still
> > cached until the client detects the file has changed.  *writes* are
> > no longer cached, but reads can hit the client's data cache as long
> > as the file doesn't change on the server.
> > 
> 	Then their manpage is also wrong.  On 2.6 (and 2.8) it says:
> 	         noac           Suppress data and attribute caching.
> 
> 	It sounds very much like they kill all caching, but who knows
> 	what they actually do.

for the record, here's what my man page says (Solaris 9):

     noac    Suppress data and attribute caching.  The data
             caching that is suppressed is the write-behind.
             The local page cache is still maintained, but
             data copied into it is immediately written to
             the server.

there's a section further down in the man page called "File
Attributes" that explains in detail how attribute caching
works and what noac does, which i think also appears in the
Solaris 8 version of this page.


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs