LCX backup causes lock up

dvdwsn

Member
Jul 29, 2022
20
1
8
I have an NFS mount in Storage that I use for my backups. When I backup my VMs to it, everything works fine. When I try to initiate a backup of a CT, the host (pve node) sort of locks up. The CT and its nested docker containers are unresponsive, the PVE gui stops working properly, although the VMs are still working.

INFO: starting new backup job: vzdump 101 --notes-template '{{guestname}} test2' --node pve1 --compress zstd --storage omv-nas --mode snapshot --remove 0 INFO: Starting Backup of VM 101 (lxc) INFO: Backup started at 2023-04-09 22:18:02 INFO: status = running INFO: CT Name: Docker INFO: including mount point rootfs ('/') in backup INFO: excluding volume mount point mp0 ('/mnt') from backup (disabled) INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: create storage snapshot 'vzdump'
At this point the CT was locked up and I had to restart the host, then pct unlock 101 to get things working again.

Before this test backup I added a mount point to the CT with a path of /mnt, since I have some SSHFS mounts in that path that I wanted excluded.
The previous backup test also failed, but at least didn't mess up the host.
INFO: starting new backup job: vzdump 101 --node pve1 --compress zstd --notes-template '{{guestname}} test' --storage omv-nas --remove 0 --mode snapshot INFO: Starting Backup of VM 101 (lxc) INFO: Backup started at 2023-04-09 22:14:46 INFO: status = running INFO: CT Name: Docker INFO: including mount point rootfs ('/') in backup INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: create storage snapshot 'vzdump' failed to open /mnt/media: Permission denied failed to open /mnt/config: Permission denied WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full. Logical volume "snap_vm-101-disk-0_vzdump" created. WARNING: Sum of all thin volume sizes (1.11 TiB) exceeds the size of thin pool ssd1/ssd1 and the size of whole volume group (<476.94 GiB). INFO: creating vzdump archive '/mnt/pve/omv-nas/dump/vzdump-lxc-101-2023_04_09-22_14_46.tar.zst' INFO: tar: /mnt/pve/omv-nas/dump/vzdump-lxc-101-2023_04_09-22_14_46.tmp: Cannot open: No such file or directory INFO: tar: Error is not recoverable: exiting now INFO: cleanup temporary 'vzdump' snapshot Logical volume "snap_vm-101-disk-0_vzdump" successfully removed ERROR: Backup of VM 101 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/mnt/pve/omv-nas/dump/vzdump-lxc-101-2023_04_09-22_14_46.tmp' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd --rsyncable '--threads=1' >/mnt/pve/omv-nas/dump/vzdump-lxc-101-2023_04_09-22_14_46.tar.dat' failed: exit code 2 INFO: Failed at 2023-04-09 22:14:47 INFO: Backup job finished with errors TASK ERROR: job errors
The issue here seems to be that it couldn't create the .tmp file for the vzdump.

The VM and CT backups use Snapshot.
If I backup the CT to the local disk, it works fine.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!