Hello,

I should add some clarification after reviewing my initial report.

While the debian bug is apparently observed without the client being in
suspend state, for us the problem happened shortly after or directly
after (I cannot establish the exact timeline) the client waking up from
suspend. I am not sure if there is a causal connection. Also, as
reported I observe always the "... testing state ID with incorrect
client ID" message after an ubuntu 18.04 client wakes up from suspend. I
am not sure if there is a causal connection to the "RPC request reserved
..." message and the NFS becoming unusable on the client. This might be
correlation.

Regards

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1785788

Title:
  NFS breaks after wake from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I am observing all symptoms of debian bug 898060 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898060) on ubuntu bionic 
4.15.0-23-generic x86_64 clients
  with a Centos7 NFS server (3.10.0-693.21.1.el7.x86_64).

  After a wake from suspend the server always logs
  kernel: NFSD: client 2001:638:redacted testing state ID with incorrect client 
ID
  which is not observed with ubuntu 16.04 (kernel 4.4) clients. Sporadically 
after wake from suspend (takes days to weeks to trigger) the server logs are 
flooded with messages of the type
  kernel: RPC request reserved 84 but used 276
  and NFS on the client does not work any more. This also has not been observed 
with our 20 or so ubuntu 16.04 NFS clients in the last two years.

  Rebooting the client appears to stop the log flooding on the server
  and NFS works normally after the reboot. Remark: systemd hangs during
  shutdown, presumably waiting for the NFS mount to stop, the power
  button is the only remaining option.

  I will upgrade to the latest bionic kernel later and try to trigger
  this again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785788/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to