On Mon, 2017-11-06 at 17:46 -0500, Andrew W Elble wrote:
> Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> writes:
>
> > v8:
> > - Really fix compile issue when CONFIG_NFS_V4_1=n
> > - nfs_inode_find_state_and_recover() should also try to match the
> > open_stateid.
>
> Seeing a lot of TEST_STATEID's for the invalid stateid go over the
> wire - this also makes the server hit this quite a bit:
>
> pr_warn_ratelimited("NFSD: client %s testing state ID "
> "with incorrect client ID\n", addr_str);
>
I'm not seeing that at all. Can you please elaborate on which server
errors are triggering this? I'd not expect to ever see TEST_STATEID on
a normal run.
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
