I don't know if this helps, but this is the message tar spits out when
this problem occurs:
/bin/tar: home/pedro/COL&AMk-TA: Read error at byte 21958656, reading
10240 byte: Input/output error
Cress, Andrew R wrote:
> You really need to know what the additional sense data shows.
> With DAT tapes often they have variable length block sizes and get errors
> from some UNIX commands as a result. Or, it may be something that could be
> fixed with a firmware update to the DAT drive, or a driver fix. It depends
> on the details. Is sd08:11 the DAT drive?
Hmmm... I have no idea! I know that "host 0 channel 0 id 1 lun 0"
refers to the new Atlas HD, and I know that I have another HD with id 0,
and that the tape drive is id 3. I do not know how to interpret
Maybe 'sd08' refers to the block device number?
[root@office sysadm]# cat /proc/devices
So, one of the three SCSI devices uses block 8... but which? I don't know.
> Make sure
> CONFIG_SCSI_DEBUG=m (or =y)
> in your kernel, and issue
> echo "scsi log error 3" > /proc/scsi/scsi
> and rerun the tape backup to get more info.
Okay, good idea. I will recompile setting those symbols, but I will not
be able to do so until after the machine is idle (>5PM tonight). BTW,
these are my current SCSI symbol defs:
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_SCSI_LOGGING is not set
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:23 EST