I am currently very confused. I restored the snapshots of my test VMs from yesterday and now I can mount the NFS-shares on the jammy server on all clients (Knoppix, Ubuntu 18.04) with nfs3+udp after putting "udp=y" in /etc/nfs.conf, also with the last kernel version 5.15.0-18.
Yesterday in all my tests the udp=y param was ignored, only the vers=? params had an effect after restarting the nfs-kernel-server. My only explanation for now is a problem with the internal network between my VirtualBox Test VMs. Sorry, I know this sounds very strange. But despite of the kernel config option CONFIG_NFS_DISABLE_UDP_SUPPORT=y I can mount the NFS-shares on the jammy server with nfs3+udp from every test client VM. /proc/mounts shows: vers=3 and proto=udp Only on the server itself I cannot mount with nfs3+udp. mount -o vers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt leads to mount.nfs: an incorrect mount option was specified but mount -o vers=3,tcp 192.168.0.1:/srv/nfs/testshare /mnt is working. So conclusion for me now. The /etc/nfs.conf params are working correctly and my nfs3+udp problem is solved. But nfs3+udp should not be possible to be enabled with respect to the kernel param. This disabled NFS3 support seems only to affect the client part of the kernel-module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964093 Title: nfsver=3,udp not working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
