From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: "tibbs@math.uh.edu" <tibbs@math.uh.edu>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS: nfs4_reclaim_open_state: Lock reclaim failed! log spew
Date: Thu, 17 Nov 2016 14:32:39 -0500 [thread overview]
Message-ID: <20161117193239.GD20937@fieldses.org> (raw)
In-Reply-To: <1479404750.33885.1.camel@primarydata.com>
On Thu, Nov 17, 2016 at 05:45:52PM +0000, Trond Myklebust wrote:
> On Thu, 2016-11-17 at 11:31 -0500, J. Bruce Fields wrote:
> > On Wed, Nov 16, 2016 at 02:55:05PM -0600, Jason L Tibbitts III wrote:
> > >
> > > I'm replying to a rather old message, but the issue has just now
> > > popped
> > > back up again.
> > >
> > > To recap, a client stops being able to access _any_ mount on a
> > > particular server, and "NFS: nfs4_reclaim_open_state: Lock reclaim
> > > failed!" appears several hundred times per second in the kernel
> > > log.
> > > The load goes up by one for ever process attempting to access any
> > > mount
> > > from that particular server. Mounts to other servers are fine, and
> > > other clients can mount things from that one server without
> > > problems.
> > >
> > > When I kill every process keeping that particular mount active and
> > > then
> > > umount it, I see:
> > >
> > > NFS: nfs4_reclaim_open_state: unhandled error -10068
> >
> > NFS4ERR_RETRY_UNCACHED_REP.
> >
> > So, you're using NFSv4.1 or 4.2, and the server thinks that the
> > client
> > has reused a (slot, sequence number) pair, but the server doesn't
> > have a
> > cached response to return.
> >
> > Hard to know how that happened, and it's not shown in the below.
> > Sounds like a bug, though.
>
> ...or a Ctrl-C....
How does that happen?
--b.
next prev parent reply other threads:[~2016-11-17 19:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 21:43 NFS: nfs4_reclaim_open_state: Lock reclaim failed! log spew Jason L Tibbitts III
2016-02-25 19:58 ` J. Bruce Fields
2016-02-29 23:06 ` Jason L Tibbitts III
2016-03-01 0:48 ` J. Bruce Fields
2016-03-01 0:53 ` Jason L Tibbitts III
2016-03-01 1:01 ` J. Bruce Fields
2016-03-01 1:03 ` Jason L Tibbitts III
2016-11-16 20:55 ` Jason L Tibbitts III
2016-11-17 16:31 ` J. Bruce Fields
2016-11-17 17:08 ` Jason L Tibbitts III
2016-11-17 20:22 ` Andrew W Elble
2016-11-17 17:45 ` Trond Myklebust
2016-11-17 19:32 ` bfields [this message]
2016-11-17 19:58 ` Olga Kornievskaia
2016-11-17 20:17 ` bfields
2016-11-17 20:29 ` Olga Kornievskaia
2016-11-17 20:46 ` bfields
2016-11-17 21:05 ` Olga Kornievskaia
2016-11-17 21:26 ` bfields
2016-11-17 21:45 ` Trond Myklebust
2016-11-17 21:53 ` Olga Kornievskaia
2016-11-17 22:15 ` Trond Myklebust
2016-11-17 22:27 ` Olga Kornievskaia
2016-11-17 22:43 ` Trond Myklebust
2016-11-18 20:52 ` bfields
2016-11-18 22:44 ` Trond Myklebust
2016-11-21 18:37 ` Fields Bruce James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161117193239.GD20937@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tibbs@math.uh.edu \
--cc=trondmy@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.