From: Paul Dickson <dickson@permanentmail.com>
To: linux-kernel@vger.kernel.org
Subject: NFS doen't uniformly copy timestamps to server
Date: Wed, 1 Mar 2006 17:35:54 -0700 [thread overview]
Message-ID: <20060301173554.f2d18939.dickson@permanentmail.com> (raw)
I think I first noticed this problem in late December (I wrote a script
to get around it then). If I attempt to copy the mtime with a file, it
won't get transfered. But I can set it later.
Within a NFS mount directory:
cp -a file1 file2 # Timestamp not copied
mv file1 file2 # Timestamp not copied
touch -r file1 file2 # Timestamp copied
I've looked through the man files for mount, exportfs, and exports and I
don't see an option I'm over looking. An ethereal dump shows the mtime
being sent to the server and the server replying with NFS3_OK and the
correct mtime, but the resulting file does not have the mtime applied.
More data is at:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183208
This currently happens with 2.6.16rc5-git3
Is this a problem with the NFS server or am I applying the wrong options?
-Paul
next reply other threads:[~2006-03-02 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 0:35 Paul Dickson [this message]
2006-03-02 0:57 ` Trond Myklebust
2006-03-02 18:05 ` Paul Dickson
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=20060301173554.f2d18939.dickson@permanentmail.com \
--to=dickson@permanentmail.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
Powered by JetHome