Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #189543 > unrolled thread
| Started by | Emil Flink <emil.flink@bublar.com> |
|---|---|
| First post | 2017-12-04 10:00 +0100 |
| Last post | 2017-12-04 14:30 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.user
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
| From | Emil Flink <emil.flink@bublar.com> |
|---|---|
| Date | 2017-12-04 10:00 +0100 |
| Subject | nfs4_reclaim_open_state: Lock reclaim failed! |
| Message-ID | <uSULx-2yp-9@gated-at.bofh.it> |
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.
Regards,
Emil Flink
[toc] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2017-12-04 14:30 +0100 |
| Message-ID | <uSYYN-5oz-3@gated-at.bofh.it> |
| In reply to | #189543 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web