Command Reference Guide

Chapter 1: Matrix Server Commands 31

unlocked, trying to lock

The SANlock does not appear to be held. The host on which mxsanlk was

run is trying to acquire the SANlock.

unlocked

The SANlock does not appear to be held. If a host holds the SANlock, it

has not yet committed its hold.

initiating sdmp, not yet examined

This is a transitional state. It indicates that the sdmp process responsible

for the SANlock has been started but has not yet accessed the SANlock.

sdmp process hung

The SDMP process responsible for the SANlock is unresponsive.

trying to lock, sdmp process hung

The host on which mxsanlk was run is trying to acquire the SANlock but

the SDMP process responsible for the SANlock is unresponsive.

locked, sdmp process hung

The host on which mxsanlk was run held the SANlock but the SDMP

process responsible for the SANlock is now unresponsive.

lock is corrupt, will repair

This transitional state occurs after the SDMP has detected that the

SANlock has been corrupted but before it has repaired the SANlock.

trying to lock (lock is corrupt, will repair)

The host on which mxsanlk was run is trying to acquire the SANlock. The

SANlock was corrupted but will be repaired.

locked (lock is corrupt, will repair)

The host on which mxsanlk was run holds the lock. The SANlock was

corrupted but will be repaired.

If a membership partition cannot be accessed, use the mxmpconf program to

correct the problem.

When you invoke mxsanlk, it checks for the Storage Device Monitor Pulse

(SDMP) daemon. This daemon is responsible for grabbing and maintaining

the locks on the membership partitions.