* lock reclaim failed!
@ 2015-11-13 9:22 Christoph Hellwig
2015-11-13 15:47 ` Olga Kornievskaia
2015-11-17 12:00 ` Christoph Hellwig
0 siblings, 2 replies; 4+ messages in thread
From: Christoph Hellwig @ 2015-11-13 9:22 UTC (permalink / raw)
To: linux-nfs
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!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: lock reclaim failed!
2015-11-13 9:22 lock reclaim failed! Christoph Hellwig
@ 2015-11-13 15:47 ` Olga Kornievskaia
2015-11-14 0:58 ` Jeff Layton
2015-11-17 12:00 ` Christoph Hellwig
1 sibling, 1 reply; 4+ messages in thread
From: Olga Kornievskaia @ 2015-11-13 15:47 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-nfs
On Fri, Nov 13, 2015 at 4:22 AM, Christoph Hellwig <hch@infradead.org> wrote:
> 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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: lock reclaim failed!
2015-11-13 15:47 ` Olga Kornievskaia
@ 2015-11-14 0:58 ` Jeff Layton
0 siblings, 0 replies; 4+ messages in thread
From: Jeff Layton @ 2015-11-14 0:58 UTC (permalink / raw)
To: Olga Kornievskaia; +Cc: Christoph Hellwig, linux-nfs
On Fri, 13 Nov 2015 10:47:32 -0500
Olga Kornievskaia <aglo@umich.edu> wrote:
> On Fri, Nov 13, 2015 at 4:22 AM, Christoph Hellwig <hch@infradead.org> wrote:
> > 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?
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?
--
Jeff Layton <jlayton@poochiereds.net>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: lock reclaim failed!
2015-11-13 9:22 lock reclaim failed! Christoph Hellwig
2015-11-13 15:47 ` Olga Kornievskaia
@ 2015-11-17 12:00 ` Christoph Hellwig
1 sibling, 0 replies; 4+ messages in thread
From: Christoph Hellwig @ 2015-11-17 12:00 UTC (permalink / raw)
To: linux-nfs
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-17 12:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-13 9:22 lock reclaim failed! Christoph Hellwig
2015-11-13 15:47 ` Olga Kornievskaia
2015-11-14 0:58 ` Jeff Layton
2015-11-17 12:00 ` Christoph Hellwig
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.