| are vzdump problems well known ? [message #43212] |
Mon, 08 August 2011 19:09  |
chipitsine
Messages: 2
Registered: August 2011
|
Junior Member |
|
|
I'm using ProxMox VE with OpenVZ containers.
versions are:
KT0016:~# uname -a
Linux KT0016 2.6.32-5-pve #1 SMP Wed Jul 6 07:08:47 CEST 2011 x86_64 GNU/Linux
KT0016:~# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-5-pve
proxmox-ve-2.6.32: 1.8-35
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-5-pve: 2.6.32-35
qemu-server: 1.1-30
pve-firmware: 1.0-12
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6
KT0016:~#
ProxMox VE is built with OpenVZ patches, everything works well, but once a week containers become unaccessible after vzdump backup. error messages are:
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
Jul 10 04:35:27 KT0016 kernel: lost page write due to I/O error on dm-3
there are some other messages like ext3 problems, lvm problems, etc
is it normal thing about OpenVZ? or maybe it is known bug and ProxMox is just using wrong(old) OpenVZ patchset ?
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
