[Spam-fortigate] Re: NFSv4 client's BUG?

[J. Bruce Fields]

On Wed, Jul 16, 2008 at 04:02:32PM +0800, Wei Yongjun wrote:
> J. Bruce Fields wrote:
>> On Mon, Jul 14, 2008 at 10:03:01AM +0800, Wei Yongjun wrote:
>>   
>>> J. Bruce Fields wrote:
>>>> So, is the problem occuring because the client is doing a setattr to
>>>> modify the size using a sequence id returned from a read delegation?
>>>>
>>>>         
>>> This happend in special case:
>>>
>>> OPEN (OPEN4_SHARE_ACCESS_BOTH)    --->                                
>>>      <---      OPEN Reply OK
>>> SETATTR (size=0)                  --->
>>> OPEN (OPEN4_SHARE_ACCESS_READ)    --->
>>>                                     <---      SETATTR Reply NFSERR_OPENMODE
>>>                                     <---      OPEN Reply OK
>>>     
>>
>> Can you see which stateid the SETATTR was done with (in particular,
>> where did it come from)?  (You could just send me a link to the raw
>> capture if you'd like).
>>
>>   
> The file in this mail is a small tcpdump file of this error, the  
> NFSERR_OPENMODE is the NO.298 packet.

Yes, so the stateid used on the setattr represents a read delegation,
and was returned in packet 291.  I think that's a client bug.

Trond, do you agree, and if so, is this something familiar?

--b.