[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#726507: marked as done (nfs4_reclaim_open_state: unhandled error -10026. Zeroing state)

Your message dated Sat, 24 Apr 2021 11:45:08 -0700 (PDT)
with message-id <60846734.1c69fb81.4ef6f.9bd0@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #726507,
regarding nfs4_reclaim_open_state: unhandled error -10026. Zeroing state
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
726507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726507
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.10-0.bpo.3-amd64
Version: 3.10.11-1~bpo70+1

NFSv4 on my client froze with

	nfs4_reclaim_open_state: unhandled error -10026. Zeroing state

The server (running the same kernel) showed no incident at
this time. By now I could not reproduce the problem, though.

mount options:
# mount | grep /home
nfs-data:/space/home on /home type nfs4 (rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.19.97.128,local_lock=none,addr=172.19.96.218)

I know its a bpo kernel, but Wheezy's 3.2 kernel doesn't work on
my hardware, and using testing or unstable is not an option in
this case. Hope you don't mind?


Thanx in advance for your help
Harri

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: