From: Rob Sims <lkml-z@robsims.com>
To: linux-kernel@vger.kernel.org
Subject: Change in NFS client behavior
Date: Wed, 31 Aug 2005 08:55:45 -0600 [thread overview]
Message-ID: <20050831145545.GA8426@robsims.com> (raw)
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?
Thanks,
Rob
#!/bin/sh
if [ -n "$1" ]; then
if [ -e "$1" ]; then
printf "%s exists - please specify a new file name.\n" "$1"
else
touch $1
origtime=`stat -c '%X %Y %Z' "$1"`
sleep 5
cat /dev/null > "$1"
newtime=`stat -c '%X %Y %Z' "$1"`
rm "$1"
printf "%s\n%s\n" "$origtime" "$newtime"
if [ "$origtime" = "$newtime" ]; then
printf "Error - timestamps not modified\n"
else
printf "Good - timestamps modified\n"
fi
fi
else
printf "Please specify a file name.\n"
fi
next reply other threads:[~2005-08-31 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 14:55 Rob Sims [this message]
2005-09-01 23:38 ` Change in NFS client behavior Trond Myklebust
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=20050831145545.GA8426@robsims.com \
--to=lkml-z@robsims.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