[SOLVED] vzdump hang up with offline nfs storage

[informant]

hi, if a storage was mounted with nfs and a backup is running, storage goes offline (power lost for exsample), vzdump is hang up, prozess can not be kill, not stop in web gui and not with kill -9 pid

pve-manager/7.2-11/b76d3178

any ideas for fix or is a bug in main software for proxmox team?

complete vm whats backup is hang up and cant start normal, unlock dont work, reset not work, is hang total here...

regards

Spoiler: pveversion -v

pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-13
pve-kernel-helper: 7.2-13
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.4.157-1-pve: 5.4.157-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
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-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
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.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

same in newest version, too^^

 

[VictorSTS]

That's not a bug, that is how NFS works.

If you setup your NFS mount from Proxmox GUI, it will set it up with option "hard". For example:

192.168.0.11:/volume1/Proxmox_Backup on /mnt/pve/NFS_Backup type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,[B]hard[/B],proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.1,local_lock=none,addr=192.168.0.11)

"Hard" option will force every process that requests access to the NFS server to be placed in "D" state (uninterrumpable sleep) until the NFS servers replies back to the request. If the NFS server is running ok, that time is short but when the NFS server is unavailable the process may stay in un-killable state forever (until server reboot). The advantage of the "hard" option is that when the NFS server comes back online the request can continue as if nothing had happend. In practice that does not happend as often as I would like it to.

An alternative is to manually mount the NFS share to a local path in your server using "soft" instead of "hard" and from Proxmox GUI configure that path as a directory storage and manually set the "is_mountpoint 1" option in storage.cfg:

https://forum.proxmox.com/threads/problem-with-storage-directory.73928/post-332394

 

[informant]

Ah ok, thanks for this information. than it was clear. but i mean, if backup hang up why storage unavailable, after a time x its better to stop backup automatical and resume vm online. hope proxmox team can use this as feedback and wish.
best regards

 

[VictorSTS]

Not even the kernel can stop or kill a process in "D" state, so there's no way to do what you are requesting. Use "soft" mount option and understand its implications.