[Bug 1964093] Re: nfsver=3,udp not working anymore

[Andreas Hasenack]

Taking a look at this, most curious:

# mount localhost:/storage /mnt -o vers=3,proto=udp
mount.nfs: an incorrect mount option was specified
root at j-nfs-dep8:~# mount localhost:/storage /mnt -v -o vers=3,proto=udp
mount.nfs: timeout set for Tue Mar  8 14:59:11 2022
mount.nfs: trying text-based options 'vers=3,proto=udp,addr=127.0.0.1'
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 127.0.0.1 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 127.0.0.1 prog 100005 vers 3 prot UDP port 58825
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified


# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  44661  status
    100024    1   tcp  40383  status
    100005    1   udp  45269  mountd
    100005    1   tcp  58873  mountd
    100005    2   udp  44744  mountd
    100005    2   tcp  41675  mountd
    100005    3   udp  58825  mountd
    100005    3   tcp  60591  mountd
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049
    100003    3   udp   2049  nfs
    100227    3   udp   2049
    100021    1   udp  33771  nlockmgr
    100021    3   udp  33771  nlockmgr
    100021    4   udp  33771  nlockmgr
    100021    1   tcp  34605  nlockmgr
    100021    3   tcp  34605  nlockmgr
    100021    4   tcp  34605  nlockmgr

-- 
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/1964093

Title:
  nfsver=3,udp not working anymore

Status in nfs-utils package in Ubuntu:
  New

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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