[4947] in linux-scsi channel archive
Re: scsi tape problems in 2.1.123 (solved)
daemon@ATHENA.MIT.EDU (Finn Arne Gangstad)
Mon Oct 19 10:40:30 1998
Date: Mon, 19 Oct 1998 14:55:20 +0200 (MEST)
From: Finn Arne Gangstad <finnag@guardian.no>
To: Kai.Makisara@metla.fi
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.OSF.4.03.9810190958090.6492-100000@abies.metla.fi>
On Mon, 19 Oct 1998, Kai M{kisara wrote:
> On Fri, 16 Oct 1998, Finn Arne Gangstad wrote:
>
> >
> > dump fails to backup to scsi tape on a machine here in 2.1.123, it
> > complains about end of tape at once. The following message is logged by
> > the kernel:
> >
> > st0: Error 27070000 (sugg. bt 0x20, driver bt 0x27, host bt 0x7).
> >
> This can be interpreted by using linux/scsi/scsi.h. The suggestion byte
> 0x20 is SUGGEST_ABORT, the driver code 0x07 (suggestion and driver code
> are packed into one byte), and the host byte 0x07 is DID_ERROR. This means
> that the Buslogic driver encountered an internal error. Further
> interpretation can be found by looking at linux/drivers/scsi/Buslogic.c.
> There are many conditions that return DID_ERROR. Some of those are related
> to SCSI bus error conditions but there are also errors related to the host
> adapter software and the driver.
>
> The standard suggestion is: check your cables, termination, and SCSI
> address assignments.
I found the problem: Somehow, blocksize 63 no longer works, the maximum
blocksize with 2.1.123 seems to be 32kb. This was also verified with
mt setblk 32768 (which is the largest number it will accept).
Is this low blocksize a driver problem? Or can it be configured to be
larger somehow?
- Finn Arne
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
