Managing Disk Array Logs - HP Surestore Disk Array 12h - And FC60 Advanced User's Manual

A parity scan compares the data and its associated parity to ensure they match. A parity
scan cannot be performed on a LUN that has experienced a disk failure and is operating in
degraded mode.
Although RAID 1 LUNs and 0/1 LUNs do not use parity, you can still perform a parity scan
on them. The parity scan compares the data on the mirrored disks.
What should I do if parity errors are detected?
Note
If errors are detected during a parity scan, it is recommended that you contact
your Hewlett-Packard service representative immediately. The occurrence of
parity errors may indicate a potential problem with the disk array hardware.
Displaying Parity Scan Status
If a parity scan is in progress, you can monitor its progress. This will help you determine
how much longer the parity scan will take.
To display parity scan progress, type:
ammgr -s <LUN> <ArrayID>
Halting a Parity Scan
You can halt a parity scan currently in progress. This may be useful if the parity scan is
impacting performance and you want to reschedule it to run when the host is less busy.
To halt a parity scan, type:
ammgr -H <LUN> <ArrayID>

Managing Disk Array Logs

The disk array controller continuously gathers and stores information on all aspects of disk
array operation. Array Manager 60 retrieves these controller log entries at regular intervals
and stores them in a log directory on the host (/var/opt/hparray/log). The log files
are valuable in monitoring disk array operation and isolating problems that may occur.
On HP08 and later, major event logging is available. MAjor event logging provides more
detailed information on disk array operation. Many events that were not logged in the
Managing the Disk Array Using Array Manager 60
307