From owner-freebsd-hackers@FreeBSD.ORG Fri May 15 07:34:47 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F19831065670; Fri, 15 May 2009 07:34:47 +0000 (UTC) (envelope-from kheuer2@gwdg.de) Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23]) by mx1.freebsd.org (Postfix) with ESMTP id B32E58FC1B; Fri, 15 May 2009 07:34:47 +0000 (UTC) (envelope-from kheuer2@gwdg.de) Received: from gwdu60.gwdg.de ([134.76.8.60]) by mailer.gwdg.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M4rwM-00044K-7b; Fri, 15 May 2009 09:34:46 +0200 Date: Fri, 15 May 2009 09:34:46 +0200 (CEST) From: Konrad Heuer To: Robert Watson In-Reply-To: <20090515073949.M70549@gwdu60.gwdg.de> Message-ID: <20090515093121.W70549@gwdu60.gwdg.de> References: <20090508101555.J47014@gwdu60.gwdg.de> <20090515073949.M70549@gwdu60.gwdg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: freebsd-hackers@freebsd.org Subject: Re: How to invalidate NFS read cache? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 07:34:48 -0000 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