Yes, Filer and Clients using NTP, syncronized correctly..
Hi all,
Has anyone encounter the problem like this?
If a user replace a file (which on the Filer) using cp command using Solaris 8 machine such as;
# cp newfile oldfile
Then, on Linux server(NFS Client) A , reading the file, the file is new one.
But on another Linux server B, reading same file above,
the file is stil OLD.
We experienced many times on many files and Linux servers. I suspect some linux cache behavior (attribute caching?), but This situation still remain after a few days...
[Our mount options] rw,nosuid,bg,soft,rsize=8192,wsize=8192,timeo=11,retrans=5
[Our Linux (all)] kernel 2.4.20, based on RHL 7.3
[Filer] F825, NetApp Release 6.3.3D2
I've read Technical report written by Chuck Lever(TR3183), noct and/or noac options may help, but I don't know why such long time Linux does not see a new file.
Just a guess here, but are you using ntp to sync the date/time on the filer and the Linux box? I imagine that if there is a big discrepancy, then the Linux box might not know when a cached file needs to be refreshed.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
---
Jun Ohata ohhata@tnes.nec.co.jp