Re: nfs4_reclaim_open_state: Lock reclaim failed!
- Date: Mon, 4 Dec 2017 08:28:07 -0500
- From: Roberto C. Sánchez <roberto@xxxxxxxxxx>
- Subject: Re: nfs4_reclaim_open_state: Lock reclaim failed!
On Mon, Dec 04, 2017 at 09:39:55AM +0100, Emil Flink wrote:
> 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
I believe that this sounds very similar to the issue I encountered
following a jessie -> stretch upgrade of my NFS server:
However, I am not sure how sec=sys relates to the sec=krb5p setting that
I had determined was the culprit in my case.
Roberto C. Sánchez