Proxmox 1.4 beta2: vzdump freez machines ....

I have just done some test using the SCST iSCSI target with block size 4096 - everything works as expected - no problems.
 
this is crazy ....

all here under debian as works without problems, too. The only thing what makes touble is the vzdump tool. As already written, dd copys from the TheCus I4500r with blocksize of 4096 without problems.

So, what do you think about it? Can it be the TheCus device?!
Do you have testes the blocksize with openfiler? How do you have change it?! I want make some tests too with the blocksize and openfiler.
 
Last edited:
valshare said:
all here under debian as works without problems, too. The only thing what makes touble is the vzdump tool. As already written, dd copys from the TheCus I4500r with blocksize of 4096 without problems.
Click to expand...

dd just do 'read' calls, whereas vzdump also do 'seek' calls. Anyways, an IO-Error cant be cause of a software bug inside vzdump.

valshare said:
So, what do you think about it? Can it be the TheCus device?!
Click to expand...

Again, I would ask TheCus support. Do you use the lastest software from them?

valshare said:
Do you have testes the blocksize with openfiler? How do you have change it?! I want make some tests too with the blocksize and openfiler.
Click to expand...

Openfiler uses IET, which can't change block size (AFAIK).

See http://scst.sourceforge.net/comparison.html
 
Does the problem show up if you use the iscsi lun directly, or only when you use LVM on top of the iscsi lun.
 
dietmar said:
You can use iSCSI LUNs without lvm too (not recommended, but good for testing).
Click to expand...

i have activated the "Use LUNs directly" switch in the Proxmox settings for my ISCSI LUN Interface and startet with vzdump --snapshot -- compress a backup. The Backup completed without an error now!
 
valshare said:
i have activated the "Use LUNs directly" switch in the Proxmox settings for my ISCSI LUN Interface
Click to expand...

Changing that flag does not change anything iSCSI related. I just allows you to create a VM which uses iSCSI LUNs directly.

valshare said:
and startet with vzdump --snapshot -- compress a backup. The Backup completed without an error now!
Click to expand...

If you use a LUN directly --snapshot will fail, and vzdump will falback to suspend mode.
 
ok, have now use the LUN direct and failed to backup. Same as above. The backup file didn´t grow. interrupted the backup after 30 minutes.

Regards, Valle

Code: 
proxmox01:/# vzdump --suspend --compress 115
INFO: starting new backup job: vzdump --suspend --compress 115
INFO: Starting Backup of VM 115 (qemu)
INFO: running
INFO: status = running
INFO: backup mode: suspend
INFO: bandwidth limit: 10240 KB/s
INFO: suspend vm
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-115-2009_10_20-23_35_21.tgz'
INFO: adding '/var/lib/vz/dump/vzdump-qemu-115-2009_10_20-23_35_21.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/dev/disk/by-id/scsi-32034001378a40e50' to archive ('vm-disk-ide0.raw')
interrupted by signal
INFO: resume vm
INFO: vm is online again after 1799 seconds
ERROR: Backup of VM 115 failed - interrupted by signal
ERROR: Backup job failed - interrupted by signal
 
Last edited:
You must log in or register to reply here.
Top Bottom