LXC restore error in 4.0-48

klauskurz

Renowned Member
Mar 8, 2013
12
5
68
Hi!

I did a container backup and then a restore.

There is the following error:


Code:
Formatting '/var/lib/vz/images/1002/vm-1002-disk-1.raw', fmt=raw size=10485760
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks:  1024/10240           done                            
Creating filesystem with 10240 1k blocks and 2560 inodes
Filesystem UUID: 5678a725-035a-4a1e-9c16-23586c5a6f01
Superblock backups stored on blocks: 
    8193


Allocating group tables: 0/2   done                            
Writing inode tables: 0/2   done                            
Creating journal (1024 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/2   done


extracting archive '/mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo'
tar: ./usr/share/man/fr/man8/dpkg-reconfigure.8.gz: Cannot write: No space left on device
tar: ./usr/share/man/fr/man8/update-passwd.8.gz: Cannot write: No space left on device
....
....
tar: ./opt/observium/LICENSE: Cannot open: No such file or directory
Total bytes read: 1772206080 (1.7GiB, 303MiB/s)
tar: Exiting with failure status due to previous errors
command 'tar xpf /mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo --numeric-owner --totals --sparse -C /var/lib/lxc/1002/rootfs --anchored --exclude './dev/*'' failed: exit code 2

Is there anything that I can do here, to make the restore work?

Best regards
Klaus
 
Try to specify/overwrite the container size with --rootfs option:

# pct restore 1002 /mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo --rootfs local:4

which use 4GB on storage 'local'.

I wonder why the original size is only 1GB? It this a backup from beta1?
 
Try to specify/overwrite the container size with --rootfs option:
# pct restore 1002 /mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo --rootfs local:4
which use 4GB on storage 'local'.

I wonder why the original size is only 1GB? It this a backup from beta1?

Thank you for the quick and perefect answer. The restore now worked.

# pct restore 1002 /mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo --rootfs local:4

I did some investigation:

The backup was from: 2015_10_18-12_38_32. Never had a beta installed.

# tar -xf /mnt/pve/h01-backup-01/dump/vzdump-lxc-10001-2015_10_18-12_38_32.tar.lzo ./etc/vzdump/pct.conf
# cat ./etc/vzdump/pct.conf

Code:
arch: amd64
cpulimit: 4
cpuunits: 1024
hostname: v02
memory: 2048
nameserver: 172.18.1.1
net0: bridge=vmbr0,hwaddr=0A:94:64:FE:38:B1,name=eth0,type=veth
ostype: ubuntu
rootfs: local:10001/vm-10001-disk-1.raw,size=10M
swap: 512

There is indeed a "size=10M"

There was another backup, just after the first:

# tar -xf /mnt/pve/h01-backup-01/dump/vzdump-lxc-40008-2015_10_18-12_40_40.tar.lzo ./etc/vzdump/pct.conf
# cat ./etc/vzdump/pct.conf

Code:
arch: amd64
cpulimit: 8
cpuunits: 1024
hostname: v08
memory: 8192
net0: bridge=vmbr0,gw=172.18.1.1,hwaddr=AE:E5:10:14:76:73,ip=172.18.1.18/24,name=eth0,type=veth
ostype: ubuntu
rootfs: local:40008/vm-40008-disk-1.raw,size=4G
swap: 8704

Here the size seems to be OK.

Please let me know, if you need more debugging here.
 

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!