vzdump stop during backup 80GB VM and restart all VPS

[krisss117]

Hi, i have a few Proxmox instances on separated networks and differents hardware, but the same problem.

Packages:
proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve)
pve-manager: 4.3-9 (running version: 4.3-9/f7c6f0cd)
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-46
qemu-server: 4.0-92
pve-firmware: 1.1-10
libpve-common-perl: 4.0-79
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-68
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.3-12
pve-qemu-kvm: 2.7.0-4
pve-container: 1.0-80
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

Backup from one local drive to another local drive (and on another location to SMB)

During backup VM larger than 80GB Proxmox stop backup and try to start VMs.


Backup: unexpected status
INFO: Starting Backup of VM 900 (qemu)
INFO: status = running
INFO: update VM 900: -lock backup
INFO: VM Name: OwnCloud-PRIV
INFO: include disk 'virtio0' 'local-zfs:vm-900-disk-2'
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/BACKUP_1TB/dump/vzdump-qemu-900-2016_11_01-11_38_25.vma.lzo'
INFO: started backup task '957b7f11-04b8-466f-a672-ab62f9113f26'
INFO: status: 0% (171048960/161061273600), sparse 0% (41299968), duration 3, 57/43 MB/s
INFO: status: 1% (1615462400/161061273600), sparse 0% (133496832), duration 37, 42/39 MB/s
INFO: status: 2% (3272736768/161061273600), sparse 0% (173670400), duration 72, 47/46 MB/s
INFO: status: 3% (4861591552/161061273600), sparse 0% (252035072), duration 106, 46/44 MB/s
INFO: status: 4% (6594887680/161061273600), sparse 0% (392880128), duration 141, 49/45 MB/s
INFO: status: 5% (8065908736/161061273600), sparse 0% (414957568), duration 172, 47/46 MB/s
INFO: status: 6% (9681371136/161061273600), sparse 0% (528400384), duration 206, 47/44 MB/s
INFO: status: 7% (11277828096/161061273600), sparse 0% (664084480), duration 236, 53/48 MB/s
INFO: status: 8% (13033930752/161061273600), sparse 0% (781479936), duration 269, 53/49 MB/s
INFO: status: 9% (14512553984/161061273600), sparse 0% (782680064), duration 306, 39/39 MB/s
INFO: status: 10% (16156131328/161061273600), sparse 0% (910647296), duration 353, 34/32 MB/s
INFO: status: 11% (17724473344/161061273600), sparse 0% (1014079488), duration 490, 11/10 MB/s
INFO: status: 12% (19328532480/161061273600), sparse 0% (1019424768), duration 617, 12/12 MB/s
INFO: status: 13% (20955398144/161061273600), sparse 0% (1049665536), duration 720, 15/15 MB/s
INFO: status: 14% (22597468160/161061273600), sparse 0% (1078108160), duration 779, 27/27 MB/s
INFO: status: 15% (24212930560/161061273600), sparse 0% (1122525184), duration 816, 43/42 MB/s
INFO: status: 16% (25832194048/161061273600), sparse 0% (1167044608), duration 1092, 5/5 MB/s
INFO: status: 17% (27383037952/161061273600), sparse 0% (1316376576), duration 1222, 11/10 MB/s
INFO: status: 18% (28998500352/161061273600), sparse 0% (1394372608), duration 1320, 16/15 MB/s
INFO: status: 19% (30636769280/161061273600), sparse 0% (1432940544), duration 1426, 15/15 MB/s
INFO: status: 20% (32251969536/161061273600), sparse 0% (1467645952), duration 1571, 11/10 MB/s

Logs from:
/var/log/messages
/var/log/kern
/var/log/syslog

Any ideas?

 

[spirit]

Are you sure that the server don't have rebooted ? (It's the only moment when you can have "start all vms" task log )

 

[krisss117]

Are you sure that the server don't have rebooted ? (It's the only moment when you can have "start all vms" task log )

Yes, I'm sure. I have this problem on differents time and hardware.

 

[Entropywrench]

Looks like the same issue I am having: https://forum.proxmox.com/threads/pve-kernel-panic-during-nightly-backup.29232/

 

[krisss117]

Yes, but there is no solution to resolve problem.

Who can help? I can give more logs if You want.

 

[krisss117]

I think it is a ZFS problem. Before i have drive EXT4 and there is no problem.

Here my ZFS configuraction:
zfs get all rpool

NAME PROPERTY VALUE SOURCE
rpool type filesystem -
rpool creation Tue Oct 4 20:36 2016 -
rpool used 209G -
rpool available 690G -
rpool referenced 96K -
rpool compressratio 1.21x -
rpool mounted yes -
rpool quota none default
rpool reservation none default
rpool recordsize 128K default
rpool mountpoint /rpool default
rpool sharenfs off default
rpool checksum on default
rpool compression lz4 local
rpool atime off local
rpool devices on default
rpool exec on default
rpool setuid on default
rpool readonly off default
rpool zoned off default
rpool snapdir hidden default
rpool aclinherit restricted default
rpool canmount on default
rpool xattr on default
rpool copies 1 default
rpool version 5 -
rpool utf8only off -
rpool normalization none -
rpool casesensitivity sensitive -
rpool vscan off default
rpool nbmand off default
rpool sharesmb off default
rpool refquota none default
rpool refreservation none default
rpool primarycache all default
rpool secondarycache all default
rpool usedbysnapshots 0 -
rpool usedbydataset 96K -
rpool usedbychildren 209G -
rpool usedbyrefreservation 0 -
rpool logbias latency default
rpool dedup off local
rpool mlslabel none default
rpool sync standard local
rpool refcompressratio 1.00x -
rpool written 96K -
rpool logicalused 230G -
rpool logicalreferenced 40K -
rpool filesystem_limit none default
rpool snapshot_limit none default
rpool filesystem_count none default
rpool snapshot_count none default
rpool snapdev hidden default
rpool acltype off default
rpool context none default
rpool fscontext none default
rpool defcontext none default
rpool rootcontext none default
rpool relatime off default
rpool redundant_metadata all default
rpool overlay off default