3.4.0 Matrix Server Administration Guide

Chapter 17: SAN Maintenance 193

• 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 mprepair program

to correct the problem.

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

Pulse (SDMP) process. This process is responsible for grabbing and

maintaining the locks on the membership partitions. Depending on the

status of the SDMP process, 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 process 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 process. If

you continue to have problems, contact PolyServe Technical Support.

Manage Membership Partitions with mprepair

Each server in the matrix has a membership partition file, which is called

the “local MP list.” This file specifies the locations of the membership

partitions. Each membership partition also has its own MP list. Because

the membership partitions control access to the SAN, it is important that

each server in the matrix have the same view of where the partitions are

located.

However, it is possible for these views to get out of sync if changes to the

membership partition configuration are made when all servers are not

accessible. Therefore, before a server can negotiate for control of the SAN,

it must have a local MP list that matches the membership lists stored on

each of the membership partitions, and each membership partition must

be in the Active state.