Vzdump error Input/output error

[___jul]

Hello,

I've 3 VE, vzdump is run successfully in snapshot mode for 2, with the 3rd VE I have error in vzdump log.

First the data of mysql :

" File shrank by 2170847232 bytes; padding with zeros"

and then a bunch of files have

"Read error at byte 0, while reading 40 bytes: Input/output error"

Aug 20 03:00:07 INFO: backup mode: snapshot
Aug 20 03:00:07 INFO: ionice priority: 7
Aug 20 03:00:07 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-proxmox-prod
x-0')
Aug 20 03:00:08 INFO: Logical volume "vzsnap-proxmox-prod-0" created
Aug 20 03:00:09 INFO: creating archive '/mnt/disk-usb/vzdump-openvz-105-2012_08_20-03_00_01.tgz'
Aug 20 03:08:01 INFO: tar: ./var/lib/mysql/ibdata1: File shrank by 2170847232 bytes; padding with zeros
Aug 20 03:08:42 INFO: tar: ./var/lib/sudo/adminit/3: Warning: Read error at byte 0, while reading 40 byte
s: Input/output error
Aug 20 03:08:42 INFO: tar: ./var/lib/sudo/adminit/1: Warning: Read error at byte 0, while reading 40 byte
s: Input/output error
Aug 20 03:08:42 INFO: tar: ./var/lib/sudo/adminit/0: Warning: Read error at byte 0, while reading 40 byte
s: Input/output error
Aug 20 03:08:42 INFO: tar: ./var/lib/sudo/adminit/2: Warning: Read error at byte 0, while reading 40 byte
s: Input/output error

I've made some research on the forum and add some space to the snapshot

cat /etc/vzdump.conf
size : 3096

But I've still have the error.

The backup are made on a separated disk with plenty of space and there is still space of on the VG to create the snapshot partition

vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 1116
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 2
Act PV 2
VG Size 1,25 TB
PE Size 4,00 MB
Total PE 328445
Alloc PE / Size 233078 / 910,46 GB
Free PE / Size 95367 / 372,53 GB
VG UUID LRS1Qu-mLmX-T3SW-XkR4-yAN2-v18D-GBPiox

pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-50
pve-kernel-2.6.32-6-pve: 2.6.32-50
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-1dso1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

I don't think the dump is properly done, how to fix this ?

Thank you

 

[dietmar]

You should update to 2.1. There were plenty of fixes related to lvm and vzdump, and we will not debug old 1.9 code.

 

[___jul]

You should update to 2.1. There were plenty of fixes related to lvm and vzdump, and we will not debug old 1.9 code.

I understand, thank you.
What risk to update a production system from 1.9 to 2.1 ?

 

[dietmar]

What risk to update a production system from 1.9 to 2.1 ?

see http://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0