Forgive me for what may be an obvious question. In the middle of
tracking down NFS4ERR_RESOURCE storms from an AIX server to linux
clients on three busy webservers, I noticed that our linux client
performs a compound OPEN,GETATTR for every read of a file even if the
reads are well within the attribute cache timeout. Adding nocto doesn't
seem to change this behavior -- and for apache looking up numerous
.htaccess files it would be great to avoid the trip to the server to
revalidate attributes if we're within the timeout.
So the simple question: is this expected? I'd like to minimize
consecutive GETATTR calls, if possible, and get the most from VFS cache.
I've got some ridiculous timeouts set up at this point:
barasinga.uvm.edu:/ on /fs/barasinga type nfs4
rw,sec=krb5,nocto,hard,intr,actimeo=3600,addr=132.198.101.73
Ben
--
Benjamin Coddington
Systems Architecture and Administration
Enterprise Technology Services
University of Vermont
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
