volume group not activated

[shankar!]

Hi,

I have two node cluster srv1 srv2, the cluster and package is up and running. The shared volumes on srv1 mounted well, but not on srv2. It shows,

srv2:root> vgdisplay
--- Volume groups ---
VG Name /dev/vg0
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 4454
Free PE 4294
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg02".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg01".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg03".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg04".
You have mail in /var/mail/root

I tried,
srv2:root> vgchange -a s vg01
vgchange: Activation mode requested for the volume group "/dev/vg01" conflicts with configured mode.
srv2:root> vgchange -a e vg01
vgchange: Activation of volume group "/dev/vg01" denied by another node in the cluster.
Request on this system conflicts with Activation Mode on remote system.
srv2:root> vgchange -a y vg01
vgchange: Activation mode requested for the volume group "/dev/vg01" conflicts with configured mode.

Due to this, the oracle server is not running on srv2 server. can someone help us on this?

Thanks
-shankar

[Pete Randall]

Maybe this helps:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1241524129857+28353475&threadId=1205866


Pete

[shankar!]

Thanks for your speedy response. But that link seems not much help to our situation.

thans
-shankar

[Torsten.]

First you should check the cluster status and vgdisplay output on the other node to get the current status and configuration. Inspect the cluster config as well to know about what mode to use.

[smatador]

Hi,

Change the flag cluster to no, and active it on exclusive
# vgchange -c n /dev/vg01
# vgchange -a e /dev/vg01
# vgchange -a y /dev/vg01
You could like that, activate the vg in local.

Hope it helps

[likid0]

Hi,

Check in your first node where the vgs are active if they are in shared mode, do:

#vgdisplay -v /dev/vgshared | grep "VG Status"
VG Status available, shared,master

You should get out like above, if you don't then looks like it isn't activated in shared mode. If that's the case you should do, on the first node with SG runing:

/usr/sbin/vgchange -c cluster -S sharable vg_name

and then:

vgchange -a s vg_name

and finally on the second node:

vgchange -a s vg_name

[shankar!]

Here is the cluster status and vgdisplay output

srv1:root> cmviewcl -v

CLUSTER STATUS
hprac up

NODE STATUS STATE
srv1 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/3/1/0/5/0 lan2

PACKAGE STATUS STATE AUTO_RUN NODE
beserv_pkg up running enabled srv1

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 172.16.0.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled srv1 (current)
Alternate up enabled srv2

NODE STATUS STATE
srv2 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/3/1/0/5/0 lan2


srv1:root> vgdisplay
--- Volume groups ---
VG Name /dev/vg0
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 7194
Free PE 1554
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg01
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 6
Open LV 6
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 15256
Free PE 2243
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg02
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 16375
Free PE 1124
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg03
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 8125
Free PE 9374
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg04
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 8381
Free PE 9118
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

thanks
-shankar

[Torsten.]

The status of all VGs are available, exclusive from server1, so you cannot activate them from the other server until the packages are stopped.

[shankar!]

yes, the volumes are not sharable. I did the following on the first node (srv1),

srv1:root> /usr/sbin/vgchange -c hprac -S sharable /dev/vg01
Usage: vgchange
{-a Availability -q Quorum [-l] [-p] [-s] [VolumeGroupName... ]}
{[-S shareable] -c cluster VolumeGroupName}
{[-P parallel_nomwc_resync_count]}
"cluster": Bad value supplied. Legal values are "yn".

any help?
thanks

[shankar!]

so, should i stop the cluster on both nodes using cmhaltcl and then execute above commmands and then run cluster?

thanks

[Torsten.]

Are you really sure your configuration will work with shared volumes groups? If not, your data on it will be corrupted soon.

[shankar!]

Torsten,

I think this should be in shared mode as I recall last time I saw output as shared. These are basically for oracle RAC clusters so they should be in shared mode. Is there anyway we can find out the status (shared/exclusive) to prior to this problem?

Thanks
-shankar

[Torsten.]

Volume group commands are all logged into syslog - have a look.

[shankar!]

I confirmed with my co-worker who says these should be in shared mode. So, following above steps given an error

srv1:root> /usr/sbin/vgchange -c cluster -S sharable /dev/vg01
Usage: vgchange
{-a Availability -q Quorum [-l] [-p] [-s] [VolumeGroupName... ]}
{[-S shareable] -c cluster VolumeGroupName}
{[-P parallel_nomwc_resync_count]}
"cluster": Bad value supplied. Legal values are "yn".

please someone give the correct syntax/command.

thanks
-shankar

[shankar!]

I did something now the package shows disabled

UNOWNED_PACKAGES

PACKAGE STATUS STATE AUTO_RUN NODE
beserv_pkg down halted disabled unowned


volumes are dismounted, is there any way how to fix this? how to make package enable?

Please help

thanks
-shankar

[Sajjad Sahir]

Dear Friend

vgchange -S y -C y then volume group name.

thanks and regards

Sajjad Sahir

[shankar!]

I was able to start the package using cmrunpkg command

Thanks all.

-Shankar

[Md. Minhaz Khan]

Dear

You can keep your mind the below steps:

#cmhaltcl -f -v

#
vgchange -a n vg_name ## all nodes.
vgchange -S y -c y vg_name ## all nodes
vgchange -a s vg_name ## all nodes.
vgdisplay -v vg_name ## to view status

#

#cmruncl -v

[Stephen Doud]

Umm - you should not have to manually run the vgchange commands. You should have Serviceguard packages that activate the VGs in shared mode before launching Oracle RAC instance startup on each node.

If you are trying to configure a VG for shared activation, you would first start the cluster, then run:
# vgchange -c y -S y
This will 'clusterize' the VG (place the cluster ID on the LVM metadata on disk).
You would not be able to do this unless Serviceguard with extendsions for Real Application Clusters (SGeRAC) were installed.


The package control script (legacy model) has a VGCHANGE parameter that you would set to "vgchange -a s" and then you would identify the VGs that you want to activate in shared mode.

You also need to include the VG names in the cluster ASCII file. Example:
OPS_VOLUME_GROUP /dev/vg01

Be advised that once a VG is marked 'shared', LVM modification commands will not work on the VG. It must be mark to activate in standard or exclusive mode before you can modify the VG or lvol in the VG.