Date: Thu, 19 Aug 2021 13:07:26 -0600 From: Alan Somers <asomers@freebsd.org> To: FreeBSD-scsi <freebsd-scsi@freebsd.org> Subject: CAM_IO_STATS ignores some I/O errors Message-ID: <CAOtMX2jqSs89oxEiZyczzmegwL3icaTcLcriMuRg4D4OCz2Smg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--0000000000009f0b0605c9ee43ba Content-Type: text/plain; charset="UTF-8" I use the non-default CAM_IO_STATS kernel option to record how many errors each HDD experiences. But it seems like a lot of errors don't get recorded. For example, today I saw an error like this in dmesg, but the kern.cam.da.158.stats.errors still equals 0. In fact, I've noticed that MEDIUM ERROR never seems to be recorded. Is this intentional, or is there some error path that slipped through the cracks? (da158:mpr1:0:272:0): READ(10). CDB: 28 00 6a db 2d 7e 00 00 a5 00 (da158:mpr1:0:272:0): CAM status: SCSI Status Error (da158:mpr1:0:272:0): SCSI status: Check Condition (da158:mpr1:0:272:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (da158:mpr1:0:272:0): Info: 0x6adb2dd5 (da158:mpr1:0:272:0): Field Replaceable Unit: 134 (da158:mpr1:0:272:0): Command Specific Info: 0x81037000 (da158:mpr1:0:272:0): Actual Retry Count: 209 (da158:mpr1:0:272:0): Error 5, Unretryable error -Alan --0000000000009f0b0605c9ee43ba--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jqSs89oxEiZyczzmegwL3icaTcLcriMuRg4D4OCz2Smg>