From: Frank van Maarseveen <frankvm@frankvm.com>
To: Andre Majorel <aym-xunil-Bi/FLWfhfolQFI55V6+gNQ@public.gmane.org>
Cc: linux-nfs@vger.kernel.org, Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: atimes not updated over NFS
Date: Mon, 14 Jan 2008 09:34:35 +0100 [thread overview]
Message-ID: <20080114083435.GA24215@janus> (raw)
In-Reply-To: <20080109235153.GI9212-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
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 </dev/zero >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)
--
Frank
next prev parent reply other threads:[~2008-01-14 8:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 10:13 atimes not updated over NFS Andre Majorel
[not found] ` <20080109101313.GG9212-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2008-01-09 15:27 ` Trond Myklebust
[not found] ` <1199892437.11141.2.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-09 22:37 ` Andre Majorel
[not found] ` <20080109223748.GH9212-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2008-01-09 23:23 ` Trond Myklebust
[not found] ` <1199920996.7638.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-09 23:31 ` Trond Myklebust
2008-01-09 23:51 ` Andre Majorel
[not found] ` <20080109235153.GI9212-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2008-01-14 8:34 ` Frank van Maarseveen [this message]
2008-01-14 15:43 ` Trond Myklebust
[not found] ` <1200325393.7470.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-14 17:51 ` Frank van Maarseveen
2008-01-21 19:06 ` J. Bruce Fields
2008-01-21 19:31 ` Trond Myklebust
[not found] ` <1200943865.25562.56.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-21 21:02 ` Frank van Maarseveen
2008-01-21 21:09 ` J. Bruce Fields
2008-01-22 17:17 ` J. Bruce Fields
2008-01-29 2:59 ` J. Bruce Fields
2008-01-29 4:14 ` J. Bruce Fields
2008-01-29 8:34 ` Jens Axboe
2008-01-29 18:27 ` J. Bruce Fields
2008-01-29 18:30 ` Jens Axboe
2008-01-29 19:45 ` J. Bruce Fields
2008-01-29 19:51 ` Jens Axboe
2008-01-29 20:09 ` J. Bruce Fields
2008-01-29 20:12 ` Jens Axboe
2008-01-29 20:37 ` Andre Majorel
[not found] ` <20080129203713.GS17213-956IwFboN44acnK+F/IuxqxOck334EZe@public.gmane.org>
2008-01-30 11:23 ` Jens Axboe
2008-01-30 12:13 ` Andre Majorel
-- strict thread matches above, loose matches on Subject: below --
2007-12-26 23:12 Andre Majorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080114083435.GA24215@janus \
--to=frankvm@frankvm.com \
--cc=aym-xunil-Bi/FLWfhfolQFI55V6+gNQ@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.