Re: NFS cache problem

[Anton Starikov <A.Starikov@utwente.nl>]

Trond Myklebust wrote:
> "noac" just means that the client rereads the attributes every time it
> reads or writes.
> If the size and the mtime on the file haven't changed, then the client
> assumes the data in the file itself also hasn't changed. That is usually
> a good assumption on something like XFS (which has nanosecond precision
> on mtime). It can be rather inaccurate on something like EXT3 (which has
> a precision of only 1 second on mtime).
I use ReiserFS.
And here we talk not about seconds...we talk about hours sometimes.
That's seems too strange for me. For seconds I can find plenty of
explanations :)
In principal even if it will be one minute, I'll be much more happy than
now.

> If you seriously need uncached reads and writes, then you should rather,
> consider using O_DIRECT.
Unfortunatelly this is not trivial problem. A lot of software are
involved here. And I beleive that NFS should be able to work in this
conditions properly. At least it did with solaris in similar environment.

Best,
	Anton.


-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs