Hi - I'm encountering an issue with NFS after a recent upgrade that looks similar to some threads I've seen here but not entirely. Here are the specifics and if there is any other info that may be helpful for anyone to understand the issue, please let me know:
I recently upgraded (via apt full-update) to proxmox-ve 9.0.0 (running kernel: 6.14.11-4-pve). I can share the full output of pveversion -v or any other diagnostics if helpful.
After the upgrade, the NFS mounts I had previously configured (across three hosts running in a cluster) no longer worked. Meaning that LXC guests that had those NFS storage volumes mounted encountered the following error when trying to read the filesystem:
Checking on the hosts yields the same issue.
I dropped and recreated the NFS mounts (and in doing so validate connectivity to my the NFS server) but continue to run into the same issue. The storage.cfg is fairly straightforward, two mounts of this form:
Attempting to validate manually from the pve console (via ssh) yields similar behavior:
I'd appreciate any suggestions on how to resolve this. To my knowledge, if the issue is a bug in the current version without a workaround, my options would be attempting to load a prior kernel version or re-installing proxmox entirely. Are there other approaches? If that's the case, is there a known good version that isn't subject to this issue?
I recently upgraded (via apt full-update) to proxmox-ve 9.0.0 (running kernel: 6.14.11-4-pve). I can share the full output of pveversion -v or any other diagnostics if helpful.
After the upgrade, the NFS mounts I had previously configured (across three hosts running in a cluster) no longer worked. Meaning that LXC guests that had those NFS storage volumes mounted encountered the following error when trying to read the filesystem:
Code:
ls: reading directory '.': Input/output errorChecking on the hosts yields the same issue.
I dropped and recreated the NFS mounts (and in doing so validate connectivity to my the NFS server) but continue to run into the same issue. The storage.cfg is fairly straightforward, two mounts of this form:
Code:
nfs: backup
export /mnt/north/backup
path /mnt/pve/backup
server 192.168.xx.xx
content images,backup,vztmpl,iso,rootdir,snippets
prune-backups keep-all=1Attempting to validate manually from the pve console (via ssh) yields similar behavior:
Code:
pve1 /mnt/pve ❯ mount -vvv -t nfs <ip-of-nfs-server:/mnt/north/backup test
mount.nfs: timeout set for Fri Nov 7 20:56:08 2025
mount.nfs: trying text-based options 'vers=4.2,addr=<ip-of-nfs-server>,clientaddr=<ip-of-proxmox-host>'
pve1 /mnt/pve ❯ cd test
pve1 /mnt/pve/test ❯ ls
ls: reading directory '.': Input/output errorI'd appreciate any suggestions on how to resolve this. To my knowledge, if the issue is a bug in the current version without a workaround, my options would be attempting to load a prior kernel version or re-installing proxmox entirely. Are there other approaches? If that's the case, is there a known good version that isn't subject to this issue?
