I`m often using Proxmox in my classic setup, 2 nodes with 1 VM, 1/24h backup to NAS via NFS or CIFS. NASes are added for all nodes via storage menu in Datacenter.
And there is a problem. Sometimes node lost connection with NAS and VM is going to be locked and unavailable.
I have to restart node or I can try to reconnect to NFS or CIFS share.
Can I defend VM against these connection breakdown? Why are nodes so sensitive for this mounted disks? Is there better and more reliable solution for me?
I didn`t remeber such problems in older version of Proxmox (v5,6 maybe 7), but I had the several issues in various v8 clusters for sure.
This night I had a problem with space in NAS during backup and VM is frozen but sometimes node has no reason to lost connection with NAS. Only 1 node lost connection with NAS in this case.
And there is a problem. Sometimes node lost connection with NAS and VM is going to be locked and unavailable.
I have to restart node or I can try to reconnect to NFS or CIFS share.
Can I defend VM against these connection breakdown? Why are nodes so sensitive for this mounted disks? Is there better and more reliable solution for me?
I didn`t remeber such problems in older version of Proxmox (v5,6 maybe 7), but I had the several issues in various v8 clusters for sure.
This night I had a problem with space in NAS during backup and VM is frozen but sometimes node has no reason to lost connection with NAS. Only 1 node lost connection with NAS in this case.
Nov 22 00:00:01 pve2 pvescheduler[1858641]: Warning: unable to close filehandle GEN76 properly: No space left on device at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 271.
Nov 22 00:00:02 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:02 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:02 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:05 pve2 pvescheduler[1858641]: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - got timeout
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Nov 22 00:00:06 pve2 systemd[1]: Starting logrotate.service - Rotate log files...
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Nov 22 00:00:06 pve2 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:06 pve2 kernel: CIFS: VFS: No writable handle in writepages rc=-9
Nov 22 00:00:07 pve2 systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Last edited: