[pnfs] [PATCH 0/2] Update seqid and stateid handling to draft 13
Iyer, Rahul
Rahul.Iyer at netapp.com
Thu Sep 13 16:24:44 EDT 2007
The state id handling patch should probably go in. As mentioned in
section 8.2.2, line 8072, the client can use either a 0 stateid seqid or
a specific one.
8072 When stateids are sent to the server by the client, it has
two
8073 choices with regard to the seqid sent. It may set the seqid
to zero
8074 to indicate to the server that it wishes the most up-to-date
seqid
8075 for that stateid's "other" field to be used. This would be
the
8076 common choice in the case of stateid sent with a READ or
WRITE
8077 operation. It also may set a non-zero value in which case
the server
8078 checks if that seqid is the correct one. In that case the
server is
8079 required to return NFS4ERR_OLD_STATEID if the seqid is lower
than the
8080 most current value and NFS4ERR_BAD_STATEID if the seqid is
greater
8081 than the most current value.
Thanks,
-Rahul
> -----Original Message-----
> From: William A. (Andy) Adamson [mailto:andros at citi.umich.edu]
> Sent: Thursday, September 13, 2007 1:12 PM
> To: Sager, Mike
> Cc: pnfs at linux-nfs.org
> Subject: Re: [pnfs] [PATCH 0/2] Update seqid and stateid
> handling to draft 13
>
> As I just emailed the list,
> draft-ietf-nfsv4-minorversion1-13.txt does not change this
> behaviour from draft-ietf-nfsv4-minorversion1-10.txt. See the
> "Vestigial Locking Infrastructure from V4" sections of both drafts.
>
> So, these patches will not be applied at this time...
>
>
> -->Andy
>
>
> On 9/12/07, Sager, Mike < Mike.Sager at netapp.com
> <mailto:Mike.Sager at netapp.com> > wrote:
>
> Two patches to bring seqid and stateid handling
> up-to-date. The first basically updates the server to ignore
> the seqid. The second deals with the stateid's seqid
> (generation number).
>
> Mike
>
> _______________________________________________
> pNFS mailing list
> pNFS at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
> <http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs>
>
>
>
>
More information about the pNFS
mailing list