From: bfields@fieldses.org (J. Bruce Fields)
To: Emil Flink <emil.flink@bublar.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Client locks up with nfs4_reclaim_open_state: Lock reclaim failed!
Date: Mon, 4 Dec 2017 10:51:11 -0500 [thread overview]
Message-ID: <20171204155111.GC4405@fieldses.org> (raw)
In-Reply-To: <CAELMAQQGxK=2CgfqLnajhvt-ParO6WoX-gBY19Z4pN9DRaArtQ@mail.gmail.com>
On Thu, Nov 30, 2017 at 03:49:15PM +0100, Emil Flink wrote:
> Hi,
>
> I'm not sure where to go with this issue so please free to point me to
> a more suitable forum if necessary.
>
> My issue is that a client mounting a NFS share frequently locks up
> with massive amounts of "nfs4_reclaim_open_state: Lock reclaim
> failed!" in the kernel logs. Meanwhile the NFS server does not log any
> errors as far as I can tell.
>
> I only encounter this when the client is doing a lot of I/O against
> the NFS share.
>
> To recover from this I have to kill all processes on the client using
> the NFS share, unmount the NFS share and remount it.
>
> The NFS export is mounted with:
> 10.0.1.203:/nfs/lxc-office on /var/lib/lxc type nfs4
> (rw,noatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.1.231,local_lock=none,addr=10.0.1.203)
>
> Both the server and the client is running up-to-date installations of
> Debian 9 ("stretch"), meaning kernel 4.9.0-4 and nfs-common /
> nfs-kernel-server 1.3.4-2.1.
It's not a very satisfying answer, I know, but unless someone else
recognizes the issue off the top of their heads, best is probably to
install the latest upstream kernel and see if that resolves the problem,
and if so that would help narrow down where it was fixed.
Any bug is almost certainly in the kernel, so you don't need to upgrade
anything but the kernel (you can leave nfs-common/nfs-kernel-server
alone).
prev parent reply other threads:[~2017-12-04 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 14:49 Client locks up with nfs4_reclaim_open_state: Lock reclaim failed! Emil Flink
2017-12-04 15:51 ` J. Bruce Fields [this message]
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=20171204155111.GC4405@fieldses.org \
--to=bfields@fieldses.org \
--cc=emil.flink@bublar.com \
--cc=linux-nfs@vger.kernel.org \
/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.