[linux-lvm] pvmove fails on VG, managed by PCS resource agent in HA-LVM mode(Active-Passive), with tagging enabled.

[linux-lvm] pvmove fails on VG, managed by PCS resource agent in HA-LVM mode(Active-Passive), with tagging enabled.

[Udai Sharma]

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hi,
pvmove seems to fail on VG, which is managed by PCS Resource agent with
'exclusive' activation enabled.

The volume group(VG) is created on a shared disk, with '--addtag test'
added.
Content of my lvm.conf is
#lvmconfig activation/volume_list
volume_list=["@test"]

I am able to create Logical volume over it, vgextend, vgremove everything
works fine.
When I tried to do pvmove, it fails with error that lvm cannot activate
vg0/pvmove0.

On probing little further, I found that when I create LVM PCS resource
agent with 'exclusive=true', it strips-off the original tag 'test'
and adds its own 'pacemaker' tag.
Since VG was stripped-off with original tag, I think, that is the reason of
pvmove is getting failed.

I am out-of ideas to debug this further. Need some expert advice/solution
to handle this situation.

Also, how to use lvmconfig utility to modify volume_list, without the need
manually update lvm.conf file?

-Udai

[-- Attachment #2: Type: text/html, Size: 1264 bytes --]

[linux-lvm] pvmove fails on VG, managed by PCS resource agent in HA-LVM mode(Active-Passive), with tagging enabled.

[Udai Sharma]

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hi,
pvmove seems to fail on VG, which is managed by PCS Resource agent with
'exclusive' activation enabled.

The volume group(VG) is created on a shared disk, with '--addtag test'
added.
Content of my lvm.conf is
#lvmconfig activation/volume_list
volume_list=["@test"]

I am able to create Logical volume over it, vgextend, vgremove everything
works fine.
When I tried to do pvmove, it fails with error that lvm cannot activate
vg0/pvmove0.

On probing little further, I found that when I create LVM PCS resource
agent with 'exclusive=true', it strips-off the original tag 'test'
and adds its own 'pacemaker' tag.
Since VG was stripped-off with original tag, I think, that is the reason of
pvmove is getting failed.

I am out-of ideas to debug this further. Need some expert advice/solution
to handle this situation.

Also, how to use lvmconfig utility to modify volume_list, without the need
manually update lvm.conf file?

-Udai

[-- Attachment #2: Type: text/html, Size: 1362 bytes --]