issue with Lock disk creation

[gab_in]

Hi,

We created a dedicated volume group /dev/vglck and allocated one disk /dev/dsk/c1t0d0 for the lock disk and it was working fine & there was an entry in the /etc/lvmtab file.

But it was removed from the /etc/lvmtab file along with other VGs by one of the team member my mistake.

We used the dedicated Lock Volume Group so we are sure this VG will never be deleted. Now we created the lock disk again but getting the below error message while using the cmruncl -v to start the cluster.

cmruncl: Validating network configuration...
cmruncl: Network validation complete
cmruncl: Validating cluster lock disk ...WARNING: Cluster lock on disk /dev/dsk/c1t0d0 is missing! Until it is fixed, a single failure could cause all nodes in the cluster to crash.
/dev/dsk/c1t0d0 is inaccessible
error
Failed to check cluster lock disks
. Done
Waiting for cluster to form ...... done
Cluster successfully formed.
Check the syslog files on all nodes in the cluster to verify that no warnings occurred during startup.


Need your help to create the lock disk again

Thanks in advance

[Duncan Edmonstone]

>> Now we created the lock disk again but getting the below error message while using the cmruncl -v to start the cluster.


How did you re-create the lock disk VG?

Probably just running a new cmapplyconf will re-create...

HTH

Duncan

[gab_in]

Thanks Duncan,

We removed the lock disk (PV) and Lock VG (/dev/vglck) and recreated the Lock PV & VG (/dev/vglck) again using the normal VG creation process. After that export from first node and import from second node, backup /etc/lvmtab and used vgscan -av to create the new /etc/lvmtab which has /dev/vglck entry.

Pls help

Thanks

[gab_in]

just wanted to update that we haven't used cmappyconf after the above process. We have just started the cluster using "cmruncl -v".

[smatador]

Hi,
I agree with Duncan, perhaps just to be sure.
activate it first
# vgchange -a y /dev/vglck
then do cmapplyconf
After it works deactivate
#vgchange -a n /dev/vglck
and start the cluster.
#cmruncl -v
If it's not good, perhaps you have an issue with the hardware, check after with
diskinfo /dev/rdsk/c1t0d0
pvdisplay /dev/dsk/c1t0d0
dd if=/dev/rdsk/c1t0d0 of=/dev/null bs=2048k
Hope it helps

[Duncan Edmonstone]

So by recreating the VG you have ovewritten the data in the disk header that the cluster lock mechanism uses... do to restore thsi you will have to re-apply the cluster configuration (which means having the cluster down)

once down, make sure the vglock vg is active on one node, then run:

cmapplyconf -v -C /etc/cmcluster/cmclconfig.ascii

Note you cluster configuration ASCII file may have a different name...

HTH

Duncan