Netware; Linux; Netware Failure Scenarios; Linux Failure Scenarios - HP StorageWorks 6400/8400 - Enterprise Virtual Array User Manual

NetWare

Table 31 NetWare failure scenarios.
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
Controller restart
Server path failure
Storage path failure

Linux

Table 32 Linux failure scenarios.
Fault stimulus
Server failure (host power-cycled)
Switch failure (SAN switch disabled)
Controller failure
126 Single Path Implementation
Failure effect
OS reboots. When mounting volumes, volume repair or NSS rebuild
executes to cleanup volumes. Data loss, data that finished writing
survived.
I/O to device stops with I/O errors indicated on server console.
Applications using lost connection halts. Server restart recommended
but may not be necessary. Volume repair or NSS rebuild runs when
volumes are mounted.
I/O to device stops with I/O errors indicated on server console.
Applications using lost connection halts. Server restart recommended
but may not be necessary. Volume repair or NSS rebuild runs when
volumes are mounted.
I/O to device stops with I/O errors indicated on server console.
Applications using lost connection halts. Server restart recommended
but may not be necessary. Volume repair or NSS rebuild runs when
volumes are mounted.
I/O to device stops with I/O errors indicated on server console.
Applications using lost connection halts. Server restart recommended
but may not be necessary. Volume repair or NSS rebuild runs when
volumes are mounted.
I/O to device stops with I/O errors indicated on server console.
Applications using lost connection halts. Server restart recommended
but may not be necessary. Volume repair or NSS rebuild runs when
volumes are mounted.
Failure effect
OS reboots, automatically checks disks. HSV disks must be manually
checked unless auto mounted by the system.
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.
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.