From owner-freebsd-scsi Fri Aug 13 19:35:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 35C0714C57 for ; Fri, 13 Aug 1999 19:35:54 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-41.dialup.HiWAAY.net [216.180.14.41]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA04057; Fri, 13 Aug 1999 21:33:55 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA13520; Fri, 13 Aug 1999 21:33:53 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908140233.VAA13520@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger Cc: Randy Bush , FreeBSD SCSI From: David Kelly Subject: Re: dump to dlt gets write error In-reply-to: Message from Karl Denninger of "Fri, 13 Aug 1999 19:16:46 CDT." <19990813191646.A57450@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 21:33:53 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Denninger writes: > I've seen this kind of stupidity before and you're not going to like the > problem or solution. > > Put the DLT on a different SCSI bus (different host adapter) from the disks. > > Specifically, separate the fast/wide and narrow SCSI devices. > > I've seen both DLTs and other "non-wide" devices have kittens with disks > running fast/wide on the same SCSI bus. It usually manifests itself as > an I/O error on the narrow device - which is exactly what you're getting. > > My guess is that the hardware on the narrow (and not-so-fast) device gets > mightily confused by the shorter signal times (even though they're not > aimed at that target) and randomly "freaks out" enough to botch an > operation. I'd go a bit in the other direction and ask, "How is the transition between narrow and wide being handled?" Specifically people tend to purchase "narrow to wide" SCSI cables and simply plug things up with narrow devices at the tail end of the SCSI bus. Narrow terminator on the far end, wide terminator on the SCSI card. Nothing in the middle terminating the high bits of the wide bus. There are special terminators made just for that purpose. I'd like to think problems are caused by the device having problems. But we're talking about electrons here, and those little guys are sneaky. It may very well be a wide device is causing the narrow device to have problems. You are supposed to be safe if the internal narrow devices are connected to the 2940UW on the narrow connector, and the wide devices are connected the same, as long as you don't put a Tee in your SCSI bus by adding an external device. Just because the 2940UW has 3 connectors doesn't mean you can use all of them at once. Another good way to deal with everything internal is to route wide cable everywhere but use wide-to-narrow IDC-like adapters right at each device. About $15 each. Don't use the narrow connector on the 2940. The external wide connector is still usable this way. An old used narrow Adaptec 2940, or Symbios '810, or a new Adaptec 2930, might be a very good solution for the tape and CDROM. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message