mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Paul Dickson <dickson@permanentmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS doen't uniformly copy timestamps to server
Date: Wed, 01 Mar 2006 16:57:43 -0800	[thread overview]
Message-ID: <1141261063.26382.20.camel@netapplinux-10.connectathon.org> (raw)
In-Reply-To: <20060301173554.f2d18939.dickson@permanentmail.com>

On Wed, 2006-03-01 at 17:35 -0700, Paul Dickson wrote:
> 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?

The RedHat bugzilla tracks RedHat bugs. For kernel bugs, see
bugzilla.kernel.org.

>From your description, it looks very much like the issue being tracked
in

   http://bugzilla.kernel.org/show_bug.cgi?id=6127

Feel free to try the proposed patch.

Cheers,
  Trond


  reply	other threads:[~2006-03-02  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02  0:35 Paul Dickson
2006-03-02  0:57 ` Trond Myklebust [this message]
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=1141261063.26382.20.camel@netapplinux-10.connectathon.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=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