[SOLVED] No space left while recovering

[Andrey Yumashev]

[ Thu Jan 07, 10:46:09 | root@yls2:~ ] # pct restore 107 vzdump-openvz-107-2016_01_05-14_22_06.tar.gz --storage YLS2D0
Formatting '/mnt/pve/YLS2D0/images/107/vm-107-disk-1.raw', fmt=raw size=21474836480
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 95cef709-8c02-494e-8eee-a449286fde74
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000

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

extracting archive '/root/vzdump-openvz-107-2016_01_05-14_22_06.tar.gz'
tar: ./root/.local: Cannot mkdir: No space left on device
tar: ./root/.local: Cannot mkdir: No space left on device
.....more errors....
Total bytes read: 21070704640 (20GiB, 75MiB/s)
tar: Exiting with failure status due to previous errors
command 'tar xpf /root/vzdump-openvz-107-2016_01_05-14_22_06.tar.gz --totals --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-xattr-write' -C /var/lib/lxc/107/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

while trying to recover OpenVZ disk image
Disks are full of space:

[ Thu Jan 07, 10:52:14 | root@yls2:~ ] # df -ih
Filesystem          Inodes IUsed IFree IUse% Mounted on
udev                   18M   508   18M    1% /dev
tmpfs                  18M   731   18M    1% /run
rpool/ROOT/pve-1      1.3G   96K  1.3G    1% /
tmpfs                  18M   105   18M    1% /dev/shm
tmpfs                  18M    22   18M    1% /run/lock
tmpfs                  18M    17   18M    1% /sys/fs/cgroup
rpool                 1.3G     7  1.3G    1% /rpool
rpool/ROOT            1.3G     7  1.3G    1% /rpool/ROOT
tmpfs                  18M    11   18M    1% /run/lxcfs/controllers
cgmfs                  18M    13   18M    1% /run/cgmanager/fs
/dev/fuse             9.8K    66  9.8K    1% /etc/pve
/dev/md0               59M    18   59M    1% /mnt/md0
172.16.5.2:/mnt/md0    59M    18   59M    1% /mnt/pve/YLS2D0
[ Thu Jan 07, 10:56:09 | root@yls2:~ ] # df -h
Filesystem           Size  Used Avail Use% Mounted on
udev                  10M     0   10M   0% /dev
tmpfs                 29G  9.0M   29G   1% /run
rpool/ROOT/pve-1     776G  149G  628G  20% /
tmpfs                 71G   60M   71G   1% /dev/shm
tmpfs                5.0M     0  5.0M   0% /run/lock
tmpfs                 71G     0   71G   0% /sys/fs/cgroup
rpool                628G     0  628G   0% /rpool
rpool/ROOT           628G     0  628G   0% /rpool/ROOT
tmpfs                100K     0  100K   0% /run/lxcfs/controllers
cgmfs                100K     0  100K   0% /run/cgmanager/fs
/dev/fuse             30M   32K   30M   1% /etc/pve
/dev/md0             917G   72M  871G   1% /mnt/md0
172.16.5.2:/mnt/md0  917G   72M  871G   1% /mnt/pve/YLS2D

ls -lha | grep vzd
-rw-r--r--  1 root root  16G Jan  6 23:46 vzdump-openvz-107-2016_01_05-14_22_06.tar.gz

What i am doing wrong? If i try to untar the archive with the command above all is OK! Is there any way to do step-by-step recover?

 

[Andrey Yumashev]

Okay, finally i solved it.

Reason was that the backup made by the Proxmox 3 was really strange.

I found that the disk size of my virt was 20G and backup is bigger:

/dev/loop6            20G  20G   0G  0% /var/lib/lxc/107/rootfs

this is quote from watching df -h at moment when error appeared

I studied the google and man and finally

[ Thu Jan 07, 16:45:12 | root@yls2:~ ] # pct restore 107 vzdump-openvz-107-2016_01_05-14_22_06.tar.gz --storage YLS2D1 --rootfs YLS2D1:107,size=30G --force

solved the problem