qmrestore extract tmp location?

tomstephens89

Renowned Member
Mar 10, 2014
177
7
83
Kingsclere, United Kingdom
Hi guys,

I am trying to restore a VM from a USB drive via the command line and have run into an issue. The restore fails with exit code 133 every time. My target storage is LVM backed with iSCSI, plenty of space.

However, it appears that qmrestore tries to use /var/tmp as the location to extract the lzo backup. This is a problem since this server does not have much local disk space.

Is there a way I can change or specify a different location for qmrestore to use as its temp extract space?

progress 97% (read 83322404864 bytes, duration 427 sec)
progress 98% (read 84181385216 bytes, duration 429 sec)
progress 99% (read 85040365568 bytes, duration 438 sec)
progress 100% (read 85899345920 bytes, duration 461 sec)

** (process:4647): ERROR **: restore failed - vma bdrv_flush drive-virtio0 failed
/bin/bash: line 1: 4646 Done lzop -d -c /mnt/usb/vzdump-qemu-103-2016_07_26-18_34_21.vma.lzo
4647 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp4644.fifo - /var/tmp/vzdumptmp4644
Logical volume "vm-100-disk-1" successfully removed
temporary volume 'p2000_bigstore:vm-100-disk-1' sucessfuly removed
command 'lzop -d -c /mnt/usb/vzdump-qemu-103-2016_07_26-18_34_21.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp4644.fifo - /var/tmp/vzdumptmp4644' failed: exit code 133


If I try and make a symbolic link /var/tmp pointing to /mnt/usb/restore then I get the following error on restore:

** (process:8413): ERROR **: no device name mapping for drive-virtio0
/bin/bash: line 1: 8412 Broken pipe lzop -d -c /mnt/usb/vzdump-qemu-103-2016_07_26-18_34_21.vma.lzo
8413 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp8410.fifo - /var/tmp/vzdumptmp8410
Logical volume "vm-100-disk-1" successfully removed
temporary volume 'p2000_bigstore:vm-100-disk-1' sucessfuly removed
command 'lzop -d -c /mnt/usb/vzdump-qemu-103-2016_07_26-18_34_21.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp8410.fifo - /var/tmp/vzdumptmp8410' failed: exit code 133
 
Last edited:
/var/tmp is only used to extract the configuration. Data is directly copied to the target storage. What kind of target storage do you use?
 
/var/tmp is only used to extract the configuration. Data is directly copied to the target storage. What kind of target storage do you use?

The target storage is iSCSI backed LVM. MPIO configured. There is more than enough space on any of the target LUN's I try and use.

This is a new cluster so I havn't even tried to make a new VM, I will try that later today.

Any ideas?
 

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!