Switch back to old vzdump-version?

[rengiared]

Hi,

is it possible to switch back to an old vzdump-version?
the actual vzdump (1.2-15) which came with 1.9 drives me crazy.

when the backup starts i can see the rise of the .dat file, e.g. 12GB in 5 minutes and then happens nothing (12gb is the size of the vm, so it would be finished from the data-amount)
the .dat file stays as it is, only the timestamp is getting updated and if that were not enough i can't kill the vmtar or vzdump process, not even with "kill -9 id"

the log shows this:
Sep 23 07:20:01 INFO: Starting Backup of VM 201 (qemu)
Sep 23 07:20:01 INFO: running
Sep 23 07:20:01 INFO: status = running
Sep 23 07:20:02 INFO: backup mode: snapshot
Sep 23 07:20:02 INFO: ionice priority: 7
Sep 23 07:20:02 INFO: Logical volume "vzsnap-pve02-0" created
Sep 23 07:20:02 INFO: creating archive '/mnt/pve/pve02/vzdump-qemu-201-2011_09_23-07_20_01.tar'
Sep 23 07:20:02 INFO: adding '/mnt/pve/pve02/vzdump-qemu-201-2011_09_23-07_20_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Sep 23 07:20:02 INFO: adding '/mnt/vzsnap0/images/201/vm-201-disk-1.qcow2' to archive ('vm-disk-ide0.qcow2')


if possible i would get back to vzdump 1.2-13 cause all ran fine with pve 1.8 and i hope its gettin better with the old version.
thanks in advance

 

[tom]

you should find the cause of the issue, but yes, downgrading is not that hard. just download the needed package from http://download.proxmox.com and install with 'dpkg -i ...'

 

[rengiared]

i would love to find the issue, same as with the 2.6.32-6 kernel problem i had/have.
but the problem is that next week i'm on vacation and i don't like to go with bellyache

the strange thing is that the next try i started went through without any problems

Sep 23 09:02:01 INFO: Starting Backup of VM 202 (qemu)
Sep 23 09:02:01 INFO: running
Sep 23 09:02:01 INFO: status = running
Sep 23 09:02:02 INFO: backup mode: snapshot
Sep 23 09:02:02 INFO: ionice priority: 7
Sep 23 09:02:02 INFO: Logical volume "vzsnap-pve02-0" created
Sep 23 09:02:02 INFO: creating archive '/mnt/pve/pve02/vzdump-qemu-202-2011_09_23-09_02_01.tar'
Sep 23 09:02:02 INFO: adding '/mnt/pve/pve02/vzdump-qemu-202-2011_09_23-09_02_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Sep 23 09:02:02 INFO: adding '/mnt/vzsnap0/images/202/vm-202-disk-1.qcow2' to archive ('vm-disk-ide0.qcow2')
Sep 23 09:19:46 INFO: adding '/mnt/vzsnap0/images/202/vm-202-disk-2.qcow2' to archive ('vm-disk-ide1.qcow2')
Sep 23 09:32:26 INFO: Total bytes written: 67160333824 (35.11 MiB/s)
Sep 23 09:32:26 INFO: archive file size: 62.55GB
Sep 23 09:32:28 INFO: Logical volume "vzsnap-pve02-0" successfully removed
Sep 23 09:32:28 INFO: Finished Backup of VM 202 (00:30:27)

if you tell me how i could "debug" this issue the next time it appears, i would do my best to find the issue
the problem is that my linux-knowledge is very rudimentary

 

[tom]

any infos about your VM 201? did you specify something in /etc/vzdump.conf?

do you have enough space in your snapshot? you can increase by adding this line in /etc/vzdump.conf:

size: 3072

 

[rengiared]

hi
vm 201 was just an example, it can happen with everyone on the host
i have the size set to 4000 cause that was the maximum that was possible, e.g. 4096 was already too much

BUT maybe i found the real issue for this problem. my nexentacore nas with napp-it on top just informed me about an faulty drive and i'm going to replace it tomorrow
i will report if the error disappears or not in the next time

thx for your help!