4.0.0 HP Polyserve Matrix Server Administration Guide (T5392-96052, March 2010)

Operator error may have caused filesystem corruption! 99.10.20.4
returned to the cluster without being rebooted, even though the
operator verified that 99.10.20.4 was down. It is recommended that
all filesystems that 99.10.20.4 had mounted be checked for corruption.
This alert will display for 48 hours.
Storage
Online insertion of new storage
Matrix Server supports online insertion (OLI) of new storage, provided that OLI support
is present for your combination of storage device, SAN fabric, HBA vendor-supplied
device driver, and the associated HBA vendor-supplied libhbaapi. (Check with your
vendors to determine whether OLI is supported.)
NOTE:
OLI of new storage can cause an interruption of normal operations on your storage
device. Because of this, it is recommended that OLI of new storage be scheduled for
off-peak hours.
When the appropriate lower-level OLI support is in place, inserting a new disk will
cause a new device to automatically become eligible for importing. The disk can be
imported with the PolyServe Management Console or mx utility, and can be used
normally from that point forward.
If OLI is not possible with your hardware combination, you will need to restart Matrix
Server after inserting a new disk. The disk will then be visible to the cluster.
Recommendations for storage capacity upgrades
When the drives in a storage array such as the HP Storageworks EVA are being
replaced to increase capacity, the array rebalances the data as each drive is
replaced. This activity can impact the performance of the active cluster, as the latent
I/Os generated by the data rebalancing can trigger Matrix Server timeouts.
When planning a disk upgrade process, in addition to following the best practices
recommended for your particular array, you should also consider increasing the
following Matrix Server timeouts.
HP PolyServe Matrix Server administration guide 259