proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev...

[techguys]

pveversion -v

atom2:/var/lib/vz/vzbackups# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.35-2-pve
proxmox-ve-2.6.35: 1.8-13
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-2-pve: 2.6.35-13
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

Another VM on the same disk using snapshot runs fine consistently. This one fails consistently.

 

[techguys]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

Anyone else experiencing this, or have any suggestions?

 

[dietmar]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

What is 'vzbackup'?

 

[techguys]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

Sorry I guess I should have said vzdump... The built in backup facility in proxmox.

The snapshot keeps failing and essentially hanging the vzdump process:

atom2:/var/log/vzdump# ps aux | grep vzb
root 4940 0.0 0.0 8884 1100 ? S Jul31 0:00 sh -c /usr/lib/qemu-server/vmtar '/var/lib/vz/vzbackups/vzdump-qemu-201-2012_07_31-03_30_01.tmp/qemu-server.conf' 'qemu-server.conf' '/dev/atom2-disk3/vzsnap-atom2-0' 'vm-disk-ide0.raw'|gzip - >/var/lib/vz/vzbackups/vzdump-qemu-201-2012_07_31-03_30_01.dat
root 4941 99.6 0.0 7644 4220 ? R Jul31 11903:34 /usr/lib/qemu-server/vmtar /var/lib/vz/vzbackups/vzdump-qemu-201-2012_07_31-03_30_01.tmp/qemu-server.conf qemu-server.conf /dev/atom2-disk3/vzsnap-atom2-0 vm-disk-ide0.raw

atom2:/var/log/vzdump# lvdisplay atom2-disk3
/dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
--- Logical volume ---
LV Name /dev/atom2-disk3/vm-203-disk-1
VG Name atom2-disk3
LV UUID 6j3IG5-e9C3-B1FT-Hz79-f1En-Llq4-TAcTAv
LV Write Access read/write
LV Status available
# open 1
LV Size 150.00 GB
Current LE 38400
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:5
--- Logical volume ---
LV Name /dev/atom2-disk3/vzsnap-atom2-0
VG Name atom2-disk3
LV UUID WN3Whq-JzEJ-UMaI-kXLf-kg6d-N1Fo-WckCOK
LV Write Access read/write
LV snapshot status INACTIVE destination for /dev/atom2-disk3/vm-201-disk-1
LV Status available
# open 1
LV Size 150.00 GB
Current LE 38400
COW-table size 1.00 GB
COW-table LE 256
Snapshot chunk size 4.00 KB
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:4

 

[dietmar]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

Maybe you need to increase snapshot size in /etc/vzdump.conf (see 'man vzdump')

 

[techguys]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

Ok, I'll give that a try, however it was working and then occassionally it actually works. But mostly it doesn't.

 

[techguys]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

So in looking at this though... The 'failed' snapshot was the same size as the actual LV in the first place:
LV Size 150.00 GB

It's 150 GB for both the original and the snapshot LV.

 

[dietmar]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

It's 150 GB for both the original and the snapshot LV.

The interesting part is 'COW-table size', which is 1GB:

COW-table size 1.00 GB

 

[techguys]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

So interestingly enough... I added the line:
atom2:/etc# cat vzdump.conf
size: 30720

And since then the last 2 backups have completed successfully...

The actual TGZ file being created is about 100G... as near as I can tell without the vzdump.conf it by default creates the snapshot the same size as the LV in the first place. I don't really understand why this would have fixed the problem.

 

[dietmar]

Re: proxmox 1.9 vzbackup failing with snapshot error: INACTIVE destination for /dev..

size: 30720

This is very large. I guess 4000 (4GB) would be enough.