shared LVM group for lock disk

[borut kurnik_1]

Hello!

I've got two rx4640 hosts (HP-UX 11.23 MCOE)
oradbsrv1 and oradbsrv2 accesing shared
volumes on EVA 6000.

So far I've created LVM volume group
/dev/sglck1 with one physical disk
(EVA provided LUN) /dev/dsk/c5t0d7
and SG cluster configuration file
/etc/cmcluster/clm.asc.

cmquerycl -v -n oradbsrv1 -n oradbsrv2 returns
----------------------------------------------
....
Possible Cluster Lock Devices:

LVM volume groups:

/dev/sglck1 oradbsrv1

LVM physical volumes:

/dev/sglck1
/dev/dsk/c5t0d7 0/4/2/0.2.0.0.0.0.7 oradbsrv1

LVM logical volumes:

Volume groups on oradbsrv1:

Volume groups on oradbsrv2:
---------------------------------------------

But I cannot cmapplyconf ... to run the
cluster sw:
-----------------------------------------
[root@oradbsrv1]# cmapplyconf -C clm.asc
Begin cluster verification...
First cluster lock volume group /dev/sglck1 needs to be designated as a cluster aware volume group.
cmapplyconf: Unable to verify cluster file: clm.asc.
-----------------------------------------

And I cannot make volume group shareable ...

--------------------------------------------
[root@oradbsrv1]# vgchange -c y /dev/sglck1
vgchange: Cluster Services not available or unreachable on this system, for volume group "/dev/sglck1".
---------------------------------------------

Please, how do I make LVM group shareable to
be able to provide lock disk and run the
SG cluster?

Thanks,

Borut

[A. Clay Stephenson]

I think that you have the FIRST_CLUSTER_LOCK_VG /dev/sglck1 line in your cmapplyconf ASCII file but you did not include the VOLUME_GROUP /dev/sglck1 line to include in the cluster aware VG list in the same file.

[Ian Vaughan · Accepted solution]

Hi,
What do you get back when you "vgdisplay" /dev/sglck1 on both hosts?

That volume group should be active on the node that you run cmapplyconf from and no other.

regards
ian

[borut kurnik_1]

Hi and thanks for the quick answer, guys!

You were both right.

I added VOLUME_GROUP line for /dev/sglck1
volume group.

The next message was:
-------------------------------------------
[root@oradbsrv1]# cmapplyconf -C clm.asc
Begin cluster verification...
Need not have to look for shared VGs
First cluster lock volume group "/dev/sglck1" is not available on all nodes. Choose a volume group that is available on all nodes.
Unable to find find first cluster lock volume group "/dev/sglck1" on node "oradbsrv2" but found it in cluster "oradbclu1".
cmapplyconf: Unable to verify cluster file: clm.asc.
-------------------------------------------


I cannot create VG on the other node, even
when I deactivate /dev/sglck1 on first
node (oradbsrv1).

-------------------------------------------
[root@oradbsrv1]# vgchange -a n /dev/sglck1
vgchange: Volume group "/dev/sglck1" has been successfully changed.

[root@oradbsrv2]# vgcreate /dev/sglck1 /dev/dsk/c5t0d7
Increased the number of physical extents per physical volume to 2559.
vgcreate: Volume group "/dev/sglck1" could not be created:
Device busy
-------------------------------------------

Looking forward to hearing from you soon and
thanks,

Borut

[A. Clay Stephenson]

I think that you need to run vgchange -c n /dev/sglck1 and then run cmapplyconf. I assume that you have actually vgimported the VG's to all the nodes.

[borut kurnik_1]

Hi!