OpenVZ does not support shared storage, so I do not see how this should work. what files ystem do you use on var/lib/vz?
This is how i have it setup:
Server 1
prox:/var/lib/vz/private# fdisk -l
Disk /dev/sdc: 48.0 GB, 48049946624 bytes
64 heads, 32 sectors/track, 45824 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x22ea0421
Device Boot Start End Blocks Id System
/dev/sdc1 1 45824 46923760 83 Linux
Disk /dev/sdd: 47.2 GB, 47278194688 bytes
64 heads, 32 sectors/track, 45088 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x79266f52
Device Boot Start End Blocks Id System
/dev/sdd1 1 45088 46170096 83 Linux
******************************************************************
prox:/var/lib/vz/private# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 2.0G 709M 1.2G 38% /
tmpfs 248M 0 248M 0% /lib/init/rw
udev 10M 580K 9.5M 6% /dev
tmpfs 248M 0 248M 0% /dev/shm
/dev/mapper/pve-data 3.5G 730M 2.8G 21% /var/lib/vz1
/dev/sda1 504M 31M 448M 7% /boot
/dev/sdb1 45G 1.1G 41G 3% /var/lib/vz
10.5.0.6:/mnt/data_vg/images/ISO
12G 713M 11G 7% /mnt/pve/test_NFS
/dev/sdc1 45G 1.1G 41G 3% /var/lib/vz
***********************************************************************
prox:/var/lib/vz/private# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz1 ext3 defaults 0 1
UUID=ccf0a892-784b-4f07-9d51-0c081fa988b2 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/sdc1 /var/lib/vz ext3 defaults,auto,_netdev 0 0
*****************************************************************
Server 2
pprox2:/var/lib/vz/private# fdisk -l
Disk /dev/sdb: 48.0 GB, 48049946624 bytes
64 heads, 32 sectors/track, 45824 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x22ea0421
Device Boot Start End Blocks Id System
/dev/sdb1 1 45824 46923760 83 Linux
Disk /dev/sdc: 47.2 GB, 47278194688 bytes
64 heads, 32 sectors/track, 45088 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x79266f52
Device Boot Start End Blocks Id System
/dev/sdc1 1 45088 46170096 83 Linux
*****************************************************************
prox2:/var/lib/vz/private# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 2.0G 742M 1.2G 39% /
tmpfs 248M 0 248M 0% /lib/init/rw
udev 10M 576K 9.5M 6% /dev
tmpfs 248M 0 248M 0% /dev/shm
/dev/sda1 504M 31M 448M 7% /boot
10.5.0.6:/mnt/data_vg/images/ISO
12G 713M 11G 7% /mnt/pve/test_NFS
/dev/mapper/pve-data 3.5G 225M 3.3G 7% /var/lib/vz1
/dev/sdc1 44G 334M 41G 1% /var/lib/vz
******************************************************************
prox2:/var/lib/vz/private# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz1 ext3 defaults 0 1
UUID=a3a2eb86-9159-4210-b276-3b496dd6b485 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/sdc1 /var/lib/vz ext3 defaults,auto,_netdev 0 0
***********************************************************************
In the output from fdisk -l the disks are appearing with different /dev names but the identifiers are the same on both servers - so even though on the second server it looks like i am mapping the same device /dev/sdc1 it's actually the 2nd LUN i am mapping (sdd on the first server, which is sdc on the 2nd server).
As i said offline migration works perfectly and the server is only down for the time it takes to shutdown the container and start it on the other server so ping times out for approx 5 seconds only
Not sure why everyone has so much trouble getting this working it was pretty straight forward - perhaps you would like me to do a wiki for setting up openvz on iSCSI?
Cheers,
Peter