NFS4 error with new Kernel 5.15.136-1-pve on PVE 7.4

[nmmn]

Error:
mount error: mount.nfs: Protocol not supported

last version which worked: 5.15.131-2

lsmod | grep -i nfs
nfsv4 839680 0
nfs 393216 1 nfsv4
lockd 110592 1 nfs
fscache 385024 1 nfs
sunrpc 581632 6 nfsv4,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs


--> NFS is now a Kernel module? On old functional Kernel, there is nothing with nfs in lsmod.

mount/storage configuration:

nfs: ISOS_HDD_CEPH
export /isos
path /mnt/pve/ISOS_HDD_CEPH
server IP.IP.IP.IP
content iso
nodes node04,node03
options vers=4.2
prune-backups keep-all=1

NFS server side information:

Ceph NFS Export.

Access Type
RW
CephFS Filesystem
name_nfs
CephFS User
nfs.name_nfs.1
Cluster
name_nfs
NFS Protocol
NFSv4
Path
/
Pseudo
/isos
Security Label
Squash
no_root_squash
Storage Backend
CephFS
Transport
TCP, UDP

pveversion -v

proxmox-ve: 7.4-1 (running kernel: 5.15.136-1-pve)
pve-manager: 7.4-17 (running version: 7.4-17/513c62be)
pve-kernel-5.15: 7.4-10
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.136-1-pve: 5.15.136-1
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.4.203-1-pve: 5.4.203-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx4
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.4-1
proxmox-backup-file-restore: 2.4.4-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+2
pve-firewall: 4.3-5
pve-firmware: 3.6-6
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1

 

[bbgeek17]

What does "cat /proc/fs/nfsd/versions" return on NFS server?
Did you try without vers=4.2 - what did the client/server negotiate?
Can you boot into old kernel and report working and none versions of kernel, packages, etc You can try mounts directly from command line for clarity.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[nmmn]

What does "cat /proc/fs/nfsd/versions" return on NFS server?
--> File not existing (Ceph only Support NFSv4)

Did you try without vers=4.2 - what did the client/server negotiate?

4, 4.1 and 4.2 are not working

Can you boot into old kernel and report working and none versions of kernel, packages, etc You can try mounts directly from command line for clarity.

--> Old Kernel is working fine.

 

[nmmn]

Now i have done an upgrade on 2 Clusters to Proxmox 8 and NFS is working again. (kernel 6.5.11-8-pve)

Still have one cluster for Testing.

 

[nmmn]

mounting manual, same error:

mount -t nfs -o vers=4.2 IP:/isos /mnt/pve/ISOS_HDD_CEPH/
mount -t nfs -o vers=4.1 IP:/isos /mnt/pve/ISOS_HDD_CEPH/
mount -t nfs -o vers=4 IP:/isos /mnt/pve/ISOS_HDD_CEPH/

--> mount error: mount.nfs: Protocol not supported

 

[bbgeek17]

You can check whether there are any differences in the output of "grep NFS /boot/config-$(uname -r)", I suspect there wont be.
You can also add "-v" to manual mount to see if more information becomes available.

Collect your data and report it in Bugzilla if its something you wish to pursue. Make sure its in an orderly fashion and clearly labeled.

Good luck

PS additional info
https://unix.stackexchange.com/questions/205529/nfs-mount-nfs-protocol-not-supported

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox