lock reclaim failed!
Subsystems (2)
I see the following running xfstestst on latest Linus' tree against as sever from the same tree:
generic/089 [ 2000.358405] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
[ 2001.769939] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2001.770732] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2122.608136] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
Quoted 7 lines · Christoph Hellwig
I see the following running xfstestst on latest Linus' tree against as sever from the same tree:
generic/089 [ 2000.358405] NFS:
nfs4_reclaim_open_state: Lock reclaim failed![ 2001.769939] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2001.770732] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2122.608136] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
Going against the NetApp server, we have seen this error logged when the server returned BAD_STATEID to the IO on the delegated stateid. Is there such error on the network trace?
Quoted 4 lines · On Fri, 13 Nov 2015 10:47:32 -0500 Olga Kornievskaia <[email protected]> wrote:
Quoted 3 lines · Christoph Hellwig
I see the following running xfstestst on latest Linus' tree against as sever from the same tree:
Quoted 8 lines
Quoted 4 lines
generic/089 [ 2000.358405] NFS:
nfs4_reclaim_open_state: Lock reclaim failed![ 2001.769939] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2001.770732] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [ 2122.608136] NFS: nfs4_reclaim_open_state: Lock reclaim failed!Going against the NetApp server, we have seen this error logged when the server returned
BAD_STATEIDto the IO on the delegated stateid. Is there such error on the network trace?
Yes, a capture is probably the best way to tell what's really going on.
I just tried generic/test089 a couple of times on the fedora kernel here (on both server and client) and didn't see that pop:
http://koji.fedoraproject.org/koji/buildinfo?buildID=699182
What's the top commit of your kernel? I assume that the server didn't restart or anything, right?
Signature · 1 line
Jeff Layton <[email protected]>
I've tried for a couple days to reproduce this issue, but failed. Looks like this was just a one off - sorry for the noise.