ABORT message after hours of working
Justin T. Gibbs
gibbs at scsiguy.com
Thu Sep 6 06:26:51 PDT 2001
>Hi, I've seen the abort message problems from other people, but we have this p
>roblem:
>After a days work of database reading/writing postgres at reiserfs I get
>that famous ABORT message :(.
>
>I do not know who wants to queue that ABORT message, but the problem is,
>that the device get's kicked out of the raid configuration.
The problem here has to do with these guys:
>Attached devices:
>Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: SEAGATE Model: ST318404LW Rev: 0002
> Type: Direct-Access ANSI SCSI revision: 03
>Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: SEAGATE Model: ST318404LW Rev: 0002
> Type: Direct-Access ANSI SCSI revision: 03
>Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: SEAGATE Model: ST318404LW Rev: 0002
> Type: Direct-Access ANSI SCSI revision: 03
IIRC, Seagate fixed a cache bug in these drives with firmware rev 0005.
When the cache fills up in a certain way, the drive forgets about
transactions including newly queued ones. You should contact Seagate
about getting the latest firmware. In the mean time, you can disable
the write cache on the drives with old firmware (the one with firmware
rev 0006 should be okay) from the SCSI-Select menu.
BTW, although the driver reports a drop to 3.3MB/s, this is only during
a small window while it renegotiates with the device after a bus reset.
Once the negotiation is complete, the device is handled at the full
80MB/s rate.
--
Justin
To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
More information about the aic7xxx
mailing list