[Bug 1214540] New: NFS mount doesn't succeed any more
https://bugzilla.suse.com/show_bug.cgi?id=1214540 Bug ID: 1214540 Summary: NFS mount doesn't succeed any more Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: lopa@mailbox.org QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- After one of the last Tumbleweed updates, the nfs kernel server doesn't work correctly any more. An nfs mount command from another machine doesn't return, it hangs forever and nothing is mounted. Old working configuration ------------------------- nfs-client-2.6.2-38.1 nfs-kernel-server-2.6.2-38.1 Syslog: Aug 23 17:08:36 orion rpc.mountd[19233]: v4.0 client attached: 0x131b2e4a64e620dc from "192.168.1.21:991" The mount command on the client machine returns immediately and the remote directory is mounted correctly. New non working configuration ----------------------------- nfs-client-2.6.3-39.4 nfs-kernel-server-2.6.3-39.4 Syslog: Aug 23 16:47:37 orion rpc.mountd[18307]: auth_unix_ip: inbuf 'nfsd 192.168.1.21' Aug 23 16:47:37 orion rpc.mountd[18307]: successful authentication for IP 192.168.1.21 as 192.168.1.0/24 Aug 23 16:47:37 orion rpc.mountd[18307]: auth_unix_ip: client 0x5619032d0770 '192.168.1.0/24' Aug 23 16:47:37 orion rpc.mountd[18307]: v4.0 client attached: 0x131b2e4764e61c00 from "192.168.1.21:717" Aug 23 16:47:37 orion rpc.mountd[18307]: nfsd_fh: inbuf '192.168.1.0/24 1 \x00000000' Aug 23 16:47:37 orion rpc.mountd[18307]: nfsd_fh: found 0x5619032d2410 path / The mount command on the client machine doesn't return and nothing is mounted. After killing the mount command, this line appears in the servers syslog: Aug 23 16:53:55 orion rpc.mountd[18307]: v4.0 client detached: 0x131b2e4764e61c00 from "192.168.1.21:717" There's no difference, whether NFSv4 or NFSv3 is used and there's no message in the syslog of the client machine. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1214540 https://bugzilla.suse.com/show_bug.cgi?id=1214540#c23 Janos Miko <mixe3y@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mixe3y@gmail.com --- Comment #23 from Janos Miko <mixe3y@gmail.com> --- Hello, I'm not sure if this is related or not, but it seems like the latest nfs-client update broke the nfs client in some cases. Context: I'm running multiple Kubernetes clusters on top of OpenSUSE MicroOS using the following Terraform module: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner I'm using Rancher Longhorn for volumes in the cluster and Longhorn's RWX volumes are using nfs under the hood. Yesterday, a transactional-update scheduled update upgraded all my nodes (including nfs-client package from 2.6.3-39.4 to 2.6.3-39.5) and the RWX volumes started to fail. The error message was the following in the journal: --- Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting command: /usr/local/sbin/nsmounter Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting arguments: mount -t nfs -o vers=4.1,noresvport,intr,hard 10.43.207.185:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount Oct 11 07:42:23 dev-worker-1-autoscaled-small-19baf778f50efd8c k3s[1294]: Output: mount.nfs: Protocol not supported for 10.43.207.185:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c on /var/lib/kubelet/plugin --- I also enabled debug logging in the kernel, you can find those logs in the related bug report. Anyway, after a few hours I decided to use MicroOS rollback going back to the latest snapshot from 2 days ago and the issue is solved now on that node. Related bug report on Github: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/1016 Please let me know if I can provide you any additional information about this issue. Regards, Janos Miko -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com