Not able to create LV with error "Aborting. Failed to activate new LV to wipe the start of it " in cluster setup

Environment

• Red Hat Enterprise Linux Server release 5.3 (Tikanga)
• kernel-2.6.18-128.el5

Diagnostic Step

1) lvcreate fails with below error message.

lvcreate -n LVScalix01b -L 900G VGScalix01b 
Aborting. Failed to activate new LV to wipe the start of it.

2) Information about the setup.

# multipath -l 

mpath1 (3600a0b800026272400001c954a9b643e) dm-3 SUN,CSM200_R 
[size=976G][features=1 queue_if_no_path][hwhandler=1 rdac][rw] 
_ round-robin 0 [prio=0][active] 
 _ 14:0:2:2 sdc 8:32  [active][undef] 
_ round-robin 0 [prio=0][enabled] 
 _ 14:0:3:2 sde 8:64  [active][undef] 
mpath0 (3600a0b800026131c000012c44a9b6017) dm-2 SUN,CSM200_R 
[size=976G][features=1 queue_if_no_path][hwhandler=1 rdac][rw] 
_ round-robin 0 [prio=0][active] 
 _ 14:0:3:1 sdd 8:48  [active][undef] 
_ round-robin 0 [prio=0][enabled] 
 _ 14:0:2:1 sdb 8:16  [active][undef] 

# pvdisplay 
  --- Physical volume --- 
  PV Name               /dev/mpath/mpath0p1 
  VG Name               VGScalix01b 
  PV Size               975.86 GB / not usable 1.33 MB 
  Allocatable           yes  
  PE Size (KByte)       4096 
  Total PE              249821 
  Free PE               249821 
  Allocated PE          0 
  PV UUID               z78GJv-b77B-Xq8J-0zYG-rJ2M-qPiN-Bn1Gr6 

  --- Physical volume --- 
  PV Name               /dev/sda2 
  VG Name               VolGroup00 
  PV Size               135.87 GB / not usable 29.25 MB 
  Allocatable           yes (but full) 
  PE Size (KByte)       32768 
  Total PE              4347 
  Free PE               0 
  Allocated PE          4347 
  PV UUID               aNUDRr-4oFt-sQ5u-tUur-YRT3-4Gfj-n2AKdK

3 ) As per the lvm configuration file '/etc/lvm/lvm,conf' in the sosreport, the "Volume_list" parameter is defines as :

    # If volume_list is defined, each LV is only activated if there is a
    # match against the list.
    #   "vgname" and "vgname/lvname" are matched exactly.
    #   "@tag" matches any tag set in the LV or VG.
    #   "@*" matches if any tag defined on the host is also set in the LV or VG
    #
    # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]

volume_list = [ "VolGroup00", "@ksabscalixc01.ksab.kroschu.com" ]

As mentioned in the comments ( shown above) each LV is only activated if there is a match against the list . That being said, LVs on volume group "VolGroup00" can be activated OR LVs on Volume group which has the tag "@ksabscalixc01.ksab.kroschu.com" can be activated.

4) So does the subjected VG has this ( ksabscalixc01.ksab.kroschu.com ) tag ?  This can be checked with the help of the below command.

# vgs -o +vg_tags

5 ) If this particular volume group does not have this tag , try adding the tag to this VG and try to create LV. The command below can be used to add tag to the VG.

# vgchange --addtag <Tag> <Volume Group Name>

Here tag can be "ksabscalixc01.ksab.kroschu.com" and volume group can be "VGScalix01b".

6) Now check if the VG has the proper tag set, with the command :

#vgs -o +vg_tags

7) If it has the proper tag , try to create an LV on this VG .

# lvcreate -n LVScalix01b -L 900G VGScalix01b