Subject: [nfsv4] Re: Delegation recall and delay

From: [email-masked]
Date: Thu, 7 Aug 2003 17:14:54 -0400 (EDT)

> 	client				server
> 	------				------
> 	<assume same openowner for all ops>
> 
> (1) OPEN(ACCESS_READ) ->
> (2) 				<-	OPEN is okay; provides READ delegation
> (3) CLOSE of OPEN in (1) ->
> (4)				<-	CLOSE is okay
> (5) local open for read
> (6) local open for write
> (7) OPEN(ACCESS_WRITE) ->
> (8)				<-	CB_RECALL of delegation from (2)
> (9) OPEN(ACCESS_READ) ***
> 
> 
> *** The client is attempting to OPEN the file as a result of the
>     delegation recall processing (ensuring all open state is at the
>     server)

Would another correct solution be for the server to issue the Open with
write_access at (9), but no new delegation and just leave the Read
delegation valid? (At this point, my server only recalls delegations
when there is a conflict and it only considers it a conflict if the
open request is from a different client.)

In other words, the server avoids the Recall, but doesn't issue a
Write Delegation.

Does this sound ok? rick

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