Hi there,
Again with the new kernel the backup will stall, but this time the compute module will not responde so the HA KVM will migrate to other servers. So far so good, but it will crash one one backup of a KVM HA we will get failed startup of the HA process because the VM is locked by the backup process.
So the auto start on a other server will not work!
This is a real problem!
Then it is unresponsive an then we will get:
multiple times on all our hosts.
We have to do manualy:
and then it will start, but then the HA is useless.
Also is it possible to downgrade the kernel? to the "old" of 2.1, that was really stable?
It crashes on multiple IMS compute modules as host and the are in short:
It crashes always on a HA KVM with storage in the LVM pool.
the only thing in /var/log/message is:
we have the problem on multiple hosts...
Again with the new kernel the backup will stall, but this time the compute module will not responde so the HA KVM will migrate to other servers. So far so good, but it will crash one one backup of a KVM HA we will get failed startup of the HA process because the VM is locked by the backup process.
So the auto start on a other server will not work!
This is a real problem!
Code:
[COLOR=#000000][FONT=tahoma]INFO: starting new backup job: vzdump --quiet 1 --mailto proxmox2@xxxxxxxxx.nl --mode snapshot --compress lzo --maxfiles 2 --storage backup_day --all 1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 103 (openvz)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: CTID 103 exist unmounted down[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = stopped[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: stop[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/backup_day/dump/vzdump-openvz-103-2012_06_01-03_45_01.tar.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Total bytes written: 1199616000 (1.2GiB, 7.7MiB/s)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: archive file size: 484MB[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: delete old backup '/mnt/pve/backup_day/dump/vzdump-openvz-103-2012_05_28-03_55_49.tar.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Finished Backup of VM 103 (00:02:52)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 104 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = stopped[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: stop[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/backup_day/dump/vzdump-qemu-104-2012_06_01-03_47_53.tar.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: adding '/mnt/pve/backup_day/dump/vzdump-qemu-104-2012_06_01-03_47_53.tmp/qemu-server.conf' to archive ('qemu-server.conf')[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: adding '/dev/vmdisks/vm-104-disk-1' to archive ('vm-disk-ide0.raw')[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Total bytes written: 34359740928 (14.58 MiB/s)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: archive file size: 7.48GB[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: delete old backup '/mnt/pve/backup_day/dump/vzdump-qemu-104-2012_05_28-04_16_33.tar.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Finished Backup of VM 104 (00:39:15)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 200 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: snapshot[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Logical volume "vzsnap-sint-0" created[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/backup_day/dump/vzdump-qemu-200-2012_06_01-04_27_08.tar.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: adding '/mnt/pve/backup_day/dump/vzdump-qemu-200-2012_06_01-04_27_08.tmp/qemu-server.conf' to archive ('qemu-server.conf')[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: adding '/dev/vmdisks/vzsnap-sint-0' to archive ('vm-disk-virtio0.raw')[/FONT][/COLOR]Then it is unresponsive an then we will get:
Code:
[COLOR=#000000][FONT=tahoma]task started by HA resource agent[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: VM is locked (backup)[/FONT][/COLOR]We have to do manualy:
Code:
qm unlock 200Also is it possible to downgrade the kernel? to the "old" of 2.1, that was really stable?
It crashes on multiple IMS compute modules as host and the are in short:
Code:
RAM usageTotal: 23.48GB
Used: 6.20GB
CPUs
16 x Intel(R) Xeon(R) CPU L5630 @ 2.13GHz
PVE Manager version
pve-manager/2.1-1/f9b0f63a
Kernel version
Linux 2.6.32-12-pve #1 SMP Tue May 15 06:02:20 CEST 2012the only thing in /var/log/message is:
and that is the gigabit driver
we have the problem on multiple hosts...
Last edited:
