3.4.0 Matrix Server Command Reference

Chapter 1: PolyServe Matrix Server Commands 18

• trying to lock, last held by host X.X.X.X

The SANlock was most recently held by host X.X.X.X and may still be held

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

SANlock.

• cannot access

The host on which mxsanlk was run is unable to access the SANlock.The

membership partition may need to be repaired.

• trying to lock, cannot access

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

is unable to access it. The membership partition may need to be repaired.

• locked, cannot access

The host on which mxsanlk was run held the SANlock but is now unable

to access it. The membership partition may need repair.

• trying to lock, not yet committed by owner

The SANlock is either not held or has not yet been committed by its

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

SANlock.

• 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.