HP P6000 HP P6300/P6500 Enterprise Virtual Array User Guide (593079-001, June - Page 149

OpenVMS, Linux, Failure effect, Fault stimulus

Page 149 highlights

OpenVMS Fault stimulus Server failure (host power-cycled) Switch failure (SAN switch disabled) Controller failure Controller restart Server path failure Storage path failure Linux Fault stimulus Server failure (host power-cycled) Switch failure (SAN switch disabled) Controller failure Controller restart 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. If the LUN is not shared, I/O is suspended or process is terminated across this HBA until path is restored. If running OpenVMS 7.3-1 and the LUN is shared, another cluster node having direct access will take over serving the device, resulting in no loss of service. In either case, 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. I/O is suspended or process is terminated across this HBA until path is restored. 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. 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. 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. Failure scenarios 149

  • 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
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

OpenVMS
Failure effect
Fault stimulus
Nonclustered-Processes fail.
Clustered—Other nodes running processes that used
devices served from the single-path HBA failed over access
Server failure (host power-cycled)
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
Switch failure (SAN switch disabled)
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.
Controller failure
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.
Controller restart
If the LUN is not shared, I/O is suspended or process is
terminated across this HBA until path is restored.
If running OpenVMS 7.3-1 and the LUN is shared, another
cluster node having direct access will take over serving the
device, resulting in no loss of service.
Server path failure
In either case, 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.
I/O is suspended or process is terminated across this HBA
until path is restored. 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.
Storage path failure
Linux
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
149