HP 6400/8400, Руководство пользователя

Страница: 125 / 150

Failure effect Fault stimulus
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.
Controller restart
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.
Server path failure
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.
Storage path failure
OpenVMS and Tru64 UNIX
Table 30 OpenVMS and Tru64 UNIX failure scenarios.
Failure effect Fault stimulus
All I/O operations halted. Possible data loss from unfinished or
unflushed writes. File system check may be needed upon reboot.
Server failure (host power-cycled)
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.
Switch failure (SAN switch disabled)
I/O fails over to the surviving path. No data is lost or corrupted. Controller failure
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.
Controller restart
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.
Server path failure
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.
Storage path failure
HP StorageWorks 6400/8400 Enterprise Virtual Array user guide 125