[6994] in linux-scsi channel archive
Re: Is my cable bad?
daemon@ATHENA.MIT.EDU (Marc SCHAEFER)
Sat Aug 14 11:50:49 1999
To: linux-scsi@vger.rutgers.edu
From: Marc SCHAEFER <schaefer@alphanet.ch>
Date: 10 Aug 1999 17:15:51 +0200
Karl-Heinz Herrmann <k.-h.herrmann@fz-juelich.de> wrote:
> I don't see any timeout in the log. Will I get the Recovered Error reported in
> the usual log messages? Does this depend on the low-level driver (aic7xxx)?
Yes, especially if you asked for ``verbose error messages'' in SCSI
kernel compilation.
> Thats more like what I wanted to know. *Are* threre drives which won't
> disconnect during recovery? They should disconnect, shouldn't they?
To my knowledge, some old Samsung didn't.
They all should, really, as long as host permitted (which is the case).
> hits the first bad blocks with 1 retry. What will a drive do when it want's to
> relocate a bad block but hasn't a spare one?
Report a MEDIUM ERROR. Or hang (the latter was reported for old Seagate
drives, I think :()
> I know the drive is "bad" -- But is it the drives fault when scsi bus is busy
> for a while or can it be something in the scsi drivers?
No, what you see is very bad SCSI behaviour, which couldn't be justified
by even very bad SCSI host implementation.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
