Sanity testing the test package: https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test
nfs-common 1:1.3.4-2.5ubuntu3.6+lp2059197v20240411b1 Testcase for this bug, i.e. the regression. $ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:14:52 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:10:26 2024 mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:02 2024 mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=2 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:48 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:13:33 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo mount -t nfs4 -o vers=4,minorversion=0 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:15:54 2024 mount.nfs4: trying text-based options 'vers=4,vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' Looks OK. Testcase for the original bug, 2049262: $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:17:55 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:01 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:05 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:18:12 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.0 +4.1 +4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:40 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:47 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:20:53 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:21:02 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.0 +4.1 -4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:32 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.2 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:38 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported $ sudo umount /mnt umount: /mnt: not mounted. $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:44 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:22:49 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Looks OK. $ sudo cat /proc/fs/nfsd/versions -2 +3 +4 -4.1 -4.2 $ sudo mount -o vers=4 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:23:46 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' $ sudo umount /mnt $ sudo mount -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:23:52 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported $ sudo umount /mnt umount: /mnt: not mounted. $ sudo mount -o vers=4.0 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:24:04 2024 mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' Looks OK. The missing patch Heitor was talking about: $ sudo cat /proc/fs/nfsd/versions -2 +3 -4 -4.0 -4.1 -4.2 Previous *broken* test package without "mount.nfs: Fix auto protocol negotiation": $ sudo mount -t nfs4 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:29:19 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: Protocol not supported $ sudo mount -t nfs -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:29:25 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported It tries NFS4 only.... Heitor was correct, I need the patch. NEW test package WITH "mount.nfs: Fix auto protocol negotiation": $ sudo mount -t nfs -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Thu Apr 11 05:27:32 2024 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'addr=192.168.122.14' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.122.14 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.122.14 prog 100005 vers 3 prot UDP port 33032 mount.nfs: mount(2): Permission denied mount.nfs: access denied by server while mounting jammy-nfs-server:/ $ sudo mount -t nfs4 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Thu Apr 11 05:28:09 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: trying text-based options 'vers=4.0,addr=192.168.122.14,clientaddr=192.168.122.249' mount.nfs4: mount(2): Protocol not supported mount.nfs4: Protocol not supported -t nfs will attempt v3 also. Looks OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
