Re: pNFS read/write behavior change in 2.6.39

[Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>]

On 04/26/2011 04:29 PM, Trond Myklebust wrote:
> On Tue, 2011-04-26 at 16:03 +0200, Tigran Mkrtchyan wrote:
>> I run 2.6.39-0.rc4.git2.0 build for fedora-16 build by redhat.
>> Probably Steve and Bruce can comment on the patch set.
>>
>> My observation is that state id provided by client on read to
>> DS dit not contain correct stateid:
>>
>> struct stateid4 {
>>           uint32_t        seqid;
>>           opaque          other[12];
>> };
>>
>> The seqid equals to zero when client send it to DS which is not the
>> value returned on OPEN.
> Why do you think this is a bug? Section 8.2.2 of RFC5661 not only allows
> this behaviour, it actually suggests it is appropriate for READ and
> WRITE since it means that the server isn't forced to constantly check
> the seqid value.
Well, It's not a bug, but it's not the behavior we was testing at 
Connectathon.
My expectation was that during interoperability testing we catch such 
changes.

Tigran.
> Trond