From owner-freebsd-scsi Mon Jan 6 12:29:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA25841 for freebsd-scsi-outgoing; Mon, 6 Jan 1997 12:29:24 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA25836 for ; Mon, 6 Jan 1997 12:29:19 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA10452 (5.67b/IDA-1.5 for ); Mon, 6 Jan 1997 21:29:05 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id VAA03470; Mon, 6 Jan 1997 21:29:07 +0100 (CET) Message-Id: Date: Mon, 6 Jan 1997 21:29:06 +0100 From: se@freebsd.org (Stefan Esser) To: kelly@fsl.noaa.gov (Kelly) Cc: scsi@freebsd.org Subject: Re: Problem appears from migration from bt0 to ncr0 References: <32D125EB.4E3F@fsl.noaa.gov> <32D15EA6.47A0@fsl.noaa.gov> X-Mailer: Mutt 0.55-PL15 Mime-Version: 1.0 In-Reply-To: <32D15EA6.47A0@fsl.noaa.gov>; from Kelly on Jan 6, 1997 13:20:54 -0700 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jan 6, kelly@fsl.noaa.gov (Kelly) wrote: > > > I've recently migrated a host using a Buslogic 946C to an NCR 53C810. > > Which FreeBSD version is that ? > > Please test with a 2.2-BETA, if possible ... > > It's 2.1.5R. I'll try it out with 2.2B as soon as possible. By the > way, do you know if it's safe to update just the ncr driver code? No, there are too many changes to other parts of thje kernel. But 2.2R should be as reliable as 2.1.5 ... > > Well, the DFRS is known to go asleep for more than a minute :( > > Blah! Didn't you observe this ? The drive is identical to the twice as expencive DFHS, except for the scheduled power down after some 10s of hours. No problem for a workstation, but unacceptable for a server that is kept powered on for days (or months). > Sounds good. And I know where that is, too. :-) Fine! Please report, whether it helps ... > > What kind of tape device is that ? > > Wangtek 6130-HS DDS-1. Hmmm, that's a first generation DDS-1 DAT, right ? > FYI: the DAT drive always appeared as async with the buslogic controller > (and the QIC drive in that system was sync). With the ncr, the DAT > drive is now sync and the QIC is async! Curious. Then just try async transfers for both of them ... If they are targets 3 and 4, then the following single command will do: # ncrcontrol -t 3 -t 4 -s sync=0 Regards, STefan