Karl-Heinz Herrmann <[EMAIL PROTECTED]> wrote:
> Can relocating blocks cause short scsi blocks?
No. However, depending on the setting of the PER bit in the error
recovery mode page, uncorrectable read error and/or write errors
can cause CHECK CONDITION, MEDIUM ERROR. But I would assume to
have all the data transferred (write) and all data transferred (read)
if data could be reallocated (and, in the case of read, if
data could be corrected). If not, you don't get a RECOVERED ERROR
sense, and you might get less data than expected. In that case
Linux usually reports underrun errors (with good low-level drivers,
such as ncr53c8xx), or reports an error, or just hangs.
> By the way: The Samsung drive is configured for 16 retries on read/write
16 retries ? That could last an awful lot of times. I have not used
a Samsung drive (well, mine was maybe not like yours, at least it had
fw level 113), but with many drives, recovery action include recalibration,
seeks, and 16 retries could well take enough to either make Linux
timeout (and maybe reset while the CDR is disconnected which could
make it destroy the CD it's writing), or *maybe* if the samsung drive
doesn't disconnect for some reason when doing recovery, starve the
other device.
> errors. If I set it to 1 and run badblocks it's dead after 1 minute and wont be
> recognised on the scsi bus on reboot. A powercycle clears it again.
Are you sure your power levels are enough ? I mean, I run usually my
drives 1 retry (and none for verify mode page), and they do not
die that easily.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
