On Fri, 15 May 2009, Konrad Heuer wrote:
(...)
The problem I observe happens with FreeBSD 6.4-R and 7.0-R with nfsv3. The
fstab entry I use is:
server:/Volume /local/dir nfs bg,rw,intr,-T,-r32768,-w16384 0 0
The server runs on Mac OSX 10.5.
In the meantime, I had the chance to examine a failure a little bit closer.
As far as I can see in the moment a file modified on a Linux NFS client gets
a new modification time on the NFS server but the FreeBSD client still sees
the old timestamp. This obviously happens sporadically only under some
circumstances I do not know further. I'll do some further testing the next
days.
Could you imagine a kind of directory or metadata caching on FreeBSD NFS
clients that may cause this behaviour?
I forgot to mention one detail: File modification happens with emacs; thus
the modified file is indeed a new one with a new inode number whereas the
old version keeps its inode and gets renamed.
Best regards
Konrad
Konrad Heuer
GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
