Would it be possible to port this fix to Proxmox 4.0? I'm having the same issue there. Setting the Backup Mode to "Suspend" or "Stop" works fine.
Regards,
Stefan
After update to 3.2: VM crashing during backup
- Thread starter jens.kuespert
- Start date
Would it be possible to port this fix to Proxmox 4.0? I'm having the same issue there. Setting the Backup Mode to "Suspend" or "Stop" works fine.
Regards,
Stefan
Hi,
This fix is pretty old (qemu 1.7), we we'll be at qemu 2.4 for proxmox 4.0. So yes the fix for the original bug is of course included.
Now, if you have a backup bug with current proxmox 4.0 beta, please give details, not just "I'm having the same issue there." .
Please send backup job task logs, vmid conf, storage hardware description (vm storage and backup storage),....
Well, I did not assume that every change that was made in 1.7 would also be made in 2.4+ - software development often doesn't work that way. But I'm happy to hear that you are sure that this particular fix is also in the source code for the current qemu branch and I'll take your word for it.
Well, same is the right word here because when I look at the logs that were previously posted, they have one thing in common and that is:
Code:
[COLOR=#000000][FONT=tahoma]INFO: starting new backup job: ...[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 106 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = running[/FONT][/COLOR]
...
[COLOR=#000000][FONT=tahoma]INFO: started backup task 'f06aa13e-a083-4b1d-941e-86d30985b7ad'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status: 0% (35323904/348966092800), sparse 0% (102400), duration 3, 11/11 MB/s[/FONT][/COLOR]
...
[COLOR=#000000][FONT=tahoma]INFO: status: 44% (153551372288/348966092800), sparse 6% (23281065984), duration 16253, 11/10 MB/s[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 106 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: aborting backup job[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: VM 106 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: Backup of VM 106 failed - VM 106 not running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: Backup job finished with errors[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: job errors[/FONT][/COLOR]And here's mine:
Code:
INFO: starting new backup job: vzdump 101 --compress lzo --storage quicky-backup --mode snapshot --remove 0 --node sedna
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: update VM 101: -lock backup
INFO: exclude disk 'virtio2' (backup=no)
INFO: exclude disk 'virtio1' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/quicky-backup/dump/vzdump-qemu-101-2015_07_17-10_36_46.vma.lzo'
INFO: started backup task '5952c5dd-5d52-46b4-b292-7f32407da5e3'
INFO: status: 0% (167575552/42949672960), sparse 0% (10502144), duration 3, 55/52 MB/s
INFO: status: 1% (440926208/42949672960), sparse 0% (18296832), duration 10, 39/37 MB/s
INFO: status: 2% (861667328/42949672960), sparse 0% (28360704), duration 15, 84/82 MB/s
INFO: status: 3% (1338900480/42949672960), sparse 0% (41533440), duration 18, 159/154 MB/s
INFO: status: 4% (1867907072/42949672960), sparse 0% (45219840), duration 27, 58/58 MB/s
INFO: status: 5% (2381316096/42949672960), sparse 0% (51580928), duration 30, 171/169 MB/s
INFO: status: 6% (2892627968/42949672960), sparse 0% (58204160), duration 33, 170/168 MB/s
INFO: status: 7% (3314548736/42949672960), sparse 0% (63549440), duration 36, 140/138 MB/s
INFO: status: 8% (3752656896/42949672960), sparse 0% (76107776), duration 39, 146/141 MB/s
INFO: status: 9% (3883270144/42949672960), sparse 0% (77668352), duration 45, 21/21 MB/s
INFO: status: 10% (4388028416/42949672960), sparse 0% (92659712), duration 53, 63/61 MB/s
INFO: status: 11% (4847763456/42949672960), sparse 0% (97730560), duration 56, 153/151 MB/s
INFO: status: 12% (5180882944/42949672960), sparse 0% (100855808), duration 68, 27/27 MB/s
INFO: status: 13% (5698355200/42949672960), sparse 0% (108658688), duration 71, 172/169 MB/s
ERROR: VM 101 not running
INFO: aborting backup job
ERROR: VM 101 not running
ERROR: Backup of VM 101 failed - VM 101 not running
INFO: Backup job finished with errors
TASK ERROR: job errorsFeel free to correct me for saying "I'm having the same issue there.", but all I'm saying is that the difference between these logs is cosmetic (at least to my eyes).
Code:
bootdisk: virtio0
cores: 2
cpu: host
memory: 6144
name: testme
net0: virtio=00:0C:29:39:46:14,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
smbios1: uuid=a1fe0cc6-0dae-4b5c-a2f4-a35592d3a4d5
sockets: 3
vcpus: 4
virtio0: quicky-esx:vm-101-disk-1,cache=unsafe,discard=on,iothread=on,size=40G
virtio1: /dev/disk/by-id/wwn-0x6001405b37ee0539d2247a0b8ac7976b,cache=unsafe,discard=on,backup=no,iothread=on,size=350G
virtio2: quicky-esx:vm-101-disk-2,cache=unsafe,discard=on,backup=no,iothread=on,size=400G
Code:
lvm: quicky-esx
vgname esx
content images
shared
nfs: quicky-backup
server 10.0.0.1
path /mnt/pve/quicky-backup
export /mnt/backup
maxfiles 2
content backup
options vers=3But that doesn't tell you much because it happens with Windows VMs, Linux VMs, with host1: VM storage on LVM via FC 4Gbps, VM backups to NFS share 1Gbps; but also on host2: VM storage on ZFS RAID-1 on local SSDs, backup to ZFS RAID-1 local HDDs.
It also happens with (LZO, GZIP) or without compression.
A possible similarity I could see between all mine and also all previously reported seems to be that the VM storage is faster than the backup storage, but that might also be a red herring.
Stefan
Ok thanks. I have disabled iothread and the backup seems to run fine. I now found out that someone else had that problem before me: http://forum.proxmox.com/threads/22...-on-virtio-disk-causes-vm-crash-during-vzdump
Thanks again,
Stefan
Yes, I have sent a protection patch to the proxmox dev mailing list today for this, to avoid crash.
It'll take a little more time to be able to backup iothread disks.