Date: Fri, 15 May 2009 09:34:46 +0200 (CEST) From: Konrad Heuer <kheuer2@gwdg.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-hackers@freebsd.org Subject: Re: How to invalidate NFS read cache? Message-ID: <20090515093121.W70549@gwdu60.gwdg.de> In-Reply-To: <20090515073949.M70549@gwdu60.gwdg.de> References: <20090508101555.J47014@gwdu60.gwdg.de> <alpine.BSF.2.00.0905121948180.71532@fledge.watson.org> <20090515073949.M70549@gwdu60.gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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, kheuer2@gwdg.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090515093121.W70549>