HP 6400/8400 HP StorageWorks 6400/8400 Enterprise Virtual Array User Guide - Page 129

OpenVMS and Tru64 UNIX, Linux, Table 31 Oracle Solaris failure scenarios

Get HP 6400/8400 PDF manuals and user guides View all HP 6400/8400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 129 highlights

Table 31 Oracle Solaris failure scenarios (continued) Fault stimulus Failure effect Server path failure 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. Storage 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. OpenVMS and Tru64 UNIX Table 32 OpenVMS and Tru64 UNIX failure scenarios Fault stimulus Server failure (host power-cycled) Switch failure (SAN switch disabled) Failure effect All I/O operations halted. 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. 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. Controller failure Controller restart 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 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. 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-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. Storage 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. Linux Table 33 Linux failure scenarios Fault stimulus Server failure (host power-cycled) Switch failure (SAN switch disabled) 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. Failure scenarios 129

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
Table 31 Oracle Solaris failure scenarios
(continued)
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.
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 32 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 33 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)
Failure scenarios
129