vgchange conflicts with configured mode

[Steven Boyer]

VG works fine on primary, and we vgchange -a n /dev/vg on the primary to make active on the second node.
however on the secondary when we do a vgchange -a y /dev/vg we get "vgchange conflicts with configured mode"

[Vihang.]

Hi Steven,

Is the VG cluster aware? If yes, then it wont allow you to activate the vg using vghchange -a y option. You will need to run vgchange -a e /dev/vg. This will activate the vg in exclusive mode which is the default behaviour of cluster aware vgs. If you want to activate as a non cluster aware vg, then first run vgchange -c n /dev/vg & then vgchange -a y /dev/vg.

Hope this helps.

Regards,
Vihang.

[Sandeep_Chaudhary]

u have to run "vgchange -a e /dev/vgname"

to activate vg insted og "vgchange -a y vgname" as in cluster mode u r exclusively activating vg.

[Jeeshan]

Hi

instead of

vgchange -a y /dev/vg

use
vgchange -a e /dev/vg

if it is part of a cluster.
Run the command from the server who owns the disk.