qmrestore with problems on Proxmox VE 2.0

cesarpk

Well-Known Member
Mar 31, 2012
770
3
58
Hello people
i have qmrestore with problems,
Can anyone tell me what's wrong?

I ran:
1- Backup mode gzip and stop with proxmox GUI (virtual machine is off)
2- By CLI (i need by CLI because will be part of a script):
qmrestore vzdump-qemu-101-2012_04_19-12_59_54.tar.gz 200
(i don't want to change the mac-address of NIC with the option -unique)

and i get:
extracting archive '/var/lib/vz/dump/vzdump-qemu-101-2012_04_19-12_59_54.tar.gz'
extracting 'qemu-server.conf' from archive
extracting 'vm-disk-virtio0.qcow2' from archive
Formatting '/var/lib/vz/images/200/vm-200-disk-1.qcow2', fmt=qcow2 size=32768 encryption=off cluster_size=65536
new volume ID is 'local:200/vm-200-disk-1.qcow2'
restore data to '/var/lib/vz/images/200/vm-200-disk-1.qcow2' (2238230528 bytes)
tar: write error <------ MESSAGE ERROR ???
1+332275 records in
8538+1 records out
2238230528 bytes (2.2 GB) copied, 39.609 s, 56.5 MB/s

On my node i ran:
aptitude update && aptitude full-upgrade && aptitude install resource-agents-pve

pveversion -v

pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

Why i get message error? and
how fix it?
 
Last edited:
Maybe disk full? What is the output of

# df /var/lib/vz

Thank you dietmar for your prompt response, but isn't disk full

Here the command:

df -h /var/lib/vz
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-data 344G 49G 295G 15% /var/lib/vz

What is happening?
Best regards
Cesar
 
  1. what file system do you mount on /var/lib/vz?
  2. do you have hardware raid?
 
It's curious, but now that Proxmox is in cluster, i use qmrestore and i can not get any error messages.
But when proxmox was not in cluster I tried to recover the backup, I got the error message described above
I previously erased records on files syslog and dmesg for obtain only those who need for answer to you, and now I can not retrieve them.

Do you have any idea about of this problem with qmrestore?

And let me a second question:
Is it possible to make a howto of Proxmox + GFS2 + DRBD for use with qcow2 without fence device with only 2 nodes for start manually VMs in case of a node is decomposed? (the idea of use two nodes is for not share resources processor), or do you know web links with these HowTos?

Thank you and best regards dietmar
Cesar
 
Last edited:
Thank you Tom for your prompt response
Please see my answers for ditemar above

and about yor questions:
1- what file system do you mount on /var/lib/vz?
A= LVM2 + EXT3 (The standard of proxmox)

2- do you have hardware raid?
A= No, only a simple disk SATA II in a mainboard desktop: Asus

Best regards
Cesar
 
Last edited:
Are there any errors in /var/log/syslog?

Also check the output of 'dmesg'

qmrestore have problem with Poxmox VE 2.0 !!!
Oh NO!, the problem be recur

:( Please Dietmar or anybody can help me :(

I execute "Only" this commands, in this order and in single PC:
1- I installed Proxmox VE again, now in a new HDD
2- After, i ran: aptitude update && aptitude full-upgrade && aptitude install resource-agents-pve
3- After i install 1 VM on the Proxmox GUI (Windows XP on KVM)
4- I cleaned the content of files syslog and dmesg
5- When the VM is stopped and run backup now (mode local, stop and gzip) on the Proxmox GUI
6- So far everything is fine (no error messages)
7- I ran by CLI: qmrestore vzdump-qemu-100-2012_04_21-16_34_20.tar.gz 200
8- I get the same error message described above: "tar: write error"

The content of file syslog:
Apr 21 16:36:42 kvmtest qmrestore[5824]: <root@pam> starting task UPID:kvmtest:000016C3:0002B278:4F931A5A:qmrestore:200:root@pam:

Apr 21 16:37:06 kvmtest qmrestore[5824]: <root@pam> end task UPID:kvmtest:000016C3:0002B278:4F931A5A:qmrestore:200:root@pam: OK

The content of file dmesg is empty

Best regards
Cesar
 
Are there any errors in /var/log/syslog?

Also check the output of 'dmesg'

qmrestore have problem with Poxmox VE 2.0 !!!
Oh NO!, the problem be recur !!!
S.O.S.!!!

:( Please Dietmar or anybody can help me :(

I execute "Only" this commands, in this order and in single PC:
1- I installed Proxmox VE again, now in a new HDD
2- After, i ran: aptitude update && aptitude full-upgrade && aptitude install resource-agents-pve
3- After i install 1 VM on the Proxmox GUI (Windows XP on KVM)
4- I cleaned the content of files syslog and dmesg
5- When the VM is stopped and run backup now (mode local, stop and gzip) on the Proxmox GUI
6- So far everything is fine (no error messages)
7- I ran by CLI: qmrestore vzdump-qemu-100-2012_04_21-16_34_20.tar.gz 200
8- I get the same error message described above: "tar: write error"

The content of file syslog:
Apr 21 16:36:42 kvmtest qmrestore[5824]: <root@pam> starting task UPID:kvmtest:000016C3:0002B278:4F931A5A:qmrestore:200:root@pam:

Apr 21 16:37:06 kvmtest qmrestore[5824]: <root@pam> end task UPID:kvmtest:000016C3:0002B278:4F931A5A:qmrestore:200:root@pam: OK

The content of file dmesg is empty
 
Maybe a problem wit your disk - any error messages from kernel?

# dmesg

Hi dietmar and thank you for your prompt response

It is not disk problem, because I tested with 2 different disks installing Proxmox in each.
I think that "qmrestore" have bugs problems

The dmesg command not show error messages, or at least the word "error", and I can not include it here because the output has too many characters.

Please help me, and i will await your feedback

Best Regards
Cesar
 
I have detected that the promox ISO installer have problems

I installed proxmox (ISO) on three different HDD, on singles Desktop PCs and singles Hard Disk sata 2 for each, and the three installations show the same problem: "doesn't contain a valid partition table"
And perhaps for this reason the command qmrestore shows me the error message described above

For Example:
fdisk -l

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008bd14

Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 91202 732049408 8e Linux LVM

Disk /dev/dm-0: 103.1 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 625.1 GB, 625068736512 bytes
255 heads, 63 sectors/track, 75993 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-2 doesn't contain a valid partition table

My hardware Desktop configuration:
Mainboard Asus + Intel quad core + AHCI + 1 HDD sata 2 on channel 1

Questions:
1- any idea what happend?
2- how fix it?

Best Regards
Cesar
 
Last edited:
About my reply above "I have detected that the promox ISO installer have problems", It's curious, but if i run the command "fdisk -l | less" then the output does not display error messages.

Excuse me if I said something wrong, bit i don't know what happen with qmrestore command?, and now what happen with these commands?

Best Regards
Cesar
 
It is not disk problem, because I tested with 2 different disks installing Proxmox in each.
I think that "qmrestore" have bugs problems

I do not think that this is a qmrestore problem. A 'tar' write error only occur if a write command fail, and this is closely related to the disk.
 
I do not think that this is a qmrestore problem. A 'tar' write error only occur if a write command fail, and this is closely related to the disk.

Thank you dietmar for your prompt response.
I understand that do not is a partitioning problem for install proxmox ISO.

:(
And i continue with the uncertainty of what happens with the qmrestore command?, so why I get the same error message? (tar: write error), Being that I installed Proxmox ISO on three different hard disks and on two differents computers?

I will be very grateful if you can help me solve the problem :D

Best Regards
Cesar
 
What tar command do you use to test (please use absolute paths)?

i ran:
cd /var/lib/vz/dump
tar -zxvf vzdump-qemu-101-2012_04_19-12_59_54.tar.gz
and
tar -zxvf vzdump-qemu-112-2012_04_21-00_23_31.tar.gz

The files unzipped and unpacked, and i don't get message errors
 

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!