diff options
author | mjacob <mjacob@FreeBSD.org> | 2001-02-11 23:46:54 +0000 |
---|---|---|
committer | mjacob <mjacob@FreeBSD.org> | 2001-02-11 23:46:54 +0000 |
commit | 3acecaf2d523e3763f225a429b3007ff059b4253 (patch) | |
tree | 0b2d7741ce40aa1807f5d7c11cbcca9c68717325 /sys/posix4 | |
parent | 3de2e69a0dc1cf1cb405a6267a7fefed942b7d1f (diff) | |
download | FreeBSD-src-3acecaf2d523e3763f225a429b3007ff059b4253.zip FreeBSD-src-3acecaf2d523e3763f225a429b3007ff059b4253.tar.gz |
1. The key SSD_KEY_RECOVERED_ERROR is not an error at all and should
not be retried. It is an indication that there was an error that was
corrected during the execution of the command. This is per ANSI SCSI2
spec.
It's possible that these should also be noted to the console (as indicative,
perhaps, of growing media defect lists in drives), but the default of
printing errors out if bootverbose in this case is probably enough.
Also, there'd been a missing ERESTART for that clause anyway.
2. If you have an ABORTED COMMAND, it's almost invariably a SCSI parity
error. You should never be silent about these since users should do something
about this if it occurs (moving that power cord *away* from the SCSI cable is
always a good first start). This should print irrespective of bootverbose
because it's an actual real error even if we retry a transmission.
Reviewed by: audit@freebsd.org, gibbs@freebsd.org
Diffstat (limited to 'sys/posix4')
0 files changed, 0 insertions, 0 deletions