From: Frank van Maarseveen Subject: Re: atimes not updated over NFS Date: Mon, 14 Jan 2008 18:51:23 +0100 Message-ID: <20080114175122.GB2768@janus> References: <20080109101313.GG9212@aym.net2.nerim.net> <1199892437.11141.2.camel@heimdal.trondhjem.org> <20080109223748.GH9212@aym.net2.nerim.net> <1199920996.7638.3.camel@heimdal.trondhjem.org> <20080109235153.GI9212@aym.net2.nerim.net> <20080114083435.GA24215@janus> <1200325393.7470.6.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andre Majorel , linux-nfs@vger.kernel.org To: Trond Myklebust Return-path: Received: from frankvm.xs4all.nl ([80.126.170.174]:33630 "EHLO janus.localdomain" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750867AbYANRvZ (ORCPT ); Mon, 14 Jan 2008 12:51:25 -0500 In-Reply-To: <1200325393.7470.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Mon, Jan 14, 2008 at 10:43:12AM -0500, Trond Myklebust wrote: > > On Mon, 2008-01-14 at 09:34 +0100, Frank van Maarseveen wrote: > > On Thu, Jan 10, 2008 at 12:51:53AM +0100, Andre Majorel wrote: > > > On 2008-01-09 18:23 -0500, Trond Myklebust wrote: > > > > On Wed, 2008-01-09 at 23:37 +0100, Andre Majorel wrote: > > > > > > > > > I'll take your word for it. However, let me assure you that atimes > > > > > somehow used to work over NFS, even for files small enough to fit > > > > > in the cache. Had they been broken, I would have known. I use Mutt. > > > > > > > > How would the server know to update the atime? If the file is in cache > > > > we don't READ. > > > > > > You tell me. All I can tell you is that Mutt used to work so > > > atimes were updated one way or another. > > > > I think 2.6.22 introduced this regression. On 2.6.22.10, reading a file > > on NFS does not affect atime according to stat(), not on the client and > > not on the server. This breaks several programs. > > > > Commands to reproduce this problem on the client: > > > > dd testfile count=1 > > ls -l --time=atime --full-time testfile > > sleep 2 > > wc testfile > > ls -l --time=atime --full-time testfile > > (same atime, not good) > > Can you confirm that it does not change on the server? If so, then we > need to look at the server for a fix. The client should only be > mirroring the server's idea of the correct atime. It doesn't change on the server (2.6.23.12) -- Frank