Restore backup failed for timeout

x-cash

New Member
Mar 8, 2014
2
0
1
The configuration:

Code:
root@proxmox1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-45 (running version: 3.1-45/b282dec2)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

root@proxmox1:~# df -H
Filesystem                Size  Used Avail Use% Mounted on
udev                       11M     0   11M   0% /dev
tmpfs                     805M  426k  804M   1% /run
/dev/mapper/pve-root      102G  1.3G   96G   2% /
tmpfs                     5.3M     0  5.3M   0% /run/lock
tmpfs                     1.7G   23M  1.6G   2% /run/shm
/dev/mapper/pve-data      1.9T   12G  1.9T   1% /var/lib/vz
/dev/sda1                 519M   60M  433M  13% /boot
/dev/mapper/second-extra  1.9T   17G  1.8T   1% /mnt/extra
/dev/fuse                  32M   13k   32M   1% /etc/pve

Backup


I did a normal snapshot lzo backup of vm 100 on the 'extra' storage (it's an lvm volume mounted at /mnt/extra)

Code:
root@proxmox1:~# ls -l /mnt/extra/dump/
-rw-r--r-- 1 root root        3966 Mar  8 16:34 vzdump-qemu-100-2014_03_08-16_30_45.log
-rw-r--r-- 1 root root  5915207790 Mar  8 16:34 vzdump-qemu-100-2014_03_08-16_30_45.vma.lzo


all ok

The problem with restore:


Doing a Restore on same storage ('extra') of that backup i get the following error:

Code:
restore vma archive: lzop -d -c /mnt/extra/dump/vzdump-qemu-100-2014_03_08-16_30_45.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp4460.fifo - /var/tmp/vzdumptmp4460
CFG: size: 244 name: qemu-server.conf
DEV: dev_id=1 size: 161061273600 devname: drive-ide0
CTIME: Sat Mar  8 16:30:47 2014
TASK ERROR: command 'lzop -d -c /mnt/extra/dump/vzdump-qemu-100-2014_03_08-16_30_45.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp4460.fifo - /var/tmp/vzdumptmp4460' failed: command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /mnt/extra/images/101/vm-101-disk-1.qcow2 157286400K' failed: got timeout

Reading here in the forum i tried decompressing the lzo file with:

Code:
lzop -d /mnt/extra/dump/vzdump-qemu-100-2014_03_08-16_30_45.vma.lzo

I ended up with a file as expected:

Code:
-rw-r--r-- 1 root root 10356096000 Mar  8 16:30 vzdump-qemu-100-2014_03_08-16_30_45.vma

Now if i Restore it (via GUI) it all goes well!

This is a fresh PVE installation upgraded to last from respository.

Seems something weird happens in the lzop pipe...
 
It seems this problem doesn't happen when using path on different drives. I was restoring on the same physical drive. Today I tried restoring on a different drive and it worked.
Might be related to the time needed to start the lzop pipe on the same device for data transfer bottlenecks?