basic cluster build question

[Jim Graefe_1]

This should be an easy one.... for some reason I can figure this out today.

I am working on a lab system for a review before doing this for real.

I am setting up a new cluster:

sys1 -
create vgtest
create lvol1
newfs lvol1
mount lvol1
unmount lvol1
vgexport -p -v -s -m mapfile vgtest

sys2 -
create /dev/vgtest
mknod group ...
vgimport -v -s -m mapfile vgtest

(All is well up to here)

vgchange -a y vgtest
vgchange: Activation mode requested for the volume group "/dev/vgtest" conflicts with configured mode.

OK- It's not cluster aware...

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

Hmmm.... make sure it's deactivated and check it out again on sys1

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


OK - Now I'm confused...
I have done this before (Really!) and it worked. I am actually folling the online docs.

Any help would be appreciated.

[RAC_1]

Is MCSG properly installed on the system??
If yes,

vgchange -s y vgtest
vhchange -c y vgtest
vgchange -a e vgtest

man vgchange for details.

[Jeff Schussele]

Hi Jim,

The cluster daemon needs to be running on the system when you turn off/on the VG cluster bit.

ps -ef | grep cmcld

The cluster doesn't have to be "up", but the daemon must be active.

Rgds,
Jeff

[Duncan Edmonstone]

Jim,

I don't know if you just missed it out, but you appear to have done a vgchange -a y on sys2 having not previously done a vgchange -a n on sys1... At this stage (i.e. before building a base cluster) you shouldn't be worrying about making the VG cluster aware... these will only come into play once you do your first cmapplyconf...

HTH

Duncan

[Jim Graefe_1]

All I was trying to do was set up the shared VG. That should work without the cmcld running right? I just followed along the docs.

All of the responses we good. For some reason, I ran

vgchange -c n vgtest

on sys1. Then I was able to import/activate/mount on sys2. I could then sucessfully reverse the process as well.

That seems strange. I don't know about patches on this system. It may be missing something.

Thanks for the help

Jim

[Jeff Schussele]

Jim,

I used to think so as well. But have had occasion where I needed cmcld running to do this.

Note from your initial post

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

Was cmcld active when you finally resolved this?

Rgds,
Jeff

[Jim Graefe_1]

Nope. No cmcld.

This is a lab setup and another engineer was folling with it first. I deleted the packages and cluster that were on it so everything was shut down. It should have been a relatively clean setup.

I will try another vg later and see how it behaves.

But I should be able to do what I was trying to do right? Or do I need to set it up as shared when I create it. I can't seem to remember. That's why I was following the docs step by step. A lot of good that did huh?

[Stuart Abramson]

the "vgchange" man page says that you must run vgchange -a n VG before you run vgchange -c y. It also states that "the HA software must be running".

[Stuart Abramson]

RAC:

do you really need to do that:

vgchange -s y
vgchange -c y
vgchange -a e

business for a "normal" cluster where the VG is only active on one server at a time?

[Jim Graefe_1]

I don't remember ever doing all that. But it has been about a year since I built a cluster.

I would usually -
create the vg / lvols
activate / mount / test
create map files
umount / deactivate

import the vg on sys2
activate / mount /test
umount /deactivate

ready for the next step.

[Kevin Wright]

vgchange -a y vgtest
vgchange: Activation mode requested for the volume group "/dev/vgtest" conflicts with configured mode.

OK- It's not cluster aware...


This actually means the VG IS cluster aware, as you can't activate a cluster aware VG with -a y. Must be -a e/-a s.

Somehow the cluster flag was set in the LVM headers.