[Bug 1956787] [NEW] nfs v3 locking fails - rpc-statd not started after minor upgrade

Launchpad Bug Tracker 1956787 at bugs.launchpad.net
Tue Jan 11 17:44:51 UTC 2022


You have been subscribed to a public bug:

We just upgraded our nfs servers from 5.4.0-72 to 5.4.0-92.

We are using NFS v3 in a large computer science department, with several
hundred clients.

Lots of applications are now failing because locks don't work.

/var/log/syslog on the client reports lockd not responding. tcpdump
shows that the client tries to connect to lockd but there is no response
to the TCP SYN.

netstat on the server shows some connections open, with lots of bytes in
the receive queue.

The problem probably occurs only with lots of clients. I believe any
typical test would work fine.

The problem is new. That is, it didn't happen in 5.4.0-72.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: kernel-common (not installed)
ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
Uname: Linux 5.4.0-92-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jan  7 13:07:34 2022
InstallationDate: Installed on 2020-10-14 (450 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: kernel-package
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-10-14T13:53:33.474467

** Affects: nfs-utils (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug focal uec-images
-- 
nfs v3 locking fails - rpc-statd not started after minor upgrade
https://bugs.launchpad.net/bugs/1956787
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.



More information about the foundations-bugs mailing list