From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: joe.korty@ccur.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] NFS no longer updates file modification times appropriately
Date: Thu, 03 Jun 2004 14:11:52 -0700 [thread overview]
Message-ID: <1086297112.3659.3.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20040603202846.GA28479@tsunami.ccur.com>
På to , 03/06/2004 klokka 13:28, skreiv Joe Korty:
> Trond,
> Paraphrased from one of my inhouse customers: "The timestamp of an
> NFS-mounted file does not change when written to, when the below test is
> run on a 2.6.6-rc1 to 2.6.7-rc2 kernel. The timestamp is appropriately
> updated when the test is run on a 2.6.5 kernel. This is with NFSv3.
> The type of system serving up the files does not seem to be a factor."
NFS is only guaranteed to flush the file to disk when you do the
close(). Your program will just result in a lot of cached writes right
up until the moment it exits...
...and no - we do not update timestamps on the client side when we cache
the write, 'cos NFS does not provide any device for ensuring that clocks
on client and server are synchronized.
Cheers,
Trond
next prev parent reply other threads:[~2004-06-03 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 20:28 Joe Korty
2004-06-03 21:11 ` Trond Myklebust [this message]
2004-06-04 3:25 ` Ingo Oeser
2004-06-06 19:17 ` Trond Myklebust
2004-06-04 13:23 ` Joe Korty
2004-06-04 23:08 ` Trond Myklebust
2004-06-04 23:24 ` Stephen Hemminger
2004-06-04 23:37 ` Trond Myklebust
2004-06-07 15:21 ` Joe Korty
2004-06-07 15:51 ` Trond Myklebust
2004-06-07 16:13 ` Joe Korty
2004-06-07 16:20 ` Trond Myklebust
2004-06-07 16:39 ` Joe Korty
2004-06-07 16:53 ` Trond Myklebust
2004-06-07 17:01 ` Trond Myklebust
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=1086297112.3659.3.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®