Sun Solaris
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
Controller restart
Server path failure
Storage path failure
OpenVMS
Fault stimulus
Server failure (host
power-cycled)
Switch failure (SAN
switch disabled)
Controller failure
Controller restart
Failure effect
Check disk when rebooting. Data loss, data that finished copying
survived.
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: 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
Nonclustered-Processes fail.
Clustered—Other nodes running processes that used devices served from the
single-path HBA failed over access to a different served path. When the single-path
node crashes, only the processes executing on that node fail.
In either case, no data is lost or corrupted.
I/O is suspended or process is terminated across this HBA until switch is back online.
No data is lost or corrupted.
The operating system 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.
I/O fails over to the surviving controller. No data is lost or corrupted.
I/O is suspended or process is terminated across this HBA until EVA is back online.
No data is lost or corrupted.
The operating system 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.
HP StorageWorks 4400 Enterprise Virtual Array user guide
75