Online migration fails with local CT using autofs inside

[x3w]

Online migration fails with local CT using nfs and autofs inside.
If I stop autofs inside the CT, online migration works OK (with independant nfs mounts inside).

Please help me find a solution (soon in production) !
Many thanks


The log :

Oct 25 00:23:12 starting migration of CT 111 to node 'pmx185' (192.168.1.185)
Oct 25 00:23:12 container is running - using online migration
Oct 25 00:23:12 starting rsync phase 1
Oct 25 00:23:12 # /usr/bin/rsync -aHAX --delete --numeric-ids --sparse /var/lib/vz/private/111 root@192.168.1.185:/var/lib/vz/private
Oct 25 00:23:25 start live migration - suspending container
Oct 25 00:23:25 # vzctl --skiplock chkpnt 111 --suspend
Oct 25 00:23:25 Setting up checkpoint...
Oct 25 00:23:25         suspend...
Oct 25 00:23:25 Can not suspend container: No such process
[B]Oct 25 00:23:25 Error: autofs pipe is not attached (-3)[/B]
Oct 25 00:23:25 ERROR: Failed to suspend container: Checkpointing failed
Oct 25 00:23:25 aborting phase 1 - cleanup resources
Oct 25 00:23:25 removing copied files on target node
Oct 25 00:23:26 start final cleanup
Oct 25 00:23:26 ERROR: migration aborted (duration 00:00:14): Failed to suspend container: Checkpointing failed
TASK ERROR: migration aborted

lsof | grep nfs (from CT0) :

automount 589180     root  mem       REG              253,2             4940492 /var/lib/vz/root/111/usr/lib/autofs/mount_nfs.so (path dev=0,26)
automount 589255     root  mem       REG              253,2             4940492 /var/lib/vz/root/111/usr/lib/autofs/mount_nfs.so (path dev=0,26)
automount 589255     root    3u     FIFO               0,26      0t0    5013917 /var/lib/vz/root/111/var/run/autofs.fifo-nfs-data1
automount 589255     root    6r      DIR               0,37        0   10450767 /var/lib/vz/root/111/nfs/data1
automount 589331     root  mem       REG              253,2             4940492 /var/lib/vz/root/111/usr/lib/autofs/mount_nfs.so (path dev=0,26)
automount 589331     root    3u     FIFO               0,26      0t0    5013918 /var/lib/vz/root/111/var/run/autofs.fifo-nfs-data2
automount 589331     root    6r      DIR               0,38        0   10450827 /var/lib/vz/root/111/nfs/data2

cat /etc/modules (on CT0) :

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

autofs4

my pveversion -v :

pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1

 

[tom]

no idea if it helps but you ran a quite outdated version, upgrade to latest 2.2

 

[thesubmitter]

I had this ssame problem, turning off autofs for the migration was the best solution i had

 

[sunnyside]

Is this rather a Proxmox problem or an OpenVZ problem ?
It would be very usefull to have autofs working well in a CT (NFS is working like a charm so why not autofs ?).

Problem still exists in pve 3.1.
Also, there is a problem when stoping a CT using autofs inside (and running on the node local filesystem), I had to reboot the node.
That's makes autofs in a CT very difficult to use in production

Thanks for any help

# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
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.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

+ autofs4 module