Hello, At our latest backup jobs the backups of all OpenVZ-containers failed with massive output of I/O errors in the logfiles. After investigating this i traced it down to the snapshot-volume not growing but staying at 1G size. Available space on the VG is >1TB.
Does the proxmox backup script (now) ignore these configuration values? As soon as the volume is full the backup log gets flooded with I/O errors until all remaining files failed or the job is stopped. The snapshot volume after stopping the failed/failing backup:
Did anyone experienced this issue lately and can point me into the right direction what option/behaviour changed? Thanks
(and why on earth is the forum software stripping all linebreaks from this post??)
Code:
# lvm dumpconfig | grep snapshot_autoextend snapshot_autoextend_threshold=85 snapshot_autoextend_percent=20
Code:
# lvs | grep vzsnap vzsnap-proxmox-0 pve swi-I-s-- 1,00g data 100.00
Code:
# pveversion -v proxmox-ve-2.6.32: 3.4-157 (running kernel: 2.6.32-39-pve) pve-manager: 3.4-6 (running version: 3.4-6/102d4547) pve-kernel-2.6.32-32-pve: 2.6.32-136 pve-kernel-2.6.32-39-pve: 2.6.32-157 pve-kernel-2.6.32-30-pve: 2.6.32-130 pve-kernel-2.6.32-37-pve: 2.6.32-150 pve-kernel-2.6.32-34-pve: 2.6.32-140 pve-kernel-2.6.32-31-pve: 2.6.32-132 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.10-2 pve-cluster: 3.0-18 qemu-server: 3.4-6 pve-firmware: 1.1-4 libpve-common-perl: 3.0-24 libpve-access-control: 3.0-16 libpve-storage-perl: 3.0-33 pve-libspice-server1: 0.12.4-3 vncterm: 1.1-8 vzctl: 4.0-1pve6 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 2.2-10 ksm-control-daemon: 1.1-1 glusterfs-client: 3.5.2-1