Date: Fri, 27 Feb 1998 07:53:35 +0100 From: Lars Koeller <Lars.Koeller@post.uni-bielefeld.de> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Conclusion: Seagate Python firmware and hanging SCBs on 2940! Message-ID: <199802270653.AA182242415@pollux.hrz.uni-bielefeld.de> In-Reply-To: grog's message of Fri, 27 Feb 1998 12:28:49 %2B1030. <19980227122849.39793@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---------- Hi! In reply to Greg Lehey who wrote: > On Tue, 24 February 1998 at 9:06:57 +0100, Lars Koeller wrote: > > > In reply to Greg Lehey who wrote: > > > >> On Tue, 24 February 1998 at 8:28:40 +0100, Lars Koeller wrote: > >> > >>> Just for your information! Don't use any combination of Seagate > >>> Python DAT > >>> drives, Adaptec 2940 SCSI controller and FreeBSD or Linux! > >> > >> This is somewhat overstating the case. I've been using exactly that > >> combination for 15 months, and I've been very satisfied. > > > > Hmmmm! Are you enable tagged comman queuing? > > Not explicitly. I haven't checked. I'm running pretty much the > latest -CURRENT. > > > What software? > > tar > > > Tar seems to be o.k. > > Yup. > > > dump most time can recover (better survive) 2 hanging SCB! But > > software which does continuous write lage blocks (30MB) and have a > > really high optimizing buffer queuing algorithm seems to mak > > problems, please test > > > > ftp://ftp.zn.ruhr-uni-bochum.de/pub/linux/afbackup-2.11.3.tar.gz > > Now that's an interesting viewpoint. I don't intend to change my > backup patterns, especially since it would promise to make things > worse, but it's a valid comment. On the other hand, it doesn't mean > you can say "Don't use any combination of Seagate Python DAT drives, > Adaptec 2940 SCSI controller and FreeBSD or Linux!" Yes, you are right, my 'conclusion' was a little bit to general, but it's really a pain, afbackup is really a very good backup solution for smaller networks, or home machines. On the other hand, it's a pain with hardware that works/fail application dependent! I can't really conclude, but it seems to be a firmware problem, which Seagate is not willing to fix. So the only solution is to buy a HP DAT and never choose again a Seagate one in my case. Or to disable tagged command queuing for all devices, which is unresonable. How do you think such problems should be handled in the future? Do we need a fix on the FreeBSD device driver layer, or should we try to make 'preassure' (think this isn't possible) on Seagate??? Lars -- E-Mail: | Lars Koeller Lars.Koeller@Uni-Bielefeld.DE | UNIX Sysadmin lkoeller@cc.FH-Lippe.DE | Computing Center PGP-key: | University of Bielefeld http://www.nic.surfnet.nl/pgp/pks-toplev.html | Germany ----------- FreeBSD, what else? ---- http://www.freebsd.org ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802270653.AA182242415>