Comment 2 for bug 2059197

Hi Jeff,

I believe this is a valid bug. I can reproduce it:

On Focal:

$ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt
mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024
mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9'

On Jammy:

$ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt
mount.nfs4: timeout set for Wed Apr 3 00:57:08 2024
mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.213'

I apologise for introducing this particular regression when I changed the
version negotiation. Let me try and find a fix and build a test package.

In the meantime, you can use a workaround of dropping "-t nfs4" and changing
"mount" to "mount.nfs", i.e.:

$ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt
mount.nfs: timeout set for Wed Apr 3 00:51:59 2024
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.9'

I will write back shortly.

Thanks,
Matthew