Cluster Lock Disk.

[DeafFrog]

Dear Gurus,

Here's a working configuration :
CCMT3:/etc/cmcluster#more cluster1.conf | grep -v "^#"
CLUSTER_NAME cluster1
FIRST_CLUSTER_LOCK_VG /dev/vg01
NODE_NAME CCMT3
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.0.1.3
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan5
HEARTBEAT_IP 67.57.0.1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c24t0d1 <==the lock disk on node
NODE_NAME CCMT4
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.0.1.2
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan5
HEARTBEAT_IP 67.57.0.2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t0d1
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 5000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
NETWORK_FAILURE_DETECTION INOUT
MAX_CONFIGURED_PACKAGES 150
---
CCMT3:/#diskinfo /dev/rdsk/c24t0d1
SCSI describe of /dev/rdsk/c24t0d1:
vendor: HP
product id: HSV210
type: direct access
size: 52428800 Kbytes
bytes per sector: 512
----

=======from lvdisplay -v===
--- Logical extents ---
LE PV1 PE1 Status 1
00000 /dev/dsk/c24t0d1 00000 current <=lock not existing at extent "0" ?
00001 /dev/dsk/c24t0d1 00001 current
00002 /dev/dsk/c24t0d1 00002 current
00003 /dev/dsk/c24t0d1 00003 current

CCMT3:/#bdf | grep vg01
/dev/vg01/lvol1 82944000 23841472 55424585 30% /timeapp <==lock disk also hosts a FS.

=====
from my previous experince the lock disk should be of 100 ~ 300 mb and should not host any FS .is that correct.am i being too apprensive or is there something wrong with this cluster configuration.Please let know if you require more o/p

Regards,

[Torsten. · Accepted solution]

The lock disk is a real disk, not a LVOL

FIRST_CLUSTER_LOCK_PV /dev/dsk/c24t0d1

A reserved block is used for this purpose, so don't worry about file systems.


You have a duplicated

FIRST_CLUSTER_LOCK_PV

entry!

[Torsten.]

Refer to the chapter

Use of a Lock LUN or LVM Lock Disk as the Cluster Lock

in SG manual.

[Jeeshan]

It's not mandetory that you cannot create file system in cluster lock disk.

But it's good to use unallocated FS disk.

[DeafFrog]

Hello Torsten and unix_sheel,

Many thanks for the prompt reply .
i can assign LUN frm EVA , do a pvcreate on it , add it to a new VG vg01 , create a cluster ,create a LV and FS on the lock disk , do a vgchange -a n /dev/vg01 , vgchange -c y /dev/vg01 ,create a package configuration file , add the vg01 to the conf and the new lv and apply the package conf file ..am i missing something .

Regards,

[Torsten.]

As said, refer to the manual section; the lock disk vs. lock LUN topic is discussed there.

[DeafFrog]

Trosten and Unix_shell 's posting helped.
Regards,