HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array User Guide (5697-0733, Marc - Page 164
Windows Server, Sun Solaris, Table 57 HP-UX failure scenarios
View all HP 6100 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 164 highlights
Table 57 HP-UX failure scenarios (continued) Fault stimulus Controller restart Server path failure Storage path failure Failure effect Short term: Data transfer stops. Possible I/O errors. Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted, need mkfs disk. Short term: Data transfer stops. Possible I/O errors. Long term: Job hangs, cannot umount disk, fsck failed, disk corrupted, need mkfs disk. Short term: Data transfer stops. Possible I/O errors. Long term: Job hangs, replace cable, I/O continues. Without cable replacement job must be aborted; disk seems error free. Windows Server Table 58 Windows Server 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 OS runs a command called chkdsk when rebooting. Data lost, data that finished copying survived. Write delay, server hangs until I/O is cancelled or cold reboot. Write delay, server hangs or reboots. One controller failed, other controller and shelves critical, shelves offline. Volume not accessible. Server cold reboot, data lost. Check disk when rebooting. Controller momentarily in failed state, server keeps copying. All data copied, no interruption. Event error warning error detected during paging operation. Write delay, volume inaccessible. Host hangs and restarts. Write delay, volume disappears, server still running. When cables plugged back in, controller recovers, server finds volume, data loss. Sun Solaris Table 59 Sun Solaris 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 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. 164 Single Path Implementation