Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
- Subject: Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
- From: 林 智子 <email@hidden>
- Date: Wed, 29 Sep 2010 09:17:39 +0900
The NFS that issues a create call with a client exclusive flag must
issue SETATTR call subsequently to specify the file attributes
clearly.
This is clearly described in Implementation Section of RFC1813 as follows.
Once the client has performed a successful exclusive
create, it must issue a SETATTR to set the correct file
attributes. Until it does so, it should not rely upon any
of the file attributes, since the server implementation
may need to overload file metadata to store the verifier.
The captured data using tcpdump shows that the MacOSX client issued a
SETATTR call. However, the issued SETATTR call only specifies UID/GID.
The SETATTR call does not specify any timestamps that must be
specified by the NFS client.
The RFC1813 statement, "it must issue a SETATTR to set the correct
file attributes." shows that NFS server does not need to request NFS
clients to issue a SETATTR call. The client itself must issue a
SETATTR call.
Thanks,
Tomoko Hayashi
On Tue, 28 Sep 2010 13:26:44 -0700
Mike Mackovitch <email@hidden> wrote:
> On Mon, Sep 27, 2010 at 08:38:34AM +0900, 林 智子 wrote:
> >
> > If anyone knows a solution to this problem, we would greatly appreciate your advice. Thanks in advance.
>
> The solution is to have the NFS server put a sane value in the atime
> when a file is created exclusively and the NFS client doesn't explicitly
> ask it to set the atime.
>
> Or, simply access the file after creating it so the server updates the
> atime to something sane.
>
> HTH
> --macko
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden