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
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
