3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

unlikely; however, if HP Scalable NAS cannot be started on any server in the cluster,
you can use the following command to determine whether all membership partitions
have a valid Cluster-ID.
mprepair --sync-clusterids
The command displays the Cluster-IDs found in each membership partition and flags
those partitions containing an invalid ID. You can then specify whether you want the
command to repair the partitions having a mismatched Cluster-ID.
mprepair --get_current_mps can also be used to obtain more information
about the membership partitions.
Increase the membership partition timeout
Under heavy I/O load, I/O timeouts can occur on membership partition accesses.
The I/O timeouts are reported as SCSI error : <...> return code = 50000
in the file /var/log/messages. The I/O timeouts can cause problems such as the
following:
• Excessive path switching.
• Filesystems appearing to be hung when a node crashes. Large numbers of I/O
timeouts can extend the time it takes to fence the node, and filesystem operations
cannot resume until the node is fenced.
If your site is experiencing the above problems due to I/O timeouts, you may want
to increase the I/O timeout parameter for accessing membership partitions. You will
need to set the timeout on each node currently in the cluster and on any nodes added
to the cluster.
Before setting the timeout, be sure to stop HP Scalable NAS.
To increase the timeout, edit the file /etc/opt/hpcfs/mxinit.conf. Locate the
following line in the file:
# sanpulse_start_options = { "--mxinit" };
You will need to add the parameter "-o sdmp_io_timeout=<millisec>" to
the start options. Also remove the comment character (#) from the beginning of the
line:
sanpulse_start_options = { "--mxinit","-o sdmp_io_timeout= <millisec>" };
<millisec> is the number of milliseconds to be used as the I/O timeout for
accessing membership partitions. The default value is 30,000ms (30 seconds). Be
sure to increase the timeout value in small increments, such as 5,000ms. If the timeout
SAN maintenance370