Date: Fri, 3 Jan 1997 18:13:40 +0100 (MET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: peter@taronga.com (Peter da Silva) Cc: scsi@freebsd.org Subject: Re: Exabyte 8200 Message-ID: <199701031713.SAA00545@yedi.iaf.nl> In-Reply-To: <199701031321.HAA08056@bonkers.taronga.com> from "Peter da Silva" at Jan 3, 97 07:21:25 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter da Silva wrote... > 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 My 8200 works OK with 2.1.5R and has done so since 2.0R or so. (ncr1:4:0): "EXABYTE EXB-8200 2687" type 1 removable SCSI 1 As you can see it hangs of an NCR (a 810 to be precise). Exabytes (the older ones) in general are 'sensitive' beasts. Cleaning etc is critical. And you have to pick a 'good' firmware version from www.exabyte.com. The one I use was recommended to me by an Exabyte employee. And works OK for me. > 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. What barfs? > Is this a known problem? Is there anything I can do to force it to write 16k > blocks regardless of the write size? The native block size is 1kB but that's the only thing to keep in mind. And the 32kB physio() limitation of course. BTW I normally use 'dump', not 'tar'. But 'tar' does work also. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda --------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701031713.SAA00545>