On Thu, 2016-11-10 at 10:58 -0500, Benjamin Coddington wrote:
> Hi Anna,
>
> On 10 Nov 2016, at 10:01, Anna Schumaker wrote:
> >
> > Do you have an estimate for when this patch will be ready? I want
> > to
> > include it in my next bugfix pull request for 4.9.
>
> I haven't posted because I am still trying to get to the bottom of
> another
> problem where the client gets stuck in a loop sending the same
> stateid
> over
> and over on NFS4ERR_OLD_STATEID. I want to make sure this problem
> isn't
> caused by this fix -- which I don't think it is, but I'd rather make
> sure.
> If I don't make any progress on this problem by the end of today,
> I'll
> post
> what I have.
>
> Read on if interested in this new problem:
>
> It looks like racing opens with the same openowner can be returned
> out
> of
> order by the server, so the client sees stateid seqid of 2 before
> 1.
> Then a
> LOCK sent with seqid 1 is endlessly retried if sent while doing
> recovery.
>
Why is it doing that? nfs4_lock_prepare() should be copying the stateid
from the nfs4_state structure on each iteration.
Cheers
Trond��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
