Re: How to invalidate NFS read cache?

2009-05-15 Thread Konrad Heuer
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

Re: How to invalidate NFS read cache?

2009-05-14 Thread Konrad Heuer
On Tue, 12 May 2009, Robert Watson wrote: On Fri, 8 May 2009, Konrad Heuer wrote: sporadically, I observe a strange but serious problem in our large NFS environment. NFS servers are Linux and OS X with StorNext/Xsan cluster filesystems, NFS clients Linux and FreeBSD. NFS client A changes

Re: How to invalidate NFS read cache?

2009-05-12 Thread Robert Watson
On Fri, 8 May 2009, Konrad Heuer wrote: sporadically, I observe a strange but serious problem in our large NFS environment. NFS servers are Linux and OS X with StorNext/Xsan cluster filesystems, NFS clients Linux and FreeBSD. NFS client A changes a file, but nfs client B (running on FreeBSD)

Re: How to invalidate NFS read cache?

2009-05-12 Thread Robert Watson
On Tue, 12 May 2009, Robert Watson wrote: Normally, NFS clients implement open-to-close consistency, which dictates that when a close() occurs on client A, all pending writes on the file should be issued to the server before close() returns, so that a signal to client B to open() the file

How to invalidate NFS read cache?

2009-05-08 Thread Konrad Heuer
Hello, sporadically, I observe a strange but serious problem in our large NFS environment. NFS servers are Linux and OS X with StorNext/Xsan cluster filesystems, NFS clients Linux and FreeBSD. NFS client A changes a file, but nfs client B (running on FreeBSD) does still see the old