From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@osdl.org>, Rob Sims <lkml-z@robsims.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change in NFS client behavior
Date: Thu, 01 Sep 2005 19:38:17 -0400 [thread overview]
Message-ID: <1125617897.7627.14.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050831145545.GA8426@robsims.com>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
on den 31.08.2005 Klokka 08:55 (-0600) skreiv Rob Sims:
> We have noticed when changing from kernel 2.4.23 to 2.6.8 that
> timestamps of files are not changed if opened for a write and nothing is
> written. When using 2.4.23 timestamps are changed. When using a local
> filesystem (reiserfs) with either kernel, timestamps are changed.
> Symptoms vary with the client, not the server. See the script below.
>
> When run on a 2.4.23 machine in an NFS mounted directory, output is
> "Good." When run on a 2.6.8 or 2.6.12-rc4 machine in an NFS directory,
> output is "Error."
>
> Is this a bug? How do we revert to the 2.4/local fs behavior?
This is a consequence of 2.6 NFS clients optimising away unnecessary
truncate calls. Whereas this is correct behaviour for truncate(), it
appears to be incorrect for open(O_TRUNC).
In fact, local filesystems like xfs and ext3 appear to have the opposite
problem: they change ctime if you call ftruncate(0) on the zero-length
file, as the attached test shows.
Cheers,
Trond
[-- Attachment #2: test.c --]
[-- Type: text/x-csrc, Size: 1447 bytes --]
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <errno.h>
#include <time.h>
#include <unistd.h>
int main(int argc, char *argv[])
{
struct stat buf1, buf2, buf3;
int fd;
if (argc != 2) {
printf("syntax: %s filename\n", argv[0]);
exit(1);
}
fd = open(argv[1], O_CREAT|O_EXCL|O_WRONLY, 0644);
if (fd == -1) {
perror("open(%s, O_CREAT|O_EXCL|O_WRONLY) failed\n", argv[1]);
exit(1);
}
if (fstat(fd, &buf1) == -1) {
perror("fstat() failed\n");
exit(1);
}
printf("File: %s, st_size = %lu, st_ctime = %s\n", argv[1],
buf1.st_size,
asctime(localtime(&buf1.st_ctime)));
close(fd);
sleep(2);
fd = open(argv[1], O_TRUNC|O_WRONLY);
if (fd == -1) {
perror("open(%s, O_TRUNC|O_WRONLY) failed\n", argv[1]);
exit(1);
}
if (fstat(fd, &buf2) == -1) {
perror("fstat() failed\n");
exit(1);
}
printf("File: %s, st_size = %lu, st_ctime = %s\n", argv[1],
buf2.st_size,
asctime(localtime(&buf2.st_ctime)));
if (buf1.st_ctime == buf2.st_ctime)
printf("Bad behaviour in open(%s, O_TRUNC)!\n", argv[1]);
sleep(2);
if (ftruncate(fd, 0) == -1) {
perror("ftruncate(0) failed\n");
exit(1);
}
if (fstat(fd, &buf3) == -1) {
perror("fstat() failed\n");
exit(1);
}
printf("File: %s, st_size = %lu, st_ctime = %s\n", argv[1],
buf3.st_size,
asctime(localtime(&buf3.st_ctime)));
if (buf2.st_ctime != buf3.st_ctime)
printf("Bad behaviour in ftruncate(0)!\n");
close(fd);
exit(0);
}
next prev parent reply other threads:[~2005-09-01 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 14:55 Rob Sims
2005-09-01 23:38 ` Trond Myklebust [this message]
2005-09-02 3:43 ` Trond Myklebust
2005-09-02 3:45 ` Andrew Morton
2005-09-02 3:52 ` Trond Myklebust
2005-09-02 4:07 ` Andrew Morton
2005-09-02 4:15 ` Trond Myklebust
2005-09-02 4:19 ` Trond Myklebust
2005-09-02 4:38 ` Andrew Morton
2005-09-07 14:25 ` Rob Sims
2005-09-02 15:39 ` Rob Sims
2005-09-02 15:06 ` Drop NFS speed on move from kernel 2.4 to 2.6 (was: Change in NFS client behavior) Tomasz Kłoczko
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=1125617897.7627.14.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml-z@robsims.com \
/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®