HP StorageWorks MSA2012i HP StorageWorks 2000 Modular Smart Array Reference Gu - Page 293

oldest snapshot., You can expand the snap pool or

Page 293 highlights

TABLE E-1 Event Descriptions and Recommended Actions (Continued) Event Code 225 226 227 228 229 230 231 232 Event Type Critical Critical Critical Critical Warning Warning Critical Warning Description Recommended Action Background master write copy-onwrite operation has failed. There was an internal I/O error. Could not complete the write operation to the disk. A probable hardware failure has prevented the software from operating successfully. Isolate and replace and failed hardware components. Once the hardware issues have been corrected, it might be necessary to delete all snapshots and restart the controller. A background master volume rollback failed to start due to inability to initialize the snap pool. All rollback is in a suspended state. Make sure the snap pool and the vdisk on which this volume exists are online. Restart the rollback operation. Failure to execute rollback for a particular portion of the master volume. Restart the rollback operation. Background rollback for a master volume failed to end due to inability to initialize the snap pool. All rollback is in a suspended state. Make sure the snap pool and the vdisk on which this volume exists are online. Restart the rollback operation. The snap pool has reached the snap The user can set up the policy for pool warning threshold. the snap pool. The snap pool has reached the snap pool error threshold. The system will take the action set up in the policy. Default is to delete the oldest snapshot. You can expand the snap pool or delete snapshots. The snap pool has reached the snap pool critical threshold. The system will take the action set up in the policy. Default is to delete all snapshots on the snap pool. If the policy is to halt writes, then you must free up space on the snap pool master, or convert the master volume to a standard volume in order to resume operations. The maximum number of enclosures allowed for the current configuration has been exceeded. The platform does not support the number of enclosures that are configured. The firmware has removed the enclosure indicated by this event from its configuration. Appendix E Event Codes 293

  • 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
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Appendix E
Event Codes
293
225
Critical
Background master write copy-on-
write operation has failed.
There was an internal I/O error.
Could not complete the write
operation to the disk.
A probable hardware failure has
prevented the software from
operating successfully. Isolate and
replace and failed hardware
components. Once the hardware
issues have been corrected, it might
be necessary to delete all snapshots
and restart the controller.
226
Critical
A background master volume
rollback failed to start due to inability
to initialize the snap pool. All
rollback is in a suspended state.
Make sure the snap pool and the
vdisk on which this volume exists
are online. Restart the rollback
operation.
227
Critical
Failure to execute rollback for a
particular portion of the master
volume.
Restart the rollback operation.
228
Critical
Background rollback for a master
volume failed to end due to inability
to initialize the snap pool. All
rollback is in a suspended state.
Make sure the snap pool and the
vdisk on which this volume exists
are online. Restart the rollback
operation.
229
Warning
The snap pool has reached the snap
pool warning threshold.
The user can set up the policy for
the snap pool.
230
Warning
The snap pool has reached the snap
pool error threshold.
The system will take the action set up
in the policy. Default is to delete the
oldest snapshot.
You can expand the snap pool or
delete snapshots.
231
Critical
The snap pool has reached the snap
pool critical threshold.
The system will take the action set up
in the policy. Default is to delete all
snapshots on the snap pool.
If the policy is to halt writes, then
you must free up space on the snap
pool master, or convert the master
volume to a standard volume in
order to resume operations.
232
Warning
The maximum number of enclosures
allowed for the current configuration
has been exceeded.
The platform does not support the
number of enclosures that are
configured. The firmware has
removed the enclosure indicated by
this event from its configuration.
TABLE E-1
Event Descriptions and Recommended Actions
(Continued)
Event
Code
Event Type
Description
Recommended Action