Public bug reported:
we want to mount with nfs 4.1 on Ubuntu 20.04, but when we run the command:
mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
it will only try version 4, the following is the log:
root@ubuntutest:~# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 12:31:23 2023
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
The only way to make it work is to specify ver=4.1:
root@ubuntutest:~# mount -o vers=4.1 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 12:31:33 2023
mount.nfs: trying text-based options 'vers=4.1,addr=x.x.x.x,clientaddr=x.x.x.x'
Now we use nfs-common version 1:1.3.4-2.5ubuntu3.5. I think it is a bug of
nfs-common package.
Normally, as a comparison, in Redhat, if we set vers=4, it will try the latest
nfs4 version 4.2, if it failed , it will try the older version until it works.
[root@zhf1smg002 ~]# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 04:37:38 2023
mount.nfs: trying text-based options
'rsize=32768,wsize=32768,vers=4.2,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'rsize=32768,wsize=32768,vers=4,minorversion=1,addr=x.x.x.x,clientaddr=x.x.x.x'
affects Ubuntu 20.04 nfs4 mount
affects nfs-common
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Package changed: pulseaudio (Ubuntu) => nfs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2049262
Title:
Cannot successfully mount the directory through nfs4 on Ubuntu 20.04
Status in nfs-utils package in Ubuntu:
New
Bug description:
we want to mount with nfs 4.1 on Ubuntu 20.04, but when we run the command:
mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
it will only try version 4, the following is the log:
root@ubuntutest:~# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 12:31:23 2023
mount.nfs: trying text-based options 'vers=4,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
The only way to make it work is to specify ver=4.1:
root@ubuntutest:~# mount -o vers=4.1 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 12:31:33 2023
mount.nfs: trying text-based options
'vers=4.1,addr=x.x.x.x,clientaddr=x.x.x.x'
Now we use nfs-common version 1:1.3.4-2.5ubuntu3.5. I think it is a bug of
nfs-common package.
Normally, as a comparison, in Redhat, if we set vers=4, it will try the
latest nfs4 version 4.2, if it failed , it will try the older version until it
works.
[root@zhf1smg002 ~]# mount -o vers=4 -vvv x.x.x.x:/sam_test /mnt
mount.nfs: timeout set for Thu Dec 28 04:37:38 2023
mount.nfs: trying text-based options
'rsize=32768,wsize=32768,vers=4.2,addr=x.x.x.x,clientaddr=x.x.x.x'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options
'rsize=32768,wsize=32768,vers=4,minorversion=1,addr=x.x.x.x,clientaddr=x.x.x.x'
affects Ubuntu 20.04 nfs4 mount
affects nfs-common
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2049262/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
