Hi!
I have been hitting my head against the wall for some time now after one of my VM's that had a NFS mount from the proxmox host start having issues that the NFS just would stall randomly without reason (i think this happend after kernel upgrade from 5.13 to 5.15 on the host)
so i did try to mount the same folder over sshfs but got the same issue.
I installed a new VM going from Ubuntu 20.04 to Ubuntu 22.04 but still same issue that NFS or SSHfs randomly hangs.
I can have a ping up from the VM to the host without losing any packages even when it drops the NFS connection and i can also access the same NFS share on secondary VM at the same time that the first one says it's unreacebal.
there is no information i any log on the host and the only thing in the vm syslog is
i have changed from virtio networking to e1000 to test, without success
and im sort of out of ideas, it was running perfectly for over a year and now i have no clue how to make it work again.
This is the version im running on the host
All help much appreciated becuase i start to lose my sanity over this.
//Ola
I have been hitting my head against the wall for some time now after one of my VM's that had a NFS mount from the proxmox host start having issues that the NFS just would stall randomly without reason (i think this happend after kernel upgrade from 5.13 to 5.15 on the host)
so i did try to mount the same folder over sshfs but got the same issue.
I installed a new VM going from Ubuntu 20.04 to Ubuntu 22.04 but still same issue that NFS or SSHfs randomly hangs.
I can have a ping up from the VM to the host without losing any packages even when it drops the NFS connection and i can also access the same NFS share on secondary VM at the same time that the first one says it's unreacebal.
there is no information i any log on the host and the only thing in the vm syslog is
Code:
Jul 18 15:41:41 X kernel: [62512.474034] nfs: server 192.168.X.3 not responding, still tryingi have changed from virtio networking to e1000 to test, without success
and im sort of out of ideas, it was running perfectly for over a year and now i have no clue how to make it work again.
This is the version im running on the host
Code:
root@pmox1:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-13
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.4.166-1-pve: 5.4.166-1
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-3
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1All help much appreciated becuase i start to lose my sanity over this.
//Ola
