From: Stefan Egli Subject: Re: NFS v3 cached directory content out of sync Date: Tue, 25 Aug 2009 21:19:20 +0200 Message-ID: References: <1250962724.8143.29.camel@heimdal.trondhjem.org> <1251115893.6325.23.camel@heimdal.trondhjem.org> <1251226809.25372.29.camel@heimdal.trondhjem.org> <1251227539.25372.35.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-nfs To: Trond Myklebust Return-path: Received: from mail-fx0-f217.google.com ([209.85.220.217]:43308 "EHLO mail-fx0-f217.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755995AbZHYTTT (ORCPT ); Tue, 25 Aug 2009 15:19:19 -0400 Received: by fxm17 with SMTP id 17so2405258fxm.37 for ; Tue, 25 Aug 2009 12:19:20 -0700 (PDT) In-Reply-To: <1251227539.25372.35.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Aug 25, 2009 at 9:12 PM, Trond Myklebust wrote: > On Tue, 2009-08-25 at 21:06 +0200, Stefan Egli wrote: >> On Tue, Aug 25, 2009 at 9:00 PM, Trond Myklebust wrote: >> > Yes. The NFS client will cache mtime whether or not you do an 'ls'. I >> > suspect the only reason for the 'ls' in that launchpad bug report, is to >> > force an mtime update (and to fill the readdir cache). >> >> Ok, interesting. I guess though that 'something' needs to read at least >> a file in that particular directory for the directory content to be >> cached, right? (i.e. either an 'ls' or some create/delete of a file?) > > Every time you use a filename, the act of looking up that name is > cached. The parent directory's mtime is also cached. If it changes, then > the cached lookup is invalidated. If not, then the cached lookup is > assumed still valid (since the directory contents are not supposed to > have changed). Great thanks, got that! Is there some docu about this level of NFS detail you know of? Esp the attribute and the data cache? Cheers, Stefan