Subject: RE: [nfsv4] is this a valid locking sequence?

From: "Noveck, Dave" <[email-masked]>
Date: Fri, 29 Aug 2003 07:06:25 -0700

I would say it is valid.

Also, my interpretation is that you do want to retry the
original lock, you should do it with seqid y+1 as well.
I think the request with seqid y has completed when you 
get the response and you are not polling for the results
of that original request but rather polling for lock
availability using a sequence of requests.

-----Original Message-----
From: Ronald E Bretschneider [mailto:[email-masked]]
Sent: Thursday, August 28, 2003 6:58 PM
To: [email-masked]
Subject: [nfsv4] is this a valid locking sequence?

Hi,

Section 8.1.5 says "Note for requests that contain a sequence number, for
each lock_owner, there should be no more than one  outstanding request".
What does "one outstanding request" mean? Does the request mean the RPC
operation or does it mean the completion of the asynchronous lock grant? As
an example, does this mean that if a lockowner has issued a blocking lock
request which has been denied, must the client poll for the results before
issuing a subsequent locking request on behalf of this lockowner?

In other words, is the following locking sequence valid? Certainly each
lock request is in a different compound RPC.
/* blocking request, cfh=f1 */

Lock  locktype=writew_lt
      reclaim=false
      offset=0
      length=100
      locker.lock_stateid=x1
      locker.lock_seqid=y
/* server returns NFS4ERR_DENIED */

/* blocking request, different range than the previous request, cfh=f1 */
lock  locktype=writew_lt      blocking request for a different range
      reclaim=false
      offset=1000
      length=200
      locker.lock_stateid=x1
      locker.lock_seqid=y+1

Does the server allow this request, or must the client poll for the granted
lock before being allowed to issue the second lock request?

thanks,
Ron

_______________________________________________
nfsv4 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nfsv4

_______________________________________________
nfsv4 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nfsv4