HP StorageWorks Clustered Gateway 3.6.0 Windows Storage Server Edition Event Notification Guide (5697-7151, January 2008)

Chapter 3: Event Messages 38
17019 <server> is unresponsive and must be rebooted ASAP. Until this reboot is
done, some or all filesystem operations may be paused throughout the
cluster.
Action. The specified server did not respond to a critical request. This
problem may be caused by a severe overload or resource shortage on the
server. Rebooting the server should clear the problem.
17020 Unresponsive server <server> resolved.
Action. None. Alert 17019 is resolved.
17021 Operator error may have caused filesystem corruption! <server> returned to
the cluster without being rebooted, even though the operation verified that
<server> was down. It is recommended that all filesystems that had <server>
mounted be checked for corruption. This alert will display for 48 hours.
Action. Run psfscheck on all filesystems that were mounted on the affected
server. See the HP StorageWorks Clustered File System Command Reference for
information about this command.
17022 Down server <server> return problem resolved.
Action. None. Alert 17021 is resolved.
17023 <server> is stalled waiting for locks from <IP address> for the following
filesystem(s): <filesystems>.
Action. If this condition persists for more than five to 10 minutes, contact
HP Support for assistance.
17024 Stalled server <server> waiting for filesystem locks resolved.
Action. None. Alert 17023 is resolved.
17025 Filesystem <filesystem> suspended.
Action. The filesystem has been suspended by the HP Clustered File System
psfssuspend command or by a third-party application such as a backup
utility. Writes to the filesystem will be blocked until the filesystem is
resumed. If the filesystem was suspended with the psfssuspend command,
it can be resumed with the psfsresume command.
17026 Filesystem <filesystem> resumed.
Action. None. Alert 17025 is resolved.
ID Message and Corrective Action