[PVE-User] Migration error because of local storage

[THe_ZiPMaN]

I have 2 hosts with 2 drbd shared storage and some VM on them.

I can migrate online all the machines between the 2 pve hosts, all
except the numer 101.

When I try to move it I receive the following error and to move it I
must shutdown it, migrate and poweron.

#######################################
Nov 28 20:39:01 starting migration of VM 101 to node 'giunone02'
(192.168.232.252)
Nov 28 20:39:01 copying disk images
Nov 28 20:39:01 ERROR: Failed to sync data - can't do online migration -
VM uses local disks
Nov 28 20:39:01 aborting phase 1 - cleanup resources
Nov 28 20:39:01 ERROR: migration aborted (duration 00:00:00): Failed to
sync data - can't do online migration - VM uses local disks
TASK ERROR: migration aborted
#######################################

Obviously the machine doesn't use any local disk. It's configuration is
exactly the same of all the other similar machine I have on that host.

Here is its config file of VM 101
#######################################
#Reverse Proxy Apache
bootdisk: virtio0
cores: 1
ide2: none,media=cdrom
memory: 512
name: marte.xxx.inet
net0: virtio=86:58:DD:D1:3F:70,bridge=vmbr0
onboot: 0
ostype: l26
sockets: 1
startup: order=40
virtio0: datastore1:vm-101-disk-1
#######################################

Instead this is the config file of VM 102 that migrates without any
problem. As you can see they are the same.
#######################################
#Joomla Hosting
bootdisk: virtio0
cores: 1
ide2: none,media=cdrom
memory: 256
name: mercurio.xxx.inet
net0: virtio=7A:58:F5:25:64:BA,bridge=vmbr0
onboot: 0
ostype: l26
sockets: 1
startup: order=30
virtio0: datastore1:vm-102-disk-1
#######################################

I looked also at the LVM config to see if there is something wrong, but,
as you can see, also LVM config is the same between 101 and 102.

#######################################
  --- Volume group ---
  VG Name               vgs1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  545
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                8
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               268,30 GiB
  PE Size               4,00 MiB
  Total PE              68686
  Alloc PE / Size       38656 / 151,00 GiB
  Free  PE / Size       30030 / 117,30 GiB
  VG UUID               8go58f-davq-Fvjb-k3c1-aDH6-j1n1-6NpJbt

  --- Logical volume ---
  LV Path                /dev/vgs1/vm-101-disk-1
  LV Name                vm-101-disk-1
  VG Name                vgs1
  LV UUID                ULBvgl-Xfzm-09g1-f4EM-2aGc-AdZb-9QMf02
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                15,00 GiB
  Current LE             3840
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:11

  --- Logical volume ---
  LV Path                /dev/vgs1/vm-102-disk-1
  LV Name                vm-102-disk-1
  VG Name                vgs1
  LV UUID                xOwFLM-9XUW-N4E6-8iQC-Xoot-ICKw-TjBVOL
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                15,00 GiB
  Current LE             3840
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:8

#######################################

Rebooting the hosts doesn't resolve the issue.

I cannot find any explanation for this behaviour... where can I
investigate further?

-- 
Flavio Visentin

IT Architect
Saidea SRL
Via Kufstein, 5
38121 - Trento (TN)
Tel. (+39) 0461 245589
Mail flavio.visentin at saidea.it