Date: Tue, 25 Jul 2000 14:56:08 -0600 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: David Gilbert <dgilbert@velocet.ca> Cc: scsi@FreeBSD.org Subject: Re: Advansys SCSI controllers. Message-ID: <200007252055.OAA51488@pluto.plutotech.com> In-Reply-To: <14716.58769.839776.66400@trooper.velocet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <14716.58769.839776.66400@trooper.velocet.net> you wrote: ... > da0 at adw0 bus 0 target 0 lun 0 > da0: <SEAGATE ST318416W 0005> Fixed Direct Access SCSI-3 device > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enable d > da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da1 at adw0 bus 0 target 1 lun 0 > da1: <SEAGATE ST318416W 0005> Fixed Direct Access SCSI-3 device > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enable d > da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > > will under heavy usage spit out the message: > > Jul 22 19:00:27 mortar /kernel: (da0:adw0:0:0:0): Invalidating pack You need to talk to Seagate about updating the firmware on your drives. Just recently I reproduced this problem under 3.4, 4.0-stable, and -current using an adaptec controller on a Cheetah 18XL. After upgrading the firmware on the device, the problems disappeared. It seems that several Seagate U2/U160 devices have inherited a write cache problem that will cause the disk to simply fall off the bus with selection timeouts. With the drives I tested, the disk failed to respond to selection and after several retries by CAM, the system had no choice but to drop the device. Perhaps 3.4 is not as efficient as 4.X in terms of I/O delivery, but you can make it happen there too, if you are persistent. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007252055.OAA51488>