HP 418800-B21 HP StorageWorks Replication Solutions Manager 4.0.1 user guide ( - Page 55

Troubleshooting - Tru64 UNIX

Get HP 418800-B21 - StorageWorks Modular Smart Array 70 Storage Enclosure PDF manuals and user guides
UPC - 882780564640
View all HP 418800-B21 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 55 highlights

After the job completes successfully, Windows Explorer on the host does not show the disk (drive letter F). The disk does appear in the host Disk Management window, but Open and Explore operations on the disk fail. Explanation / resolution The dynamic remounting (mount without a reboot) step in the job causes the host OS to loose track of some drive information. To resolve this issue: 1. Ensure that no replication manager jobs involving the host are running or scheduled to run during the reboot. 2. On the enabled host, close applications, as appropriate. 3. Reboot the host. This clears the drive information issue. 4. Restart applications on the host, as appropriate. 5. Consider rewriting the job to eliminate the remount issue. Troubleshooting - Tru64 UNIX Job with AdvFS replication fails - Tru64 UNIX Problem Job that replicates Tru64 UNIX AdvFS host volumes fails on job commands like: CreateHostVolumeFromDiskDevices CreateHostVolumeGroup. Messages in the replication manager event log indicate that the host volume could not be found in the volume group. In the host directory /var/adm/messages, a message like the following can appear: Jun 5 18:50:44 rita vmunix: Found bad xor in sbm_total_free_space! Corrupted SBM metadata file! Jun 5 18:50:44 rita vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being rendered Jun 5 18:50:44 rita vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain. Explanation / resolution When a job is run, heavy I/O in any of the mounted filesets in the domain can lead to domain panic, causing the job to fail. Resolve any issues on the host, modify the job to use freezefs and thawfs utilities, and rerun the job. For the necessary steps in the job, see Suspending I/O before replicating AdvFS volumes - Tru64 UNIX. HP StorageWorks Replication Solutions Manager 4.0.1 55

  • 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
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
After the job completes successfully, Windows Explorer on the host does not show the disk (drive letter
F). The disk does appear in the host Disk Management window, but
Open
and
Explore
operations
on the disk fail.
Explanation / resolution
The dynamic remounting (mount without a reboot) step in the job causes the host OS to loose track of
some drive information.
To resolve this issue:
1.
Ensure that no replication manager jobs involving the host are running or scheduled to run
during the reboot.
2.
On the enabled host, close applications, as appropriate.
3.
Reboot the host. This clears the drive information issue.
4.
Restart applications on the host, as appropriate.
5.
Consider rewriting the job to eliminate the remount issue.
Troubleshooting - Tru64 UNIX
Job with AdvFS replication fails - Tru64 UNIX
Problem
Job that replicates Tru64 UNIX AdvFS host volumes fails on job commands like:
CreateHostVolumeFromDiskDevices
CreateHostVolumeGroup.
Messages in the replication manager event log indicate that the host volume could not be found in
the volume group.
In the host directory
/var/adm/messages
, a message like the following can appear:
Jun 5 18:50:44 rita vmunix:
Found bad xor in sbm_total_free_space!
Corrupted SBM metadata file!
Jun 5 18:50:44 rita vmunix:
An AdvFS domain panic has occurred due to
either a metadata write error or an internal inconsistency.
This domain is
being rendered Jun 5 18:50:44 rita vmunix:
Please refer to guidelines in
AdvFS Guide to File System Administration regarding what steps to take to
recover this domain.
Explanation / resolution
When a job is run, heavy I/O in any of the mounted
fi
lesets in the domain can lead to domain panic,
causing the job to fail.
Resolve any issues on the host, modify the job to use
freezefs
and
thawfs
utilities, and rerun the job. For
the necessary steps in the job, see
Suspending I/O before replicating AdvFS volumes - Tru64 UNIX
.
HP StorageWorks Replication Solutions Manager 4.0.1
55