3Ware 9550SXU16MLB10 User Guide - Page 129

About Verifies of Redundant Units, How Errors Are Handled, About Migration

Page 129 highlights

About Background Tasks About Verifies of Redundant Units Verifies of redundant units also read each sector, working from lowest block to highest block. If verification cannot read data in a sector, dynamic sector repair is used to recover the lost data from the redundant drive or drives; this recovered data is written to the problem sector. This forces the drive to reallocate the defective sector with a good spare sector. How Errors Are Handled Verification makes use of the same error checking and error repair techniques used during ordinary use of drives configured through 3ware RAID controllers. When verification encounters an error, the controller typically retries the command. If there are cable CRC errors, there may be multiple retries including downgrade of the UDMA mode. If the error persists and is unrepairable (e.g., ECC errors), an error notification is issued to indicate the problem. (See "AEN 026h AEN_DRIVE_ECC_ERROR" on page 169.) If the disk drive is part of a redundant array that is in a redundant state (not DEGRADED or REBUILDING), then Dynamic Sector Repair automatically rewrites the redundant data to the error location to force the drive to reallocate the error location. A notification of repair is posted. The result is a restoration of drive and data integrity; the primary and redundant data are again both valid. If the array is not redundant, a file-system check is recommended to correct the issue. If the errors persist and cannot be overwritten from a backup copy, perform a final incremental backup. You will need to replace the defective drive, recreate the array, and reinstall the data. About Migration Migration allows on-line units to be reconfigured. You can make two types of configuration changes: „ RAID Level „ Unit Capacity Expansion RAID level migration and unit capacity expansion tasks can be done together or separately. Migration tasks follow the same schedule as rebuild and initialization tasks. Because of the controller and disk resources required during migration, when migration is active, it has priority over other background tasks. When migration starts, it will take the highest priority over rebuild, initialize and verify. www.3ware.com 123

  • 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

About Background Tasks
www.3ware.com
123
About Verifies of Redundant Units
Verifies of redundant units also read each sector, working from lowest block
to highest block. If verification cannot read data in a sector, dynamic sector
repair is used to recover the lost data from the redundant drive or drives; this
recovered data is written to the problem sector. This forces the drive to
reallocate the defective sector with a good spare sector.
How Errors Are Handled
Verification makes use of the same error checking and error repair techniques
used during ordinary use of drives configured through 3ware RAID
controllers.
When verification encounters an error, the controller typically retries the
command. If there are cable CRC errors, there may be multiple retries
including downgrade of the UDMA mode. If the error persists and is
unrepairable (e.g., ECC errors), an error notification is issued to indicate the
problem. (See “AEN 026h AEN_DRIVE_ECC_ERROR” on page 169.)
If the disk drive is part of a redundant array that is in a redundant state (not
DEGRADED or REBUILDING), then Dynamic Sector Repair automatically
rewrites the redundant data to the error location to force the drive to reallocate
the error location. A notification of repair is posted. The result is a restoration
of drive and data integrity; the primary and redundant data are again both
valid.
If the array is not redundant, a file-system check is recommended to correct
the issue. If the errors persist and cannot be overwritten from a backup copy,
perform a final incremental backup. You will need to replace the defective
drive, recreate the array, and reinstall the data.
About Migration
Migration allows on-line units to be reconfigured. You can make two types of
configuration changes:
RAID Level
Unit Capacity Expansion
RAID level migration and unit capacity expansion tasks can be done together
or separately.
Migration tasks follow the same schedule as rebuild and initialization tasks.
Because of the controller and disk resources required during migration, when
migration is active, it has priority over other background tasks. When
migration starts, it will take the highest priority over rebuild, initialize and
verify.