Re: nfs4_reclaim_open_state: Lock reclaim failed!

From	Roberto C. Sánchez <roberto@debian.org>
Newsgroups	linux.debian.user
Subject	Re: nfs4_reclaim_open_state: Lock reclaim failed!
Date	2017-12-04 14:30 +0100
Message-ID	<uSYYN-5oz-3@gated-at.bofh.it> (permalink)
References	<uSULx-2yp-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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
> (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)
> 
 
I believe that this sounds very similar to the issue I encountered
following a jessie -> stretch upgrade of my NFS server:

https://bugs.debian.org/880549

However, I am not sure how sec=sys relates to the sec=krb5p setting that
I had determined was the culprit in my case.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

nfs4_reclaim_open_state: Lock reclaim failed! Emil Flink <emil.flink@bublar.com> - 2017-12-04 10:00 +0100
  Re: nfs4_reclaim_open_state: Lock reclaim failed! Roberto C. Sánchez <roberto@debian.org> - 2017-12-04 14:30 +0100

csiph-web