vzdump problem

frantek

Renowned Member
May 30, 2009
171
7
83
Hi,

from time to time I'v a problem with vzdump while doing backups to a USB disk. I get:
Code:
Jan 21 08:00:01 bs01 vzdump[374]: INFO: starting new backup job: vzdump --quiet --snapshot --compress --storage backup --maxfiles 1 104
Jan 21 08:00:01 bs01 vzdump[374]: INFO: Starting Backup of VM 104 (qemu)
Jan 21 08:00:02 bs01 vzdump[374]: ERROR: Backup of VM 104 failed - command 'qm set 104 --lock backup' failed with exit code 255
Jan 21 08:00:02 bs01 vzdump[374]: INFO: Backup job finished with errors
When this happens I see the following:
Code:
qm list 

      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID       
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
       101 Nagios               stopped    1024              32.00 0         
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
       102 DLL_Builder          stopped    4096              80.00 0         
  /dev/dm-8: read failed after 0 of 4096 at 0: Input/output error 
  ....
  ....
"lvdisplay" shows:
Code:
  --- Logical volume --- 
  ....
  ....
  ....
  LV Name                /dev/vg0/vm-103-disk-1 
  VG Name                vg0 
  LV UUID                m65HoB-dciY-Mo5s-Mmpw-44I1-hXZ1-BywUTe 
  LV Write Access        read/write 
  LV snapshot status     source of 
                         /dev/vg0/vzsnap-bs01-0 [INACTIVE] 
  ....
  ....
  ....
  --- Logical volume --- 
  LV Name                /dev/vg0/vzsnap-bs01-0 
  VG Name                vg0 
  LV UUID                F0rIGg-5PEp-2Uwq-T7wx-oJph-1lBO-XDYxOd 
  LV Write Access        read/write 
  LV snapshot status     INACTIVE destination for /dev/vg0/vm-103-disk-1 
  LV Status              available
To reslove this I've to do:
Code:
lvremove -f /dev/vg0/vzsnap-bs01-0 
  /dev/dm-8: read failed after 0 of 4096 at 0: Eingabe-/Ausgabefehler 
  Logical volume "vzsnap-bs01-0" successfully removed
and unlock the VM's.

System:
Code:
uname -a
Linux bs01 2.6.35-2-pve #1 SMP Mon Aug 8 07:25:00 CEST 2011 x86_64 GNU/Linux

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-1-pve: 2.6.35-11
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-1
ksm-control-daemon: 1.0-6

example VM:

Code:
name: XP-Lexware
ide2: cdrom,media=cdrom
bootdisk: ide0
ostype: wxp
ide0: vg0:vm-103-disk-1
memory: 3072
sockets: 1
vlan0: rtl8139=B6:F9:18:3F:26:79
onboot: 0
cores: 1

How can I get around this ?

TIA
 
I know the devic. dm-8 is - or better was - /dev/vg0/vzsnap-bs01-0 :)

What I need is to know why this happens and how to get rid of this problem ...
 

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!