When we try to Backup a container we get the following output:
I searched for
I updated proxmox to the latest version today, but the problem existed before that too.
Code:
INFO: trying to get global lock - waiting...
INFO: got global lock
INFO: starting new backup job: vzdump 107 --node node2 --remove 0 --compress zstd --storage fileserver_daily --mode snapshot
INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp40159 for temporary files
INFO: Starting Backup of VM 107 (lxc)
INFO: Backup started at 2020-08-19 13:38:18
INFO: status = running
INFO: CT Name: gaming-teamspeak
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-107-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/fileserver_daily/dump/vzdump-lxc-107-2020_08_19-13_38_18.tar.zst'
INFO: tar: ./var/cache/apt/archives/bsdutils_1%3a2.27.1-6ubuntu3.3_amd64.deb: File shrank by 43806 bytes; padding with zeros
INFO: Total bytes written: 1138483200 (1.1GiB, 6.3MiB/s)
INFO: remove vzdump snapshot
Logical volume "snap_vm-107-disk-0_vzdump" successfully removed
ERROR: Backup of VM 107 failed - command 'set -o pipefail && 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=/var/tmp/vzdumptmp40159' ./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/fileserver_daily/dump/vzdump-lxc-107-2020_08_19-13_38_18.tar.dat' failed: exit code 1
INFO: Failed at 2020-08-19 13:41:13
INFO: Backup job finished with errors
TASK ERROR: job errors
tar: ./var/..._amd64.deb: File shrank by 43806 bytes; padding with zeros
, but it seems to be only an info and not and error. But the backup for other containers without this message does not fail.I updated proxmox to the latest version today, but the problem existed before that too.