> Looks like if I want to keep using UDP I'll need to stick with 20.04
for now, but it would be nice if it weren't disabled in 22.04.
Yea, same here. I've ended up here trying to update to 22.04 but not
that big of a need, just trying to be proactive.
--
You received this bug notification
I've run into this issue when using NFS mounts via Vagrant which uses NFSv3 and
UDP by default. Relevant issues:
https://github.com/hashicorp/vagrant/issues/12758
https://github.com/hashicorp/vagrant/issues/13078
Vagrant can be forced to use TCP to work around the issue, but UDP is preferred
Thanks much,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
Status in linux package in Ubuntu:
Confirmed
Bug description:
Package:
yes, I confirm. You cannot mount nfs3 shares over udp served by your
SPARCstation with 22.04 as client running the standard kernel due to the
option CONFIG_NFS_DISABLE_UDP_SUPPORT=y.
I don't know what would be necessary to add nfs3-udp to the kernel.
Maybe changing
I've encountered same problem after 22.04 upgrade. I want to mount
shares from SPARCstation 10 based SunOS 4.1.4 system on the 22.04 system
but cannot. It does work in the other direction, ie. I can mount 22.04
shares on the Sun.
If you could confirm my understanding that recompiling the Kernel
** Tags removed: server-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
Status in linux package in Ubuntu:
Confirmed
Bug
yes, this was a typo... of course I meant disabled UDP NFS mounting.
And regarding the 2nd point we have the same understanding.
So since "old" clients are still able to mount the NFS shares via nfs3 over udp
on jammy servers, I would not flip the kernel config
CONFIG_NFS_DISABLE_UDP_SUPPORT
> This disabled NFS3 support seems only to affect the client part of
the kernel-module.
NFSv3 is fine, it's udp that is disabled in the kernel (I think you
understood that, and above is just a typo, but clarifying nonetheless).
Clients running a kernel with CONFIG_NFS_DISABLE_UDP_SUPPORT=y
I am currently very confused. I restored the snapshots of my test VMs
from yesterday and now I can mount the NFS-shares on the jammy server on
all clients (Knoppix, Ubuntu 18.04) with nfs3+udp after putting "udp=y"
in /etc/nfs.conf, also with the last kernel version 5.15.0-18.
Yesterday in all my
Are you sure it's using udp? Did you confirm with /proc/mounts or mount
output? I didn't get it to work, not even with a focal server, and the
kernel option disabling UDP sounds very adamant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I added this to the Jammy 22.04 release notes at
https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
If it's decided to flip this option before release, please remove that
release notes remark.
--
You received this bug notification because you are a member of Kernel
Packages,
I just updated linux-image-5.15.0-18-generic to today's new version
linux-image-5.15.0-22-generic.
Now with enabling "udp=y" in /etc/nfs.conf and the new kernel version I can
mount
the nfs-share on the jammy server from the koppix pxe initdrd (busybox mount)
with nfs version 3 and udp.
Only
This was first disabled on groovy, the first ubuntu release after focal:
root@g1:~# grep NFS /boot/config-5.8.0-59-generic |grep UDP
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
The upstream help text next to that kernel option says:
"""
Choose Y here to disable the use of NFS over UDP. NFS over UDP
on
Found this in /boot/config-$(uname -r):
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964093
Title:
nfsver=3,udp not working anymore
Status in linux
I restored nfs-utils 1.x in the jammy client, and tried to mount again.
It still fails. I don't think this is an nfs-utils problem:
ubuntu@j-nfs-dep8:~$ dpkg -l|grep nfs
ii libnfsidmap2:amd64 0.25-6build1 amd64
NFS idmapping library
ii nfs-common
15 matches
Mail list logo
