LVM Backup running forever

danypd69

Renowned Member
Oct 8, 2010
28
0
66
Hello, I have a backup that is running for about 1 day (the normal time is about 1 hour)

Code:
INFO: starting new backup job: vzdump 101 --quiet 1 --mailto email@domain --mode snapshot --compress lzo --storage Backup --node proxmox
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: exclude disk 'virtio0' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/storage/dump/vzdump-qemu-101-2012_10_10-01_00_02.tar.lzo'
INFO: adding '/storage/dump/vzdump-qemu-101-2012_10_10-01_00_02.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/vzsnap0/images/101/vm-101-disk-1.raw' to archive ('vm-disk-ide0.raw')

Code:
136376 ?        R    1839:02 /usr/lib/qemu-server/vmtar /storage/dump/vzdump-qemu-101-2012_10_10-01_00_02.tmp/qemu-server.conf qemu-server.conf /mnt/vzsnap0/images/101/vm-101-disk-1.raw vm-disk-ide0.raw

If I do an strace of the running process I get

Code:
read(3, 0xfffffeb6d688d27b, 1413779232153) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d27a, 1413779232154) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d279, 1413779232155) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d278, 1413779232156) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d277, 1413779232157) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d276, 1413779232158) = -1 EFAULT (Bad address)
read(3, 0xfffffeb6d688d275, 1413779232159) = -1 EFAULT (Bad address)
until I stop it.


Code:
root@proxmox:/home/daniele# pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1

Backup started on Oct 10 01:00:02 and I found this message in kern.log

Code:
Oct 10 03:01:07 proxmox kernel: device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception.

I think that the problem is related to the snapshot size but I don't know what else I can check.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!