3.5.1 Matrix Server Command Reference

Chapter 1: Matrix Server Commands 33

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.

Depending on the status of the SDMP daemon, you may see one of the

following messages:

Checking for SDMP activity, please wait...

Still trying...

The SDSMP is inactive at this host.

The SDMP appears to be inactive at this host.

If the SDMP daemon is not responding on the host, wait a few seconds and

retry the command. If the command continues to fail, shut down the matrix

and then restart it. This step should restart the SDMP daemon. If you

continue to have problems, contact PolyServe Technical Support.