HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 19: SAN Maintenance 239
• 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.
• 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.