From owner-freebsd-scsi  Fri Jan  3 05:28:24 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id FAA20624
          for freebsd-scsi-outgoing; Fri, 3 Jan 1997 05:28:24 -0800 (PST)
Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA20619
          for <scsi@freebsd.org>; Fri, 3 Jan 1997 05:28:22 -0800 (PST)
Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp
	(Smail3.1.29.1 #1) id m0vg9fW-0021WTC; Fri, 3 Jan 97 08:28 EST
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA08056 for scsi@freebsd.org; Fri, 3 Jan 1997 07:21:25 -0600
Date: Fri, 3 Jan 1997 07:21:25 -0600
From: peter@taronga.com (Peter da Silva)
Message-Id: <199701031321.HAA08056@bonkers.taronga.com>
To: scsi@freebsd.org
Subject: Exabyte 8200
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

FreeBSD doesn't like Exabyte 8200s at all. I've tried with a 1540B, a 1742,
and a 2940. And no matter what controller I use it's really flakey and
unreliable. I've tried two different 8200s that I have lying around (mostly
because nothing else really likes them either), and I sorts get OK results
with tar -b 32 (16k blocks)... but any other block size and it barfs.

Is this a known problem? Is there anything I can do to force it to write 16k
blocks regardless of the write size?