Adding a New Volume Group to a Service Guard cluster

[EJ Stremler]

I had some existing volume groups where someone imported them on the other node, but never made it part of the cluster, they are presently activated by vgchange -a y.. Should I deactivate these volume groups by vgchange -a n, add them to the Cluster Ascii file, and do the cmapplyconf which will mark them as cluster aware?.. If the package is down, then i'll let the control script activate these VGs when i bring it up.. Sounds correct? ed

[A. Clay Stephenson · Accepted solution]

You are leaving out the step "vgchange -c y". Anywhere that you have "vgchange -a y" will now need to become "vgchange -a e".

[EJ Stremler]

Hi Clay, that was basically my question. I thought the cmapplyconf changes any non-cluster aware VGs in the ascii file to cluster aware. Do we still need to do the vgchange -c y? ed

[A. Clay Stephenson]

Yes, you can put them in the cluster.ascii file and they will be made cluster aware although I generally do this as a separate step and run the vgchange -c y command. The good news is that the vgchange -c y can be done on any node and it applies to all --- without the need to run cmapplyconf. It's a good technique because then you can test the vgchange -a e on all nodes before actually starting the package. This lets you get all of the LVM related stuff out of the way before doing any other package related work.

[EJ Stremler]

This sounds like a plan, and an easier way to do this by just doing the vgchange -c y, although I will still update the cluster ascii file anyway.. Does the addition of volume groups to the cluster ascii file and running a cmapplyconf make any changes to the binary, or is it just a feature of the cmapplyconf command to make these VGs cluster aware with not changing the binary at all? Just trying to understand how this wors..

[EJ Stremler]

This sounds like a plan, and an easier way to do this by just doing the vgchange -c y, although I will still update the cluster ascii file anyway.. Does the addition of volume groups to the cluster ascii file and running a cmapplyconf make any changes to the binary, or is it just a feature of the cmapplyconf command to make these VGs cluster aware with not changing the binary at all? Just trying to understand how this works..

[EJ Stremler]

This is the answer i was looking for.. this is an issue with a production system, and I needed the easiest way to accomplsh the task..