We occasionally experience a backup to disk (not a vzdump - a copy of the vzdump files, after the vzdump backup has finished) that is very slow. The syslog is full of:
It is not always the same disk (there is a rotation). And after a reboot, the disk will work fine (the next time it comes up in rotation).
Looking at this thread I did the following:
which took quite a while.
Info:
Any ideas?
Code:
pvestatd[1387]: status update time (286.687 seconds)
It is not always the same disk (there is a rotation). And after a reboot, the disk will work fine (the next time it comes up in rotation).
Looking at this thread I did the following:
Code:
# time pvesm status
drive2-backups dir 1 720915496 318580432 365691644 47.06%
drive2-vm dir 1 720915496 318580432 365691644 47.06%
local dir 1 41153856 2377108 36663212 6.59%
local-lvm lvmthin 1 225697792 120996586 104701205 54.11%
real 5m41.645s
user 0m0.492s
sys 0m0.076s
Info:
Code:
# pveversion --verbose
proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-5 (running version: 4.4-5/c43015a5)
pve-kernel-4.4.35-2-pve: 4.4.35-78
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-48
qemu-server: 4.0-102
pve-firmware: 1.1-10
libpve-common-perl: 4.0-85
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-71
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-90
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-5
lxcfs: 2.0.5-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80
Any ideas?