[Bug 2059197] Re: Issue with nfs4.0 mounts after upgrade to 3.6

[Matthew Ruffell]

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

** Also affects: nfs-utils (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: nfs-utils (Ubuntu)
       Status: New => Fix Released

** Changed in: nfs-utils (Ubuntu Focal)
       Status: New => In Progress

** Changed in: nfs-utils (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: nfs-utils (Ubuntu Focal)
     Assignee: (unassigned) => Matthew Ruffell (mruffell)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2059197

Title:
  Issue with nfs4.0 mounts after upgrade to 3.6

Status in nfs-utils package in Ubuntu:
  Fix Released
Status in nfs-utils source package in Focal:
  In Progress

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions