Public bug reported:
Hello,
On Ubuntu Server 20.04.6 LTS with the update of nfs-common package =>
"nfs-common/focal-updates 1:1.3.4-2.5ubuntu3.5" to "nfs-common/focal-
updates 1:1.3.4-2.5ubuntu3.6" I started having issues mounting ntf4.0
volumes. The NFS server supports 4.0, 4.1 and 4.2
The issue appears when using '-t ntfs4' and setting the version using -o
vers=.
When using 1:1.3.4-2.5ubuntu3.5 I am able to use '-o vers' to set the version
when using -t ntfs4 eg
mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test
mount.nfs4: trying text-based options
'vers=4.0,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx'
mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test
mount.nfs4: trying text-based options
'vers=4.1,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx'
However after upgrading to 1:1.3.4-2.5ubuntu3.6 it always mounts as nfs4.2
mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test
mount.nfs4: trying text-based options
'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx'
mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test
mount.nfs4: trying text-based options
'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx'
I would have expected the specified version in -o vers to be used when
using '-t nfs4'
When using '-t nfs' I am able to mount volumes as nfs 4.0. I understand
that 1:1.3.4-2.5ubuntu3.6 fixes version negotiation so maybe this isn't
a bug and the intent with '-t nfs4' is to always use the highest
version. If so please feel free to close the report
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
--
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:
Issue with nfs4.0 mounts after upgrade to 3.6
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
