container backup error

[jolosan]

Hello,
when I run a backup of a container it fails. I do the backup in an external 1TB USB disk.
This is the log:

NFO: starting new backup job: vzdump 104 --fleecing 0 --node pve --storage backups --notes-template '{{guestname}}' --mode stop --compress zstd --quiet 1
INFO: Starting Backup of VM 104 (lxc)
INFO: Backup started at 2024-11-28 00:00:09
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: nextcloudCT
INFO: including mount point rootfs ('/') in backup
INFO: including mount point mp0 ('/nvme1TB') in backup
INFO: stopping virtual guest
INFO: creating vzdump archive '/mnt/pve/backups/dump/vzdump-lxc-104-2024_11_28-00_00_09.tar.zst'
INFO: tar: ./var/log/journal/444d3be457d14b65a48569c433fbceca/system@0005f13a3b4cfd8b-7f7453336cd6c5ea.journal~: File shrank by 40828928 bytes; padding with zeros
INFO: Total bytes written: 111890995200 (105GiB, 124MiB/s)
INFO: restarting vm
INFO: guest is online again after 869 seconds
ERROR: Backup of VM 104 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/backups/dump/vzdump-lxc-104-2024_11_28-00_00_09.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' ./ ./nvme1TB | zstd '--threads=1' >/mnt/pve/backups/dump/vzdump-lxc-104-2024_11_28-00_00_09.tar.dat' failed: exit code 1
INFO: Failed at 2024-11-28 00:14:41
INFO: Backup job finished with errors
TASK ERROR: job errors

I dont know how to deal with the File shrank error...

Thanks in advance!

 

[dakralex]

Hi!

It seems like that the file /var/log/journal/444d3be457d14b65a48569c433fbceca/system@0005f13a3b4cfd8b-7f7453336cd6c5ea.journal~ in the container has been changed while being archived (because the tar command is run with --compare). You could either try to fsync the changes before the backup or force a log rotation for the journal with systemctl restart systemd-journald.service. If the file is invalid itself, you could also just remove it.

 

[jolosan]

Hi!

It seems like that the file /var/log/journal/444d3be457d14b65a48569c433fbceca/system@0005f13a3b4cfd8b-7f7453336cd6c5ea.journal~ in the container has been changed while being archived (because the tar command is run with --compare). You could either try to fsync the changes before the backup or force a log rotation for the journal with systemctl restart systemd-journald.service. If the file is invalid itself, you could also just remove it.

It worked!
Thank you very much for your help.
The problem I had is that I was looking in the host (/var/log/journal(), not inside the container.