I am experiencing occasional errors during live migration of openvz containers.
Some times the container will fail to un-suspend after it has been copied to the new node.
The errors I see in the kernel logs are:
CPT ERR: ffff88072f840000,5102 :rst_file: failed to fix up file content: -22
CPT ERR: ffff88072f840000,5102 :rst_file: -22 154216
CPT ERR: ffff88072f840000,5102 :rst_files: -22
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
In these occasions the CT will fail to migrate, but the files will be on the new node and generally a start will boot it properly.
I am not sure if this is a bug or a problem related to my install
# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-2
Jinjer
Some times the container will fail to un-suspend after it has been copied to the new node.
The errors I see in the kernel logs are:
CPT ERR: ffff88072f840000,5102 :rst_file: failed to fix up file content: -22
CPT ERR: ffff88072f840000,5102 :rst_file: -22 154216
CPT ERR: ffff88072f840000,5102 :rst_files: -22
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
CPT ERR: ffff88072f840000,5102 :make_baby: -22
CPT ERR: ffff88072f840000,5102 :rst_clone_children
In these occasions the CT will fail to migrate, but the files will be on the new node and generally a start will boot it properly.
I am not sure if this is a bug or a problem related to my install
# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-2
Jinjer
