Openvms And Tru64 Unix; Openvms And Tru64 Unix Failure Scenarios - HP StorageWorks 6400/8400 - Enterprise Virtual Array User Manual

Fault stimulus
Controller restart
Server path failure
Storage path failure

OpenVMS and Tru64 UNIX

Table 30 OpenVMS and Tru64 UNIX failure scenarios.
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
Controller restart
Server path failure
Storage path failure
Failure effect
Short term: Data transfer stops. Possible I/O errors.
Long term: Repeated error messages on console, no access to CDE.
System reboot causes loss of data on disk. Must newfs disk.
Short term: Data transfer stops. Possible I/O errors.
Long term: Repeated error messages on console, no access to CDE.
System reboot causes loss of data on disk. Must newfs disk.
Short term: Job hung, data lost.
Long term: Repeated error messages on console, no access to CDE.
System reboot causes loss of data on disk. Must newfs disk.
Failure effect
All I/O operations halted. Possible data loss from unfinished or
unflushed writes. File system check may be needed upon reboot.
OpenVMS—OS will report the volume in a Mount Verify state until
the MVTIMEOUT limit is exceeded, when it then marks the volume
as Mount Verify Timeout. No data is lost or corrupted.
Tru64 UNIX—All I/O operations halted. I/O errors are returned
back to the applications. An I/O failure to the system disk can cause
the system to panic. Possible data loss from unfinished or unflushed
writes. File system check may be needed upon reboot.
I/O fails over to the surviving path. No data is lost or corrupted.
OpenVMS—OS will report the volume in a Mount Verify state until
the MVTIMEOUT limit is exceeded, when it then marks the volume
as Mount Verify Timeout. No data is lost of corrupted.
Tru64 UNIX—I/O retried until controller back online. If maximum
retries exceeded, I/O fails over to the surviving path. No data is
lost or corrupted.
OpenVMS—OS will report the volume in a Mount Verify state until
the MVTIMEOUT limit is exceeded, when it then marks the volume
as Mount Verify Timeout. No data is lost or corrupted.
Tru64 UNIX—All I/O operations halted. I/O errors are returned
back to the applications. An I/O failure to the system disk can cause
the system to panic. Possible data loss from unfinished or unflushed
writes. File system check may be needed upon reboot.
OpenVMS—OS will report the volume in a Mount Verify state until
the MVTIMEOUT limit is exceeded, when it then marks the volume
as Mount Verify Timeout. No data is lost or corrupted.
Tru64 UNIX—I/O fails over to the surviving path. No data is lost
or corrupted.
HP StorageWorks 6400/8400 Enterprise Virtual Array user guide 125