3.5.1 Matrix Server Command Reference

Chapter 1: Matrix Server Commands 32

# mxsanlk

This host: 99.10.30.3

This host’s SDMP administrator: 99.10.30.1

Membership Partition SANlock State

-------------------- -------------

/dev/rpsd/psd1p1 held by SDMP administrator

/dev/rpsd/psd2p1 held by SDMP administrator

/dev/rpsd/psd3p3 held by SDMP administrator

Any of these messages can appear in the “SANlock State” column.

held by SDMP administrator

The SANlock was most recently held by the SDMP administrator of the

matrix to which the host where mxsanlk was run belongs.

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