serviceguard cluster configuration problem (vgchange)

[Rob Payne]

I am attempting to configure a single-node cluster. I created a volume group called vgprod which contains the raw logical volumes for installing RAC and 10g, as well as the cluster lock disk. Some of these logical volumes are mirrored using Mirror/UX.

I have made some changes to my cluster config file, checked them with cmcheckconf, and now want to apply the changes with cmapplyconf. To do this I need to activate the volume group.

When I attempt the command 'vgchange -a y /dev/vgprod', I get the following error:

vgchange: Activation mode requested for the volume group "/dev/vgprod" conflicts with configured mode.

What have I done wrong?

cheers ... rob

[Neil Wilson_2]

Hi Rob

I think you need to use a -c to tell it to mark the vg as a member of high availability cluster, e.g.

vgchange -c y vgprod

See if it works

Neil.

[Alex Lavrov.]

I think you need:

vgchange -c y /dev/vgprod


And then try again.

[melvyn burnard]

When you created your cluster, this marked vgprod as cluster aware.
This means that to activate the vg the clluster daemon cmcld needs to be running, i.e your cluster must be running.
If you need to activate the vg outside of the cluster, do:
vgchange -c n vgprod
vgchange -a y vgprod


Remember to mark the vg as cluster aware again before using it inside the cluster
vgchange -c y


Out of interest, why create a single node cluster for SGeRAC? as this is designed to be used on multiple nodes at the same time.
Also, for a single node cluster you do not need a cluster lock disc.

[Rob Payne]

this is the result of that command:


# vgchange -c y /dev/vgprod
vgchange: Cluster Services not available or unreachable on this system, for volume group "/dev/vgprod".

[Rob Payne]

Melvyn

I currently only have one node to work with. The other node has not been released to me yet, so I am attempting to set up a one one cluster, and add the other node later.

cheers .. rob

[melvyn burnard · Accepted solution]

Ok, so that explains that then.
You will still need to mark the vg as not part of a cluster to activate it while Servcieguard is not running.
vgchange -c n vgprod
vgchange -a y vgprod

Leave it activated while doing the cmapplyconf and this will mark it as cluster aware again.

[Rob Payne]

thanks all, the vgchange -c n /dev/vgprod did it

[Rob Payne]

thanks