HP 6400.8400 Enterprise Virtual Array - Manual (Page 133)

OpenVMS and Tru64 UNIX
Table 33 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. Switch failure (SAN switch disabled)
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. 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. Controller restart
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. Server path failure
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. Storage path failure
Tru64 UNIX—I/O fails over to the surviving path. No data is lost or
corrupted.
Linux
Table 34 Linux failure scenarios
Failure effect Fault stimulus
OS reboots, automatically checks disks. HSV disks must be manually
checked unless auto mounted by the system. Server failure (host power-cycled)
Short: I/O suspended, possible data loss.
Long: I/O halts with I/O errors, data loss. HBA driver must be reloaded
before failed drives can be recovered, fsck should be run on any failed
drives before remounting. Switch failure (SAN switch disabled)
Short term: I/O suspended, possible data loss.
Long term: I/O halts with I/O errors, data loss. Cannot reload driver,
need to reboot system, fsck should be run on any failed disks before
remounting. Controller failure
Short term: I/O suspended, possible data loss.
Long term: I/O halts with I/O errors, data loss. Cannot reload driver,
need to reboot system, fsck should be run on any failed disks before
remounting. Controller restart
Failure scenarios 133