C
ONSTELLATION
ES.3 SAS P
RODUCT
M
ANUAL
, R
EV
. C
42
* For read retry count, every tick ~ 5% of total error recovery. Valid range setting is 1-20.
e.g. 1 ~ 5%
5 ~ 25%
20 ~ 100%
Setting these retry counts to a value below the default setting could result in degradation of the unrecovered error rate. For example,
suppose the read/write recovery page has the RC bit = 0 and if the read retry count is set to 5, this means ~ 25% of error recovery will be
executed which consumes 621.62 ms (please refer to the table above). If the limit is reached and a LBA has not yet been recovered (i.e.
requires retries beyond 621.62 ms), the command will end with Check Condition status report and unrecoverable read error will be
reported.
9.3
SAS
SYSTEM ERRORS
Information on the reporting of operational errors or faults across the interface is given in the
SAS Interface Manual
. The SSP Response
returns information to the host about numerous kinds of errors or faults. The Receive Diagnostic Results reports the results of diagnostic
operations performed by the drive.
Status returned by the drive to the initiator is described in the
SAS Interface Manual.
Status reporting plays a role in systems error
management and its use in that respect is described in sections where the various commands are discussed.
9.4
B
ACKGROUND
M
EDIA
S
CAN
Background Media Scan (BMS) is a self-initiated media scan. BMS is defined in the T10 document SPC-4 available from the T10
committee. BMS performs sequential reads across the entire pack of the media while the drive is idle. In RAID arrays, BMS allows hot
spare drives to be scanned for defects prior to being put into service by the host system. On regular duty drives, if the host system makes
use of the BMS Log Page, it can avoid placing data in suspect locations on the media. Unreadable and recovered error sites will be logged
or reallocated per ARRE/AWRE settings.
With BMS, the host system can consume less power and system overhead by only checking BMS status and results rather than tying up
the bus and consuming power in the process of host-initiated media scanning activity.
Since the background scan functions are only done during idle periods, BMS causes a negligible impact to system performance. The first
BMS scan for a newly manufactured drive is performed as quickly as possible to verify the media and protect data by setting the “Start
time after idle” to 5ms, all subsequent scans begin after 500ms of idle time. Other features that normally use idle time to function will
function normally because BMS functions for bursts of 800ms and then suspends activity for 100ms to allow other background functions
to operate.
BMS interrupts immediately to service host commands from the interface bus while performing reads. BMS will complete any BMS-
initiated error recovery prior to returning to service host-initiated commands. Overhead associated with a return to host-servicing activity
from BMS only impacts the first command that interrupted BMS, this results in a typical delay of about 1 ms.
Table 6
Read and write retry count maximum recovery times
Read retry count*
Maximum recovery time per
LBA (cumulative, ms)
Write retry count
Maximum recovery time per
LBA (cumulative, ms)
0
35.94
1
124.32
1
53.91
5
621.62
2
79.89
10
1243.23
3
97.86
15
1864.85
4
175.85
20 (default)
2486.47
5 (default)
421.79
