LXC Backup Error

simonwood

New Member
Sep 6, 2020
1
0
1
44
Hello everyone!

I am trying to Backup my LCXs but none out of 3 works.

What I found out so far: Due to a technichal issue I lost my old Proxmox Setup with all LXC config files in /etc/pve/lxc
The containers itself were on another HDD so I manually recreated the LXC-config files and were able to boot the CTs again within a new Proxmox installation.

I also created a new test CT. The backup works fine then. So only the old, manually reconfiged and restored CTs don't work.

Maybe someone knows what to do. Thank you very much in advance!
Simon


concerning the storage space warning: Usage 56.67% (452.63 GiB of 798.71 GiB)

Code:
INFO: starting new backup job: vzdump 103 --storage local-old --node pve --compress zstd --remove 0 --mode snapshot

INFO: Starting Backup of VM 103 (lxc)

INFO: Backup started at 2020-10-13 12:11:05

INFO: status = running

INFO: CT Name: PiHole

INFO: including mount point rootfs ('/') in backup

INFO: backup mode: snapshot

INFO: ionice priority: 7

INFO: create storage snapshot 'vzdump'

  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-103-disk-0_vzdump" created.

  WARNING: Sum of all thin volume sizes (894.00 GiB) exceeds the size of thin pool pve_old/data and the amount of free space in volume group (<8.00 GiB).

INFO: creating vzdump archive '/old/var/lib/vz/dump/vzdump-lxc-103-2020_10_13-12_11_05.tar.zst'

INFO: tar: ./usr/lib/x86_64-linux-gnu/libmpfr.so.6.0.1: File shrank by 244752 bytes; padding with zeros

INFO: tar: ./usr/lib/x86_64-linux-gnu/libmenu.so.5.9: File shrank by 18704 bytes; padding with zeros

INFO: tar: ./usr/lib/x86_64-linux-gnu/perl-base/unicore/lib/Sc/Knda.pl: Read error at byte 0, while reading 630 bytes: Input/output error

INFO: tar: ./usr/lib/x86_64-linux-gnu/perl-base/unicore/lib/Perl/XPosixPu.pl: Read error at byte 0, while reading 2283 bytes: Input/output error

INFO: tar: ./usr/lib/x86_64-linux-gnu/libformw.so.5.9: File shrank by 40168 bytes; padding with zeros

INFO: tar: ./usr/bin/xvidtune: File shrank by 36264 bytes; padding with zeros

INFO: Total bytes written: 1528545280 (1.5GiB, 18MiB/s)

INFO: tar: Exiting with failure status due to previous errors

INFO: remove vzdump snapshot

  Logical volume "snap_vm-103-disk-0_vzdump" successfully removed

ERROR: Backup of VM 103 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=/old/var/lib/vz/dump/vzdump-lxc-103-2020_10_13-12_11_05.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' >/old/var/lib/vz/dump/vzdump-lxc-103-2020_10_13-12_11_05.tar.dat' failed: exit code 2

INFO: Failed at 2020-10-13 12:12:31

INFO: Backup job finished with errors

TASK ERROR: job errors
 
Last edited:
Hi,

I guess you have a disk problem.
The error indicates that not all files can be read.
I would try to copy the image to a new disk and try here to backup.

you can use qemu-img for this.
 

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!