*** This bug is a duplicate of bug 2059197 ***
https://bugs.launchpad.net/bugs/2059197
Thanks for the verification, I'll mark this bug as a duplicate of that
one then.
** This bug has been marked a duplicate of bug 2059197
mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4
The proposed pkg fixes my issue!
nfs-common/focal-proposed,now 1:1.3.4-2.5ubuntu3.7 amd64 [installed]
Installed from proposed repo.
Mounted via pam_mount upon ssh login using krb5p; NFSv4 successful mount
with vers=4.0 which I could not do before upgrading from focal-updates
1:1.3.4-2.5ubuntu3.6
Andreas,
Thanks for the information! Much appreciated, I did not find that bug in my
searches for NFS related things. Will definitely give this new package a try
later today on our test server, thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think this is a dupe of #2059197, but let's wait for confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063381
Title:
NFS Client can't mount via NFS version 4.0
To manage notifications
Ryan, I think you are experiencing
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197 which
is a regression on focal from a previous update that also tried to
address the version negotiation. There is a new nfs-utils package in
focal-proposed to address that, would you mind trying it
** Description changed:
When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.
This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now
