qmrestore error ?

fpausp · Apr 12, 2014

I like to qmrestore the vzdump-qemu-113-2014_04_12-09_08_11.vma.gz created on another proxmox-server and get this error:

Code:

root@proxmox2:/var/lib/vz/dump# qmrestore vzdump-qemu-113-2014_04_12-09_08_11.vma.gz 100
restore vma archive: zcat /var/lib/vz/dump/vzdump-qemu-113-2014_04_12-09_08_11.vma.gz|vma extract -v -r /var/tmp/vzdumptmp3938.fifo - /var/tmp/vzdumptmp3938
CFG: size: 326 name: qemu-server.conf
DEV: dev_id=1 size: 1073741824000 devname: drive-virtio0
CTIME: Sat Apr 12 09:08:12 2014
command 'zcat /var/lib/vz/dump/vzdump-qemu-113-2014_04_12-09_08_11.vma.gz|vma extract -v -r /var/tmp/vzdumptmp3938.fifo - /var/tmp/vzdumptmp3938' failed: command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/100/vm-100-disk-4.qcow2 1048576000K' failed: got timeout

fpausp · Apr 12, 2014

This is also not possible with the gui:

Code:

restore  vma archive: zcat  /var/lib/vz/dump/vzdump-qemu-100-2014_04_12-15_20_00.vma.gz|vma extract -v -r /var/tmp/vzdumptmp27680.fifo - /var/tmp/vzdumptmp27680
CFG: size: 308 name: qemu-server.conf
DEV: dev_id=1 size: 2147483648000 devname: drive-virtio0
CTIME: Sat Apr 12 15:20:01 2014
TASK  ERROR: command 'zcat  /var/lib/vz/dump/vzdump-qemu-100-2014_04_12-15_20_00.vma.gz|vma extract -v -r /var/tmp/vzdumptmp27680.fifo - /var/tmp/vzdumptmp27680' failed:  command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/100/vm-100-disk-2.qcow2 2097152000K' failed: got  timeout

I realy need help ????

fpausp · Apr 13, 2014

Still get the error on a fresh installed HP ML350 G6:

Code:

root@proxmox2:/var/lib/vz/dump# qmrestore vzdump-qemu-100-2014_04_13-18_46_07.vma.gz 100
restore vma archive: zcat /var/lib/vz/dump/vzdump-qemu-100-2014_04_13-18_46_07.vma.gz|vma extract -v -r /var/tmp/vzdumptmp3404.fifo - /var/tmp/vzdumptmp3404
CFG: size: 337 name: qemu-server.conf
DEV: dev_id=1 size: 536870912000 devname: drive-virtio0
CTIME: Sun Apr 13 18:46:09 2014
command 'zcat /var/lib/vz/dump/vzdump-qemu-100-2014_04_13-18_46_07.vma.gz|vma extract -v -r /var/tmp/vzdumptmp3404.fifo - /var/tmp/vzdumptmp3404' failed: command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/100/vm-100-disk-1.qcow2 524288000K' failed: got timeout

dietmar · Apr 14, 2014

What is the output of

# pveversion -v

fpausp · Apr 14, 2014

At the moment I try to reinstall from the "old" proxmox 3.1 cd...

I can give you an answer in abt 3 hours.

fpausp · Apr 14, 2014

I did a reinstall of the hp ml350 g6, qmrestore is working with the "old" proxmox 3.1, the pveversion is:

Code:

root@proxmox2:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
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.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Should I update to the latest version of proxmox 3.2 ?

fpausp · Apr 14, 2014

I did the update/upgrade to the latest version of proxmox and the error is back again...

Code:

pveversion -v

proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
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-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

Code:

qmrestore vzdump-qemu-113-2014_04_12-10_45_16.vma.gz 110

restore vma archive: zcat /var/lib/vz/dump/vzdump-qemu-113-2014_04_12-10_45_16.vma.gz|vma extract -v -r /var/tmp/vzdumptmp2777.fifo - /var/tmp/vzdumptmp2777
CFG: size: 326 name: qemu-server.conf
DEV: dev_id=1 size: 1073741824000 devname: drive-virtio0
CTIME: Sat Apr 12 10:45:17 2014
command 'zcat /var/lib/vz/dump/vzdump-qemu-113-2014_04_12-10_45_16.vma.gz|vma extract -v -r /var/tmp/vzdumptmp2777.fifo - /var/tmp/vzdumptmp2777' failed: command '/usr/bin/qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/110/vm-110-disk-1.qcow2 1048576000K' failed: got timeout

dietmar · Apr 14, 2014

Is it possible to get access to that file (to debug the problem). If so, please contact me directly with dietmar@proxmox.com

fpausp · Apr 15, 2014

How many percent do we have ?

dietmar · Apr 15, 2014

fpausp said:
How many percent do we have ?

1% (estimated time 8h)

dietmar · Apr 15, 2014

Ok, restore work here without any problem. So this seems to be related to your storage mounted at /var/lib/vz/.

Are you able to create images manually? What is the output of:

# time qemu-img create -o 'preallocation=metadata' -f qcow2 /var/lib/vz/images/test-image.qcow2 1048576000K

fpausp · Apr 15, 2014

Code:

real    0m11.704s
user    0m1.798s
sys     0m0.630s

/dev/mapper/pve-data on /var/lib/vz type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered)

fpausp · Apr 15, 2014

# HP ML350 G6 (Smart Array P410i RaidController)
It was working with proxmox 3.1 at the same hardware... after the update to 3.2 the error comes back again.

# Fujitsu TX100 S3 (Adaptec RaidController)
I tried to restore the same file on my 2nd Server and it works on it, what can/should I do ?

Any Suggestions ?

fpausp · Apr 15, 2014

what is the difference btw win7-image qmrestore (vzdump-qemu-101-2014_04_12-22_21_53.vma.gz) and linux-image qmrestore (vzdump-qemu-100-2014_04_14-17_12_37.vma.gz).

win7-image works the linux-image do not work ??????

fpausp · Apr 15, 2014

I can not figure out what the problem is, some images can be restored on the old hp server and some not.

on my fujitsu server I can restore these files, so what is the problem, the software (proxmox 3.2) is the same...

dietmar · Apr 16, 2014

What is the output of

# pveperf

dietmar · Apr 16, 2014

fpausp said:
win7-image works the linux-image do not work ??????

Your restores fails before any data is read (when creating the image), so maybe you use different image formats for the disks (qcow2 vs raw)?

fpausp · Apr 16, 2014

Why is the qmrestore working with this image on proxmox 3.1 and not with 3.2 ?

I am able to restore it on another server with proxmox 3.2, how can I debug the error ?

dietmar · Apr 16, 2014

fpausp said:
Why is the qmrestore working with this image on proxmox 3.1 and not with 3.2 ?

"qemu-img create" is to slow on your server, so you run into a timeout. Please can you post the output of

# pveperf

fpausp · Apr 16, 2014

Code:

root@proxmox2:~# pveperf
CPU BOGOMIPS:      17060.44
REGEX/SECOND:      836946
HD SIZE:           19.69 GB (/dev/mapper/pve-root)
BUFFERED READS:    427.04 MB/sec
AVERAGE SEEK TIME: 4.92 ms
FSYNCS/SECOND:     47.25
DNS EXT:           49.85 ms
DNS INT:           29.40 ms

I was able to qmrestore an image of the same linux distri (sme8) but with 500GB hdd instead of befor 1TB.

qmrestore error ?

Renowned Member

Renowned Member

Renowned Member

Proxmox Staff Member

Renowned Member

Renowned Member

Renowned Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Proxmox Staff Member

Renowned Member

Renowned Member

Renowned Member

Renowned Member

Proxmox Staff Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member