[lkml]   [2001]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectSCSI Tape Device FATAL error on 2.4.10

On a ServerWorks HE Chipset system with an Exabyte EXB-480
Robotics Tape library we are seeing a fatal SCSI IO problem
that results in a SCSI bus hang on the system. This error
is very fatal, and requires that the machine be rebooted
to recover. Following this error, the Linux
Operating System is still running OK, but the affected
SCSI bus does not respond to any commands nor do any
devices attached to this bus.

The Tape Drive is an Exabyte SCSI Tape. The error occurs when
the device reaches end of tape (EOT) during a write operation
while writing to the tape.

With tape programming, there really is no good way to know where
the end of tape is while archiving data real time, so this error
is pretty much fatal. We are using tape partitioning, which we
have noticed not many applications in Linux use at present, so
these code paths may be related to the problem. I have reviewed
st.c but it is not readily apparent where the problem may be
in this code, which is leading me to suspect it's related to
some interaction between st.c and the drivers with regard to
multiple seeks and writes between tape partitions.

Configuration is:

EXSCH (Exabyte Robotics Library for Linux 2.2.X/2.4.X) We wrote this.

The EXB-480 has 4 Exabyte tape drives and 30 150GB Tape slots with
an import/export port.

THe system we are using is the SuperMicro Serverworks HE Motherboard with
2GB of memory and 3Ware IDE Controllers. We are not using the 3Ware
controllers for any of the tape support.

Please advise,

Jeff Merkey

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:11    [W:0.069 / U:0.988 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site