From owner-freebsd-scsi Sun Oct 25 10:25:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02990 for freebsd-scsi-outgoing; Sun, 25 Oct 1998 10:25:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02984 for ; Sun, 25 Oct 1998 10:25:45 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id MAA04658 for scsi@freebsd.org; Sun, 25 Oct 1998 12:25:11 -0600 (CST) From: Joe Greco Message-Id: <199810251825.MAA04658@aurora.sol.net> Subject: Do we support > 32 drives yet? To: scsi@FreeBSD.ORG Date: Sun, 25 Oct 1998 12:25:10 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Installed a 3.0-BETA shortly before -RELEASE. This machine has a lot of disks :-) % camcontrol devlist -v scbus-1 on xpt0 bus 0: <= Huh? What's this? scbus0 on ahc0 bus 0: scbus1 on ncr0 bus 0: at scbus1 target 0 lun 0 (da0) at scbus1 target 1 lun 0 (da1) at scbus1 target 2 lun 0 (da2) at scbus1 target 3 lun 0 (da3) at scbus1 target 4 lun 0 (da4) at scbus1 target 5 lun 0 (da5) at scbus1 target 6 lun 0 (da6) scbus2 on ncr1 bus 0: at scbus2 target 0 lun 0 (da7) at scbus2 target 1 lun 0 (da8) at scbus2 target 2 lun 0 (da9) at scbus2 target 3 lun 0 (da10) at scbus2 target 4 lun 0 (da11) at scbus2 target 5 lun 0 (da12) at scbus2 target 6 lun 0 (da13) scbus3 on ahc1 bus 0: at scbus3 target 0 lun 0 (da14) at scbus3 target 1 lun 0 (da15) at scbus3 target 2 lun 0 (da16) at scbus3 target 3 lun 0 (da17) at scbus3 target 4 lun 0 (da18) at scbus3 target 5 lun 0 (da19) at scbus3 target 6 lun 0 (da20) scbus4 on ahc2 bus 0: at scbus4 target 0 lun 0 (da21) at scbus4 target 1 lun 0 (da22) at scbus4 target 2 lun 0 (da23) at scbus4 target 3 lun 0 (da24) at scbus4 target 4 lun 0 (da25) at scbus4 target 5 lun 0 (da26) at scbus4 target 6 lun 0 (da27) ahc0 is the built-in 7890 on the motherboard; I purchased an ASUS P2B-DS on the theory that I didn't want to place any artificial future limits on what I did, since I knew CAM would support it. I'm seriously looking at adding some nice (newer) Seagate Cheetah W drives to this machine, but the question is, how many can I actually do? We used to have a limit of 32 drives, and as you can see, I'm pushing to near that limit with 28. The code in MAKEDEV looks to me like we might still have that limit. I'd like to know for sure before I commit to a pointless expense. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 25 15:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29727 for freebsd-scsi-outgoing; Sun, 25 Oct 1998 15:51:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29720 for ; Sun, 25 Oct 1998 15:51:06 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA08774; Sun, 25 Oct 1998 16:49:09 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810252349.QAA08774@panzer.plutotech.com> Subject: Re: Do we support > 32 drives yet? In-Reply-To: <199810251825.MAA04658@aurora.sol.net> from Joe Greco at "Oct 25, 98 12:25:10 pm" To: jgreco@solaria.sol.net (Joe Greco) Date: Sun, 25 Oct 1998 16:49:09 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe Greco wrote... > Installed a 3.0-BETA shortly before -RELEASE. > > This machine has a lot of disks :-) > > % camcontrol devlist -v > scbus-1 on xpt0 bus 0: <= Huh? What's this? That's the transport layer "bus". Don't worry about it. :) > scbus0 on ahc0 bus 0: > scbus1 on ncr0 bus 0: > at scbus1 target 0 lun 0 (da0) > at scbus1 target 1 lun 0 (da1) > at scbus1 target 2 lun 0 (da2) > at scbus1 target 3 lun 0 (da3) > at scbus1 target 4 lun 0 (da4) > at scbus1 target 5 lun 0 (da5) > at scbus1 target 6 lun 0 (da6) [ ...bunch more disks.. ] > ahc0 is the built-in 7890 on the motherboard; I purchased an ASUS > P2B-DS on the theory that I didn't want to place any artificial future > limits on what I did, since I knew CAM would support it. It's a good board. I see you don't have the passthrough driver configured. You may want to do that, since you can't use camcontrol (or any other SCSI passthrough utilities) without it. > I'm seriously looking at adding some nice (newer) Seagate Cheetah W > drives to this machine, but the question is, how many can I actually > do? > > We used to have a limit of 32 drives, and as you can see, I'm pushing > to near that limit with 28. The code in MAKEDEV looks to me like we > might still have that limit. I'd like to know for sure before I > commit to a pointless expense. >From looking at src/sys/sys/disklabel.h, it looks like we support 2^9 disks. (512): ======================================================================== /* 3 2 1 0 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 _________________________________________________________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ----------------------------------------------------------------- | TYPE |UNIT_2 | SLICE | MAJOR? | UNIT |PART | ----------------------------------------------------------------- */ #define dkmakeminor(unit, slice, part) \ (((slice) << 16) | (((unit) & 0x1e0) << 16) | \ (((unit) & 0x1f) << 3) | (part)) #define dkmodpart(dev, part) (((dev) & ~(dev_t)7) | (part)) #define dkmodslice(dev, slice) (((dev) & ~(dev_t)0x1f0000) | ((slice) << 16)) #define dkpart(dev) (minor(dev) & 7) #define dkslice(dev) ((minor(dev) >> 16) & 0x1f) #define dktype(dev) ((minor(dev) >> 25) & 0x7f) #define dkunit(dev) ((((dev) >> 16) & 0x1e0) | (((dev) >> 3) & 0x1f)) ======================================================================== The da driver uses dkunit() to figure out the unit number. It looks like that means it supports 2^9 disk devices. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 25 17:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06578 for freebsd-scsi-outgoing; Sun, 25 Oct 1998 17:02:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06543; Sun, 25 Oct 1998 17:02:02 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA15355; Mon, 26 Oct 1998 11:30:57 +1030 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981023174049.A3035@marso.com> Date: Mon, 26 Oct 1998 11:30:57 +1030 (CST) From: "Daniel O'Connor" To: "Larry S. Marso" Subject: RE: solved: writing multisession cd9660 Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Oct-98 Larry S. Marso wrote: > I've found it's important to **save** the cdimage.raw file (which is > downright inconvenient ... please share with me any alternatives you > uncover), You can read a raw ISO image back off a CD.. I did this to copy my FreeBSD CD's.. dd if=/dev/wcd0c of=/tmp/freebsd-1.iso bs=64k cdrecord -speed=4 -v -fs=6m -dev=0,6,0 /tmp/freebsd-1.iso (You could probably glue them together, but I wasn't feeling game at the time :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 25 21:35:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01637 for freebsd-scsi-outgoing; Sun, 25 Oct 1998 21:35:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cs.tku.edu.tw (power.cs.tku.edu.tw [163.13.128.241]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA01628 for ; Sun, 25 Oct 1998 21:35:36 -0800 (PST) (envelope-from winsdom@gmail.gcn.net.tw) Received: from adagio by cs.tku.edu.tw (SMI-8.6/SMI-SVR4) id NAA12183; Mon, 26 Oct 1998 13:27:43 +0800 Message-Id: <199810260527.NAA12183@cs.tku.edu.tw> From: "Winsdom Chen" To: scsi@FreeBSD.ORG Date: Mon, 26 Oct 1998 13:34:21 +0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Buslogic BT-930 support... In-reply-to: <199810241647.KAA00129@narnia.plutotech.com> References: <19981023161532.AAA4224@sc-mail2.corpwest.BayNetworks.com@gmorgan-pc.corpwest.baynetworks.com> <199810241422.WAA04808@cs.tku.edu.tw> X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article <199810241422.WAA04808@cs.tku.edu.tw> you wrote: [del] > > Well,Linux has suppored BT-930 since kernel 2.0.29(perhaps). > > Could core team port that from Linux? > > The main thing holding this back right now is that I haven't received > hardware from Mylex yet. I'm using BT-930.Should I mail to Mylex ask them support FreeBSD? I think it might work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 01:32:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22007 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 01:32:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21992; Mon, 26 Oct 1998 01:32:04 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id KAA23645; Mon, 26 Oct 1998 10:31:20 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id E94E51508; Mon, 26 Oct 1998 09:35:11 +0100 (CET) Date: Mon, 26 Oct 1998 09:35:11 +0100 From: Ollivier Robert To: freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching Message-ID: <19981026093511.A14275@keltia.freenix.fr> Mail-Followup-To: freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG References: <199810230013.RAA19305@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <199810230013.RAA19305@salsa.gv.tsc.tdk.com>; from Don Lewis on Thu, Oct 22, 1998 at 05:13:09PM -0700 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4731 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Don Lewis: > That's certainly not my experience. Once the initiate_write_filepage > and newdirrem panics were fixed, my system has been completely stable. I agree. All my three systems are more stable now and the two using the ahc driver are faster under CAM. I've not see that much difference for the ncr driver. > I think you are thinking of NFS write caching. An NFS server isn't > supposed to tell the NFS client that the write has completed until No, I really talking about the WCE bit. SAM is very clear about this kernel value for HP-UX. There are two configurable variables, one is "async" mode (apparently you either have it for all I/O or not at all) and write caching (WCE). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 09:10:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29754 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 09:10:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA29747 for ; Mon, 26 Oct 1998 09:10:19 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 23852 invoked from network); 26 Oct 1998 17:09:37 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 26 Oct 1998 17:09:37 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id LAA29710; Mon, 26 Oct 1998 11:09:35 -0600 Date: Mon, 26 Oct 1998 11:09:35 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199810261709.LAA29710@bonkers.taronga.com> To: scsi@FreeBSD.ORG Subject: Re: Do we support > 32 drives yet? Newsgroups: taronga.freebsd.scsi In-Reply-To: <199810252349.QAA08774@panzer.plutotech.com> References: <199810251825.MAA04658@aurora.sol.net> Organization: none Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >/* > 3 2 1 0 > 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 > _________________________________________________________________ > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > ----------------------------------------------------------------- > | TYPE |UNIT_2 | SLICE | MAJOR? | UNIT |PART | > ----------------------------------------------------------------- >*/ Other than hardcoding device numbers in the config file, is there any way of tying a device to a particular bus/target/lun combination the way you can in Digital UNIX and in System-V derived systems where this data is encoded into the minor number? This seems to be a requirement if you want to be able to hot-add drives. For example, I can plug a drive into a Storageworks shelf on my DU box, and calculate the minor number for it from the bus, target, and LUN (bus*K1+target*K2+lun)... on FreeBSD I'd have to prebuild a kernel or preallocate a bunch of unused minors. With an HSZ50 I can stick 12 shelves of drives on a single controller, for 84 drives per controller. We run these in JBOD mode because each project wants to be able to keep a couple of disks "on the shelf" if necessary, ready to slot in so they can get to work on a problem on a few minutes notice. Digital UNIX has a terrific SCSI subsystem, but it looks like FreeBSD is dogging its heels. This is one of the things keeping DU ahead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 10:10:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05395 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 10:10:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05388 for ; Mon, 26 Oct 1998 10:10:25 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA06334; Mon, 26 Oct 1998 19:09:34 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA32470 (5.67b/IDA-1.5); Mon, 26 Oct 1998 19:06:04 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id IAA08664; Mon, 26 Oct 1998 08:36:47 +0100 (CET) From: Wilko Bulte Message-Id: <199810260736.IAA08664@yedi.iaf.nl> Subject: Re: Buslogic BT-930 support... In-Reply-To: <199810260527.NAA12183@cs.tku.edu.tw> from Winsdom Chen at "Oct 26, 98 01:34:21 pm" To: winsdom@gmail.gcn.net.tw (Winsdom Chen) Date: Mon, 26 Oct 1998 08:36:47 +0100 (CET) Cc: scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Winsdom Chen wrote... > > In article <199810241422.WAA04808@cs.tku.edu.tw> you wrote: > [del] > > > Well,Linux has suppored BT-930 since kernel 2.0.29(perhaps). > > > Could core team port that from Linux? > > > > The main thing holding this back right now is that I haven't received > > hardware from Mylex yet. > > I'm using BT-930.Should I mail to Mylex ask them support FreeBSD? > I think it might work. Good luck... You are really gonna need it. I've tried for a long time to get programming docs out of Mylex but they don't even answer. Mylex support is OK, but they are not authorised to release this kind of docs. And NDAs all over the place BTW. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 11:40:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13065 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 11:40:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13060 for ; Mon, 26 Oct 1998 11:40:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00604; Mon, 26 Oct 1998 11:38:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810261938.LAA00604@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: peter@taronga.com (Peter da Silva) cc: scsi@FreeBSD.ORG Subject: Re: Do we support > 32 drives yet? In-reply-to: Your message of "Mon, 26 Oct 1998 11:09:35 CST." <199810261709.LAA29710@bonkers.taronga.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 11:38:55 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >/* > > 3 2 1 0 > > 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 > > _________________________________________________________________ > > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > ----------------------------------------------------------------- > > | TYPE |UNIT_2 | SLICE | MAJOR? | UNIT |PART | > > ----------------------------------------------------------------- > >*/ > > Other than hardcoding device numbers in the config file, is there any way of > tying a device to a particular bus/target/lun combination the way you can > in Digital UNIX and in System-V derived systems where this data is encoded > into the minor number? No. DEVFS would have let us do this (via multiple appearances of a single node), but that kinda got killed off. > Digital UNIX has a terrific SCSI subsystem, but it looks like FreeBSD is > dogging its heels. This is one of the things keeping DU ahead. DEVFS. DEVFS. DEVFS. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 12:11:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17024 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 12:11:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17019 for ; Mon, 26 Oct 1998 12:11:31 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id VAA28138; Mon, 26 Oct 1998 21:10:48 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA06298 (5.67b/IDA-1.5); Mon, 26 Oct 1998 20:57:18 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA13230; Mon, 26 Oct 1998 19:35:56 +0100 (CET) From: Wilko Bulte Message-Id: <199810261835.TAA13230@yedi.iaf.nl> Subject: Re: Do we support > 32 drives yet? In-Reply-To: <199810261709.LAA29710@bonkers.taronga.com> from Peter da Silva at "Oct 26, 98 11:09:35 am" To: peter@taronga.com (Peter da Silva) Date: Mon, 26 Oct 1998 19:35:56 +0100 (CET) Cc: scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Peter da Silva wrote... > > >/* > > 3 2 1 0 > > 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 > > _________________________________________________________________ > > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > ----------------------------------------------------------------- > > | TYPE |UNIT_2 | SLICE | MAJOR? | UNIT |PART | > > ----------------------------------------------------------------- > >*/ > > Other than hardcoding device numbers in the config file, is there any way of > tying a device to a particular bus/target/lun combination the way you can > in Digital UNIX and in System-V derived systems where this data is encoded > into the minor number? This seems to be a requirement if you want to be > able to hot-add drives. For example, I can plug a drive into a Storageworks > shelf on my DU box, and calculate the minor number for it from the bus, > target, and LUN (bus*K1+target*K2+lun)... on FreeBSD I'd have to prebuild > a kernel or preallocate a bunch of unused minors. > > With an HSZ50 I can stick 12 shelves of drives on a single controller, for > 84 drives per controller. We run these in JBOD mode because each project wants ??? The HSZ50 backend is not wide scsi. In a BA355 type enclosure you can have 24 disks, using BA35[06] device shelves you can have 6 (backend channels) * 7 (disks per shelf) is 42 disks. Using redundant power supplies in your BA35[06] you are limited to 6 * 6 = 36 disks. I don't see how you get to 84 disks. > to be able to keep a couple of disks "on the shelf" if necessary, ready to > slot in so they can get to work on a problem on a few minutes notice. Why not run ADVFS on a big RAIDset (14 disks max)? ADVFS also gives you a lot of flexibility. You can have a max of 32 LUNs presented at the HSZ50s frontend bus (4 SCSI IDs * 8 LUNs). So full JBOD will not work with the max 36 disk config. > Digital UNIX has a terrific SCSI subsystem, but it looks like FreeBSD is > dogging its heels. This is one of the things keeping DU ahead. If you want to run the Altavista's of this planet you better have a good I/O subsys ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 16:29:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14195 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 16:29:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from host.nstl.nnov.ru (host.nstl.nnov.ru [195.98.49.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14184 for ; Mon, 26 Oct 1998 16:29:03 -0800 (PST) (envelope-from alex@nstl.nnov.ru) Received: from nstl.nstl.nnov.ru (root@nstl.nstl.nnov.ru [195.98.49.71]) by host.nstl.nnov.ru (8.8.8/8.8.7) with ESMTP id DAA06604 for ; Tue, 27 Oct 1998 03:28:14 +0300 (MSK) (envelope-from alex@nstl.nnov.ru) Received: from nstl.nstl.nnov.ru (jonny.nstl.nnov.ru [10.0.10.5]) by nstl.nstl.nnov.ru (8.8.5/8.8.5) with SMTP id DAA07275 for ; Tue, 27 Oct 1998 03:28:01 +0300 (MSK/MSD) Date: Tue, 27 Oct 1998 03:27:42 +0300 From: Alexander Dubinin X-Mailer: The Bat! (v1.043) UNREG Reply-To: Alexander Dubinin Organization: NSTL Message-ID: <9144.981027@nstl.nnov.ru> To: freebsd-scsi@FreeBSD.ORG Subject: Problem with cdrecord in 3.0-RELEASE, and few other questions... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello All! Question 1: Some time ago I install 3.0-RELEASE to my computer with RICOH MP6200S, and NCR 53c810A SCSI adapter (Used for CD-recording). Then I use 2.2.6-STABLE - all works fine, I link /dev/scgx to /dev/rcd0.ctl, and all 'll Ok. Now, in 3.0, I can't find this entry. In hints to cdrecord written, that I can use /dev/cd0a directly, with CAM support. So, how can I do it? Can anybody help? Question 2: On other my computer (proxy server, with AHA 2940 and two Conner drives) periodically such messages appears: (da1:ahc0:0:1:0): tagged openings now 32 (da1:ahc0:0:1:0): tagged openings now 31 etc. That does this mean? Is it dangerous for my disks/controller, or not? Question 3: And, while rebooting or halting system: syncing disks... 4 4 done (da0:ahc0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 (da0:ahc0:0:0:0): Invalid command operation code field replaceable unit: 14 And there are no disk on bus 0, lun 0 and id 0 !!!! Why system try to synchronize it? Bye! Alexander Dubinin mailto: alex@nstl.nnov.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 16:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15567 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 16:42:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15547 for ; Mon, 26 Oct 1998 16:42:26 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 10872 invoked by uid 1000); 27 Oct 1998 01:45:44 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 26 Oct 1998 20:45:44 -0400 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-scsi@FreeBSD.ORG Subject: DPT Hangs at Boot (Especially with 2.2.7) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ To those who do not know; I am the orignal author and the maintainer of the DPT drivers for FreeBSD ] Recently I have been receiving a rather constant stream of complaints that sound more or less like: When running DPT PM3334 (mainly) on FreeBSD 2.2.7 (almost always) I run into the problem where the system simply hangs during boot, or during fsck, or when switching from single-user to multi-user. The system also tends to hang when the system installation creates new file-systems during fresh installation. When the system freezes, diagnostic LED 1 is either permanently ON, or slowly blinking. The motherboard I have is ASUS model ____ (almost always and has a 300MHz (or faster) Pentium-II. The motherboard uses the Intel BX chipset (almost without exception). The DPT runs firmware version 7M0. Another thing that happens to me is that the file-system creation crashes when using a very large ``disk'' (array) and creating huge (over 4GB) file-systems. If the above sounds familiar, read on. Analysis (which was partially funded by some good souls with horrible problems of this nature) shows the following: a. The huge file-system newfs crash is probably not directly DPT related; The DPT controller simply makes it easy to come up with a 20-100GB ``disk''. This is a known (to me, at least) problem in FreeBSD-2.x.y. It appears as something in the sysinstall code (I admit to have no clue what/where) assumes that file-system sizes (in bytes) are expressed as 32bit integers. This is obviously not good enough for file-systems larger than 4GB. The solution here is to simply avoid creating any file-system ,during fresh install!) larger than 1-2GB. The problem does not seem to inflict normal fdisk/disklabel/newfs. b. Replace firmware 7M0 with 7Li. You can find 7Li in my ftp server: ftp://simon-shapiro.org/crash/fw/476d07li.fwi. This will improve things. It appears as if 7M0 is a bit confusable with the data rate that FreeBSD can send its way. This is less critical with 3.0+CAM, but very noticeable with 2.2.7. c. Move the DPT card to another slot. Move the video card to another slot. If you have multiple DPTs, swap between them. This seems to cure or greatly improve things. It cam also make things go real bad. I have a test system (sent to me by a ``customer'') that I can routinely cause to hang during POST (way before FreeBSD is loaded in any was shape or form) by simply plugging the DPT to the slot closest to the CPU. d. Upgrade to 3.0. It seems 2.2.7 does something funny (or does not do something important?) during shutdown. This is evidenced by the difference in behavior between power-up and reboot. Pushing the reset button produces results that are somewhere between power-up and all-software reboot. Folks, I am sorry I can only give you work around solutions (and not perfect ones!) and cannot give you a correction. Be assured I am working with the factory people to isolate and narrow-down the problem. BTW, I am not a regular reader of -questions, so please drop me a line if you think I can help... Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 17:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17312 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 17:04:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17307 for ; Mon, 26 Oct 1998 17:04:00 -0800 (PST) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.7/8.8.5) id SAA18934; Mon, 26 Oct 1998 18:02:48 -0700 (MST) From: Kenneth Merry Message-Id: <199810270102.SAA18934@pluto.plutotech.com> Subject: Re: Problem with cdrecord in 3.0-RELEASE, and few other questions... In-Reply-To: <9144.981027@nstl.nnov.ru> from Alexander Dubinin at "Oct 27, 98 03:27:42 am" To: alex@nstl.nnov.ru Date: Mon, 26 Oct 1998 18:02:48 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alexander Dubinin wrote... > Hello All! > > Question 1: > > Some time ago I install 3.0-RELEASE to my computer with RICOH MP6200S, > and NCR 53c810A SCSI adapter (Used for CD-recording). > > Then I use 2.2.6-STABLE - all works fine, I link /dev/scgx to > /dev/rcd0.ctl, and all 'll Ok. > Now, in 3.0, I can't find this entry. In hints to cdrecord written, > that I can use /dev/cd0a directly, with CAM support. > So, how can I do it? > > Can anybody help? When you're running cdrecord under CAM, there are several things to keep in mind: - you must have the pass(4) device configured in your kernel. (i.e. "device pass0" in your config file) - you need one pass device node in /dev for each SCSI device in your system. If you've got 10 SCSI devices, you'd type: cd /dev sh MAKEDEV pass10 - You need the transport layer device as well: cd /dev sh MAKEDEV xpt1 The xpt(4) device is automatically enabled when you have SCSI configured in your kernel, so there is no need for a separate xpt device line in your kernel config file. [ Note: If you installed 3.0 from the standard distribution (i.e. not via cvsup and buildworld/installworld), you should already have the xpt device and several pass devices in /dev ] - specify your CD recorder by bus/target/lun. I don't think the code to specify devices by name works with CAM. To find out what bus/target/lun your CD recorder is on, type "camcontrol devlist". - There is no need for the /dev/scgx symlink under CAM. cdrecord doesn't use that at all. > Question 2: > On other my computer (proxy server, with AHA 2940 and two Conner > drives) periodically such messages appears: > > (da1:ahc0:0:1:0): tagged openings now 32 > (da1:ahc0:0:1:0): tagged openings now 31 > > etc. > That does this mean? Is it dangerous for my disks/controller, or not? It isn't dangerous at all, and is actually quite normal. It means that your disk has enough space to hold 31 transactions at a time. You can use the above numbers to compare the various disks you have, and see which ones support the most tagged transactions. > Question 3: > > And, while rebooting or halting system: > > syncing disks... 4 4 done > (da0:ahc0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 > (da0:ahc0:0:0:0): Invalid command operation code field replaceable unit: 14 > > And there are no disk on bus 0, lun 0 and id 0 !!!! > Why system try to synchronize it? That's a good question. Can you send me the output of 'camcontrol devlist -v' for that system? Are you *sure* you're running 3.0-RELEASE? There were some changes that went in a couple of days before the release to disable error messages when the cache sync operation returns illegal request. i.e., if you're running 3.0-RELEASE, you shouldn't see that error message at all. If you are running 3.0-RELEASE, and you still see that message, it means that there's a bug somewhere or other. In any case, that error message is quite harmless, and it's nothing to be concerned about. I would like to know why it's popping up, though. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 17:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20995 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 17:37:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20989 for ; Mon, 26 Oct 1998 17:37:52 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id RAA24938; Mon, 26 Oct 1998 17:35:08 -0800 (PST) Date: Mon, 26 Oct 1998 17:35:08 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Simon Shapiro cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT Hangs at Boot (Especially with 2.2.7) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This seems symptomatic of the problems I'm having doing warm boots with my adaptec's and 2.2.7. As reported, a 2.2.5 kernel works peachy, 2.2.7 hangs on a warm boot. However, I do not trust 3.0 enough yet to make it a production environment, so I will just limp along until it's ready. :) On Mon, 26 Oct 1998, Simon Shapiro wrote: > [ To those who do not know; I am the orignal author and the maintainer of > the DPT drivers for FreeBSD ] > > Recently I have been receiving a rather constant stream of complaints that > sound more or less like: > > When running DPT PM3334 (mainly) on FreeBSD 2.2.7 (almost always) I run > into the problem where the system simply hangs during boot, or during > fsck, or when switching from single-user to multi-user. The system also > tends to hang when the system installation creates new file-systems > during fresh installation. When the system freezes, diagnostic LED 1 > is either permanently ON, or slowly blinking. > > The motherboard I have is ASUS model ____ (almost always and has a > 300MHz (or faster) Pentium-II. The motherboard uses the Intel BX > chipset (almost without exception). The DPT runs firmware version 7M0. > > Another thing that happens to me is that the file-system creation > crashes when using a very large ``disk'' (array) and creating huge (over > 4GB) file-systems. > > If the above sounds familiar, read on. > > Analysis (which was partially funded by some good souls with horrible > problems of this nature) shows the following: > > a. The huge file-system newfs crash is probably not directly DPT related; > The DPT controller simply makes it easy to come up with a 20-100GB > ``disk''. This is a known (to me, at least) problem in FreeBSD-2.x.y. > It appears as something in the sysinstall code (I admit to have no clue > what/where) assumes that file-system sizes (in bytes) are expressed as > 32bit integers. This is obviously not good enough for file-systems > larger than 4GB. > > The solution here is to simply avoid creating any file-system ,during > fresh install!) larger than 1-2GB. The problem does not seem to > inflict normal fdisk/disklabel/newfs. > > b. Replace firmware 7M0 with 7Li. You can find 7Li in my ftp server: > ftp://simon-shapiro.org/crash/fw/476d07li.fwi. This will improve > things. It appears as if 7M0 is a bit confusable with the data rate > that FreeBSD can send its way. This is less critical with 3.0+CAM, but > very noticeable with 2.2.7. > > c. Move the DPT card to another slot. Move the video card to another > slot. If you have multiple DPTs, swap between them. This seems to > cure or greatly improve things. It cam also make things go real bad. I > have a test system (sent to me by a ``customer'') that I can routinely > cause to hang during POST (way before FreeBSD is loaded in any was shape > or form) by simply plugging the DPT to the slot closest to the CPU. > > d. Upgrade to 3.0. It seems 2.2.7 does something funny (or does not do > something important?) during shutdown. This is evidenced by the > difference in behavior between power-up and reboot. Pushing the reset > button produces results that are somewhere between power-up and > all-software reboot. > > Folks, I am sorry I can only give you work around solutions (and not > perfect ones!) and cannot give you a correction. Be assured I am working > with the factory people to isolate and narrow-down the problem. > > BTW, I am not a regular reader of -questions, so please drop me a line if > you think I can help... > > > Sincerely Yours, Shimon@Simon-Shapiro.ORG > 770.265.7340 > Simon Shapiro > > Unwritten code has no bugs and executes at twice the speed of mouth > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 26 22:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14357 for freebsd-scsi-outgoing; Mon, 26 Oct 1998 22:11:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pixel.zycor.lgc.com (pixel.zycor.lgc.com [134.132.112.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14352; Mon, 26 Oct 1998 22:11:24 -0800 (PST) (envelope-from rsnow@lgc.com) Received: from solo (rsnow-vpn.zycor.lgc.com [134.132.112.132]) by pixel.zycor.lgc.com (8.8.8/8.8.8) with SMTP id AAA01546; Tue, 27 Oct 1998 00:10:42 -0600 (CST) (envelope-from rsnow@lgc.com) Message-ID: <000d01be0170$6d5b0880$05e48486@lgc.com> From: "Rob Snow" To: Cc: Subject: CAM question 3.0-RELEASE Date: Tue, 27 Oct 1998 00:09:42 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm still debugging my problems with lockups during heavy network writing. I've installed two 2940's and can make it fail on either controller, eliminating my thought about some SCSI bus trash. Now, both of my drives seem to reset the tag queues when they go under load, is this normal? My Micrapolis 3243-19 (On 2940): tagged openings now 35 My Segate 39173W (On 2940UW): tagged openings now 63 tagged openings now 62 ....... tagged openings now 49 Is that supposed to happen? I'm wondering if that is an indication of a problem. The Seagate will drop them down slowly and then all of the sudden they plumet before it locks the system cold. Now, this happens with either local or network writes to the drives, however, local writes do not lock the machine. It's the heavy network writes from the wire that kill the machine. My other posts tell my setup. 100Mbit switch, fxp on FreeBSD, 905 on Linux, 905b on Win98. Ideas? Thanks! -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 05:24:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17449 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 05:24:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA17443 for ; Tue, 27 Oct 1998 05:24:43 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 27059 invoked from network); 27 Oct 1998 13:24:04 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 27 Oct 1998 13:24:04 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA10344; Tue, 27 Oct 1998 07:24:02 -0600 Date: Tue, 27 Oct 1998 07:24:02 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199810271324.HAA10344@bonkers.taronga.com> To: scsi@FreeBSD.ORG Subject: Re: Do we support > 32 drives yet? References: <199810261709.LAA29710@bonkers.taronga.com> <199810261835.TAA13230@yedi.iaf.nl> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199810261835.TAA13230@yedi.iaf.nl>, Wilko Bulte wrote: >??? The HSZ50 backend is not wide scsi. In a BA355 type enclosure you can >have 24 disks, using BA35[06] device shelves you can have 6 (backend >channels) * 7 (disks per shelf) is 42 disks. Using redundant power supplies >in your BA35[06] you are limited to 6 * 6 = 36 disks. I don't see how >you get to 84 disks. You can run two HSZ50s on a single SCSI bus, with 7 disks on each shelf, for a total of 84 disks. You can only assign them to 56 unique LUNs between the two units, though. Digital UNIX doesn't support more than 7 IDs per bus, unfortunately, but on FreeBSD you could fit four HSZ50s for 168 drives over 112 LUNs. You'd run out of minor numbers before you'd populated the third host adapter. Yes, this is way extreme. There's cheaper ways of doing it, but the sparse address space and nailed-down device numbers of the System V model is handy when you have a lot of hot-pluggable hardware. As for ADVFS... My experiences with ADVFS have made me extremely reluctant to trust it with anything more critical than a news spool. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 14:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03788 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 14:40:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03782 for ; Tue, 27 Oct 1998 14:40:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id XAA06621; Tue, 27 Oct 1998 23:39:33 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA29435 (5.67b/IDA-1.5); Tue, 27 Oct 1998 23:37:09 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA25162; Tue, 27 Oct 1998 19:42:56 +0100 (CET) From: Wilko Bulte Message-Id: <199810271842.TAA25162@yedi.iaf.nl> Subject: Re: Do we support > 32 drives yet? In-Reply-To: <199810271324.HAA10344@bonkers.taronga.com> from Peter da Silva at "Oct 27, 98 07:24:02 am" To: peter@taronga.com (Peter da Silva) Date: Tue, 27 Oct 1998 19:42:56 +0100 (CET) Cc: scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Peter da Silva wrote... > In article <199810261835.TAA13230@yedi.iaf.nl>, > Wilko Bulte wrote: > >??? The HSZ50 backend is not wide scsi. In a BA355 type enclosure you can > >have 24 disks, using BA35[06] device shelves you can have 6 (backend > >channels) * 7 (disks per shelf) is 42 disks. Using redundant power supplies > >in your BA35[06] you are limited to 6 * 6 = 36 disks. I don't see how > >you get to 84 disks. > > You can run two HSZ50s on a single SCSI bus, with 7 disks on each shelf, for > a total of 84 disks. You can only assign them to 56 unique LUNs between the If I understand you right you then have 1x HSZ50 per M-shelf (controller shelf). Having 2x HSZ50 each in it's own controller shelf gives you the 84 disks in a total of 12 device shelves. It is not really recommended (performancewise) to have multiple HSZ50 sharing a single FWD scsi host bus. For HSZ50 you can get away with this, for HSZ[78]0 you are really throttling things. And a config like this leaves you out of luck in case a HSZ50 dies ... Dual redundant pairs of HSZ50 make it considerably more costly. > two units, though. Digital UNIX doesn't support more than 7 IDs per bus, > unfortunately, but on FreeBSD you could fit four HSZ50s for 168 drives > over 112 LUNs. You'd run out of minor numbers before you'd populated the > third host adapter. Steel (DUnix 5.0) will probably have wide scsi addressing I suppose. > Yes, this is way extreme. There's cheaper ways of doing it, but the sparse > address space and nailed-down device numbers of the System V model is handy > when you have a lot of hot-pluggable hardware. It's expensive, but not extreme in the sheer size of the config. Running HSZ as a sort of glorified SCSI multiplexer is sort of eh... special ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 16:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22725 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 16:40:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22716; Tue, 27 Oct 1998 16:40:25 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA21267; Tue, 27 Oct 1998 16:39:43 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 27 Oct 1998 16:39:42 -0800 (PST) From: Doug White To: Rob Snow cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: CAM question 3.0-RELEASE In-Reply-To: <000d01be0170$6d5b0880$05e48486@lgc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Oct 1998, Rob Snow wrote: > I'm still debugging my problems with lockups during heavy network writing. > I've installed two 2940's and can make it fail on either controller, > eliminating my thought about some SCSI bus trash. > > Now, both of my drives seem to reset the tag queues when they go under load, > is this normal? > > My Micrapolis 3243-19 (On 2940): > tagged openings now 35 > > My Segate 39173W (On 2940UW): > tagged openings now 63 > tagged openings now 62 > ....... > tagged openings now 49 This is normal. The system tries to figure out how many tags each unit can support by experimentation and observation. Some disks are broken here and have to be quirk'd to turn off or reduce tags. > Is that supposed to happen? I'm wondering if that is an indication of a > problem. The Seagate will drop them down slowly and then all of the sudden > they plumet before it locks the system cold. Sounds like your Seagate doesn't handle tags correctly. I'd suggest checking with Seagate for a firmware upgrade, and in the meantime adding a quirk entry to /sys/cam/cam_xpt.c Search for 'quirks' and you'll find it. > Now, this happens with either local or network writes to the drives, > however, local writes do not lock the machine. It's the heavy network > writes from the wire that kill the machine. It's simply high outstanding disk transactions (which heavy writes would cause). Nothing wrong the network code, in fact it's probably a good thing that our network code can do better than the disk code :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 18:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03054 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 18:02:16 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from loviatar.webcom.com (loviatar.webcom.com [209.1.28.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03028; Tue, 27 Oct 1998 18:02:08 -0800 (PST) (envelope-from graeme@echidna.com) Received: from eresh.webcom.com (eresh.webcom.com [209.1.28.49]) by loviatar.webcom.com (8.9.1/8.9.1) with SMTP id RAA04142; Tue, 27 Oct 1998 17:01:30 -0800 Received: from [199.183.207.131] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 10078018; Tue Oct 27 17:59 PST 1998 Message-Id: <3636A466.5222@echidna.com> Date: Tue, 27 Oct 1998 20:58:14 -0800 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: Doug White Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: CAM question 3.0-RELEASE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug White wrote: > > On Tue, 27 Oct 1998, Rob Snow wrote: > > > I'm still debugging my problems with lockups during heavy network writing. > > I've installed two 2940's and can make it fail on either controller, > > eliminating my thought about some SCSI bus trash. > > > > Now, both of my drives seem to reset the tag queues when they go under load, > > is this normal? > > > > My Micrapolis 3243-19 (On 2940): > > tagged openings now 35 > > > > My Segate 39173W (On 2940UW): > > tagged openings now 63 > > tagged openings now 62 > > ....... > > tagged openings now 49 > > This is normal. The system tries to figure out how many tags each unit > can support by experimentation and observation. Some disks are > broken here and have to be quirk'd to turn off or reduce tags. Is there some reason why these messages are desirable and need to be on by default? They certainly get annoyingly voluminous at times. The following comment is from the freebsd-scsi archives: --------------------------------------------------------------------- I have some machines at work, and whenever I do lots of disk io, I get tons of the "tagged openings now XX" messages. I noticed that this is due to line 2819 in cam_xpt.c: if (bootverbose || 1) { xpt_print_path(crs->ccb_h.path); printf("tagged openings " "now %d\n", crs->openings); } Would it be possible to remove this 1 before the 3.0 release? -Chris Csanady --------------------------------------------------------------------- -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 19:04:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09860 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 19:04:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pixel.zycor.lgc.com (pixel.zycor.lgc.com [134.132.112.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09852; Tue, 27 Oct 1998 19:04:52 -0800 (PST) (envelope-from rsnow@lgc.com) Received: from diablo ([134.132.78.117]) by pixel.zycor.lgc.com (8.8.8/8.8.8) with SMTP id VAA04111; Tue, 27 Oct 1998 21:03:35 -0600 (CST) (envelope-from rsnow@lgc.com) Message-ID: <000c01be021f$896fcd80$754e8486@diablo> From: "Rob Snow" To: "Doug White" Cc: , Subject: Re: CAM question 3.0-RELEASE Date: Tue, 27 Oct 1998 21:03:26 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeppers, matter of fact FreeBSD showed a problem with my hardware, again. (You'd think I'd have learned since 1.1.5.1) It hit me when I woke up this morning, PCI problem. Turned out that PCI write combining was it, turned it off and everything works like a charm. I'm guessing that having the 2940UW and the fxp running at the levels that I can put them under with a 2xP6-233 FreeBSD and 1x300a@450 Linux box on full duplex 100 and a UW 'cuda showed the flaw. Now I can write to the network at over 10MB/sec. (at home :-) This is what I preach at the office all the time, the network doesn't have to be the bottleneck. Thanks for the info, this is my first run with CAM. I've been running a non-CAM -current for a while. Upgraded to 3.0-RELEASE as part of the server upgrade I did this weekend. (Accidently, /kernel didn't know my processor type and panicked on boot, kernel.GENERIC was left over from 2.2.5 and wouldn't mount shit. Woops) -Rob -----Original Message----- From: Doug White To: Rob Snow Cc: ; Date: Tuesday, October 27, 1998 6:39 PM Subject: Re: CAM question 3.0-RELEASE >On Tue, 27 Oct 1998, Rob Snow wrote: > >> I'm still debugging my problems with lockups during heavy network writing. >> I've installed two 2940's and can make it fail on either controller, >> eliminating my thought about some SCSI bus trash. >> >> Now, both of my drives seem to reset the tag queues when they go under load, >> is this normal? >> >> My Micrapolis 3243-19 (On 2940): >> tagged openings now 35 >> >> My Segate 39173W (On 2940UW): >> tagged openings now 63 >> tagged openings now 62 >> ....... >> tagged openings now 49 > >This is normal. The system tries to figure out how many tags each unit >can support by experimentation and observation. Some disks are >broken here and have to be quirk'd to turn off or reduce tags. > >> Is that supposed to happen? I'm wondering if that is an indication of a >> problem. The Seagate will drop them down slowly and then all of the sudden >> they plumet before it locks the system cold. > >Sounds like your Seagate doesn't handle tags correctly. I'd suggest >checking with Seagate for a firmware upgrade, and in the meantime adding a >quirk entry to /sys/cam/cam_xpt.c Search for 'quirks' and you'll find it. > >> Now, this happens with either local or network writes to the drives, >> however, local writes do not lock the machine. It's the heavy network >> writes from the wire that kill the machine. > >It's simply high outstanding disk transactions (which heavy writes would >cause). Nothing wrong the network code, in fact it's probably a good >thing that our network code can do better than the disk code :) > >Doug White >Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve >http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 19:37:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13251 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 19:37:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13213; Tue, 27 Oct 1998 19:37:19 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810280337.TAA13213@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLW; Tue, 27 Oct 1998 19:43:57 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:38:06 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 20:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15612 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 20:03:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15594; Tue, 27 Oct 1998 20:03:41 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA23308; Wed, 28 Oct 1998 14:32:21 +1030 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000c01be021f$896fcd80$754e8486@diablo> Date: Wed, 28 Oct 1998 14:32:20 +1030 (CST) From: "Daniel O'Connor" To: Rob Snow Subject: Re: CAM question 3.0-RELEASE Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Doug White Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 28-Oct-98 Rob Snow wrote: > Yeppers, matter of fact FreeBSD showed a problem with my hardware, again. > (You'd think I'd have learned since 1.1.5.1) > It hit me when I woke up this morning, PCI problem. Turned out that PCI > write combining was it, turned it off and everything works like a charm. Weird.. So much for the card saying if it will cope with write combining or not --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 20:55:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19046 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 20:55:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19041 for ; Tue, 27 Oct 1998 20:55:22 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id VAA21943; Tue, 27 Oct 1998 21:47:54 -0700 (MST) Date: Tue, 27 Oct 1998 21:47:54 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199810280447.VAA21943@narnia.plutotech.com> To: Graeme Tait cc: scsi@FreeBSD.ORG Subject: Re: CAM question 3.0-RELEASE X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <3636A466.5222@echidna.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <3636A466.5222@echidna.com> you wrote: >> This is normal. The system tries to figure out how many tags each unit >> can support by experimentation and observation. Some disks are >> broken here and have to be quirk'd to turn off or reduce tags. > > Is there some reason why these messages are desirable and need to be on by > default? They help us (the SCSI developers) diagnose problems. They also give the user an idea of the capabilities of their hardware. > They certainly get annoyingly voluminous at times. The following comment > is from the freebsd-scsi archives: They will stop as soon as the minimum tag count is achieved. Do you reboot your system all the time or something? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 21:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19546 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 21:01:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19540 for ; Tue, 27 Oct 1998 21:01:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00409; Tue, 27 Oct 1998 21:00:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280500.VAA00409@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: Graeme Tait , scsi@FreeBSD.ORG Subject: Re: CAM question 3.0-RELEASE In-reply-to: Your message of "Tue, 27 Oct 1998 21:47:54 MST." <199810280447.VAA21943@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 21:00:40 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article <3636A466.5222@echidna.com> you wrote: > >> This is normal. The system tries to figure out how many tags each unit > >> can support by experimentation and observation. Some disks are > >> broken here and have to be quirk'd to turn off or reduce tags. > > > > Is there some reason why these messages are desirable and need to be on by > > default? > > They help us (the SCSI developers) diagnose problems. They also give the > user an idea of the capabilities of their hardware. They also generate an awful lot of questioning traffic, which is indicating that they're not actually telling the user anything useful. I think this counts as a real-world assessment of the usefulness of the messages. > > They certainly get annoyingly voluminous at times. The following comment > > is from the freebsd-scsi archives: > > They will stop as soon as the minimum tag count is achieved. Do you reboot > your system all the time or something? Watching them count down one by one from 64 to 4 or so for a system with any number of disks is an irritating nuisance. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 27 23:45:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01375 for freebsd-scsi-outgoing; Tue, 27 Oct 1998 23:45:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01337; Tue, 27 Oct 1998 23:45:40 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810280745.XAA01337@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLW; Tue, 27 Oct 1998 19:43:57 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:38:06 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 03:39:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19599 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 03:39:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from loviatar.webcom.com (loviatar.webcom.com [209.1.28.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19593 for ; Wed, 28 Oct 1998 03:39:00 -0800 (PST) (envelope-from graeme@echidna.com) Received: from kigal.webcom.com (kigal.webcom.com [209.1.28.57]) by loviatar.webcom.com (8.9.1/8.9.1) with SMTP id CAA18398; Wed, 28 Oct 1998 02:38:22 -0800 Received: from [199.183.207.131] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 4998187; Wed Oct 28 03:36 PST 1998 Message-Id: <36372BA7.402@echidna.com> Date: Wed, 28 Oct 1998 06:35:19 -0800 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: "Justin T. Gibbs" , scsi@FreeBSD.ORG Cc: info@boatbooks.com Subject: Re: CAM question 3.0-RELEASE References: <199810280447.VAA21943@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > In article <3636A466.5222@echidna.com> you wrote: > >> This is normal. The system tries to figure out how many tags each unit > >> can support by experimentation and observation. Some disks are > >> broken here and have to be quirk'd to turn off or reduce tags. > > > > Is there some reason why these messages are desirable and need to be on by > > default? > > They help us (the SCSI developers) diagnose problems. They also give the > user an idea of the capabilities of their hardware. I guess it would help if I understood what they were telling me. > > They certainly get annoyingly voluminous at times. The following comment > > is from the freebsd-scsi archives: > > They will stop as soon as the minimum tag count is achieved. Do you reboot > your system all the time or something? Actually, yes ;-) Well, I have a couple of new systems sitting on my desk, and between two systems (which for the moment get powered down / rebooted often) and multiple disks, I've been seeing a lot of such messages. Somehow I had got the impression that the messages recurred within a single run period, but I gather now that's not supposed to be the case. For some reason also I get multiple copies to a console logged in as root, like ... (da0:ahc0:0:0:0) tagged openings now 51 (da0:ahc0:0:0:0) tagged openings now 52 (da0:ahc0:0:0:0) tagged openings now 49 in bright text, followed by ... Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 51 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 51 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 50 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 50 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 49 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 49 in regular text. Whatever context I was in gets scrolled right off the screen. It would be nice if these messages could be tamed in some way (like only the last in a count-down sequence issued), or made optional, or issued only when critical. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 10:27:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27269 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 10:27:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wmmc1.wmmc ([206.217.58.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27065; Wed, 28 Oct 1998 10:26:46 -0800 (PST) (envelope-from manager@wes.cc) Message-Id: <199810281826.KAA27065@hub.freebsd.org> Received: from mail.whitemmc.com (WESWEB4 [206.217.58.12]) by wmmc1.wmmc with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id VXX6GYLW; Tue, 27 Oct 1998 19:43:57 -0800 From: Project.Manager Date: Tue, 27 Oct 1998 19:38:06 PST Subject: Y2K and FEMA Compliant Project Management Solutions Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: undisclosed-recipients:; This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s.1618 =================================================== If you're interested in Y2K and FEMA Compliant Project Management Solutions, WorldClass Enterprise Systems, Inc., has some great solutions that are leading edge. Please take a tour of our various solutions at: http://www.wes.cc/tour/default.htm Or, if you're interested in getting some specific information, you can go directly to register and enter our full site at: http://www.wes.cc/frontdoor.htm Once you get to our homepage, you can either login and browse the complete site, full with examples of solutions and client implementations, or you can go directly to our "Free Quote" area to fill out a Needs Survey and request a detailed quote for services. Thanks in advance for taking the time to consider WorldClass Enterprise Systems, Inc. for your technology integration needs. Best Regards, New Business Development Manager http://www.wes.cc To be removed from our mailing list, simply reply with "REMOVE" in the subject. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 17:45:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07203 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 17:45:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07197 for ; Wed, 28 Oct 1998 17:45:16 -0800 (PST) (envelope-from pechter@shell.monmouth.com) Received: (from pechter@localhost) by shell.monmouth.com (8.8.5/8.7.3) id UAA03859 for freebsd-scsi@freebsd.org; Wed, 28 Oct 1998 20:44:47 -0500 (EST) From: Bill/Carolyn Pechter Message-Id: <199810290144.UAA03859@shell.monmouth.com> Subject: ielem in chio To: freebsd-scsi@FreeBSD.ORG Date: Wed, 28 Oct 1998 20:44:46 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there anyone working on porting the 3.0 chio command to 2.2.-stable so the ielem command is available? Bill +---------------------------------------------------------------------------+ | Bill and/or Carolyn Pechter | pechter@shell.monmouth.com | | Bill Gates is a Persian cat and a monocle away from being a villain in | | a James Bond movie -- Dennis Miller | +---------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 19:20:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20065 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 19:20:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20058 for ; Wed, 28 Oct 1998 19:20:11 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id UAA05989; Wed, 28 Oct 1998 20:20:00 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810290320.UAA05989@panzer.plutotech.com> Subject: Re: ielem in chio In-Reply-To: <199810290144.UAA03859@shell.monmouth.com> from Bill/Carolyn Pechter at "Oct 28, 98 08:44:46 pm" To: pechter@shell.monmouth.com (Bill/Carolyn Pechter) Date: Wed, 28 Oct 1998 20:20:00 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill/Carolyn Pechter wrote... > Is there anyone working on porting the 3.0 chio command to 2.2.-stable > so the ielem command is available? You could always use the 2.2 port of CAM. There's a release available here: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/development/cam/2.2CAM-19980716-SNAP/ We may have another snapshot out before too long. (don't expect it before this weekend, though.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 19:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24299 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 19:57:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24294 for ; Wed, 28 Oct 1998 19:57:53 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA27577; Thu, 29 Oct 1998 14:27:17 +1030 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810290320.UAA05989@panzer.plutotech.com> Date: Thu, 29 Oct 1998 14:27:16 +1030 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: ielem in chio Cc: freebsd-scsi@FreeBSD.ORG, (Bill/Carolyn Pechter) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Oct-98 Kenneth D. Merry wrote: > We may have another snapshot out before too long. (don't expect it before > this weekend, though.) Wohoo.. Any fixes for the shared memory problems coming up by chance? :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 20:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25385 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 20:05:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25368 for ; Wed, 28 Oct 1998 20:05:37 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA06152; Wed, 28 Oct 1998 21:04:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810290404.VAA06152@panzer.plutotech.com> Subject: Re: ielem in chio In-Reply-To: from Daniel O'Connor at "Oct 29, 98 02:27:16 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 28 Oct 1998 21:04:10 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, pechter@shell.monmouth.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daniel O'Connor wrote... > > On 29-Oct-98 Kenneth D. Merry wrote: > > We may have another snapshot out before too long. (don't expect it before > > this weekend, though.) > Wohoo.. Any fixes for the shared memory problems coming up by chance? :) Well, at least on -current, I've been able to fix the problem by limiting the number of sectors that cdda2wav reads. (25 blocks seems to work well) It looks like there's some sort of corruption problem when the transfer sizes through the passthrough driver are between 64K and 128K. (My guess is some sort of VM problem.) I meant to say something about this a few days ago, but I forgot. I'm curious to see whether that (limiting the number of sectors read at a time) will fix the problems you've been having under -stable with cdda2wav. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 20:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27284 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 20:22:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27278 for ; Wed, 28 Oct 1998 20:22:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA27671; Thu, 29 Oct 1998 14:52:09 +1030 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810290404.VAA06152@panzer.plutotech.com> Date: Thu, 29 Oct 1998 14:52:08 +1030 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: ielem in chio Cc: freebsd-scsi@FreeBSD.ORG, pechter@shell.monmouth.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Oct-98 Kenneth D. Merry wrote: > > Wohoo.. Any fixes for the shared memory problems coming up by chance? :) > Well, at least on -current, I've been able to fix the problem by limiting > the number of sectors that cdda2wav reads. (25 blocks seems to work well) OK.. I didn't know the problem was also present in -current tho.. > It looks like there's some sort of corruption problem when the transfer > sizes through the passthrough driver are between 64K and 128K. (My guess > is some sort of VM problem.) Yeah, I was wondering if anyone had any information about the underlying problem :) > I'm curious to see whether that (limiting the number of sectors read at a > time) will fix the problems you've been having under -stable with cdda2wav. Hmm, I'll have to wait until we get some more machines before I can test :) Also I think the problem occurs in some circumstances while writing a CD (cdrecord uses shared memory to hold its ring buffer). I'm not sure about this tho since it happens less often. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 28 23:28:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14593 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 23:28:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dante.visionaire.net (visionaire.ping.de [195.37.123.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14586; Wed, 28 Oct 1998 23:28:44 -0800 (PST) (envelope-from thomas@visionaire.ping.de) Received: from thomas by dante.visionaire.net with local (Exim 1.92 #1 (Debian)) id 0zYn0e-0000KU-00; Thu, 29 Oct 1998 08:00:44 +0000 Message-ID: <19981029080043.C812@visionaire.ping.de> Date: Thu, 29 Oct 1998 08:00:43 +0000 From: Thomas Keusch To: Howard Lew , freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems References: <19980928053655.19907@visionaire.ping.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.2 In-Reply-To: ; from Howard Lew on Wed, Sep 30, 1998 at 11:40:42PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 30, 1998 at 11:40:42PM -0700, Howard Lew wrote: > > I have a very similar/the same problem with a SymbiosLogic > > 8750SP Ultra-SCSI controller and two IBM DCAS 4.1 Gb HDDs. > > > > I did not find a solution yet, but it seems that the problem on > > my box is related to FreeBSD trying to find out the size of the disks. > > This produces basically the same error as yours, but quits scanning > > with an "could not get size" error for each disk after a while. > > Yes, this is exactly the same problem I am having. I guess if I wait a > very long time, it might get past the boot probe after failing to detect > the affected drives, but generally the boot probe shouldn't take 1 hour or > more to do. Did you ever try if it gets past that state? If so, how long did it take? > > I took of the entire bus from the controller, so that the controller > > was the only SCSI device in the system. FreeBSD doesn't choke on the > > controller itself, it's the disks. > > Yes, it is the disks -- not the controller. > > There is an easy fix if you already have a working FreeBSD system that > is booting off another drive. As long as you are not using the WIDE bus, > you can force everything to 8 bit mode. I found that changing the > SCSI_NCR_MAX_WIDE to 0 does the trick. Of course, this forces 8 bit > mode and disables the WIDE bus, so you should not have any devices on the > WIDE bus. I don't have ANY Wide devices. The controller is Ultra SCSI only, but has a Wide capable chipset nevertheless. So this fix will work for me, the only drawback being that I have to install do an IDE disk first, learning how to compile the kernel first, ... etc. > As it is, this is not a real fix because you need a working system to > make the changes in ncr.c and then recompile the system. So if a new > user wants to install FreeBSD on his hard disk, this quick fix will not > work as they won't be able to get through the installation. I've been using Linux for a year now, so I guess I have the experience to get my system working, but I'm still dependant on an IDE disk, which I luckily still have. A totally inexperienced new user would have at least a really hard time to install onto SCSI disks under these circumstances, that's right. Odds are, that there are more narrow SCSI controllers out there which have this "feature" of a Wide chipset, so I guess an automatic fallback to narrow mode would be a good thing(tm). Anyway, I will try your fix. Thank you for that. Have a nice day -- thomas. .powered.by.debian/linux. irc.:.#meeting.points, #frust.ger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 29 10:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01441 for freebsd-scsi-outgoing; Thu, 29 Oct 1998 10:47:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01424; Thu, 29 Oct 1998 10:47:53 -0800 (PST) (envelope-from digital@www2.shoppersnet.com) Received: from localhost (digital@localhost) by www2.shoppersnet.com (8.8.8/8.8.8) with SMTP id KAA17427; Thu, 29 Oct 1998 10:50:01 -0800 (PST) (envelope-from digital@www2.shoppersnet.com) Date: Thu, 29 Oct 1998 10:50:00 -0800 (PST) From: Howard Lew To: Thomas Keusch cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: NCR 53c875 SCSI Problems In-Reply-To: <19981029080043.C812@visionaire.ping.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Oct 1998, Thomas Keusch wrote: > On Wed, Sep 30, 1998 at 11:40:42PM -0700, Howard Lew wrote: > > > > I have a very similar/the same problem with a SymbiosLogic > > > 8750SP Ultra-SCSI controller and two IBM DCAS 4.1 Gb HDDs. > > > > > > I did not find a solution yet, but it seems that the problem on > > > my box is related to FreeBSD trying to find out the size of the disks. > > > This produces basically the same error as yours, but quits scanning > > > with an "could not get size" error for each disk after a while. > > > > Yes, this is exactly the same problem I am having. I guess if I wait a > > very long time, it might get past the boot probe after failing to detect > > the affected drives, but generally the boot probe shouldn't take 1 hour or > > more to do. > > Did you ever try if it gets past that state? If so, how long did it take? No I never tried because this NCR 875 machine is not a full time FreeBSD OS machine... It is booted up only occasionally in FreeBSD, but taking hours to bootup is not acceptable. So that's why I am not sure if it ever gets past that point. I remember aborting the scsi boot probe after more than 2 hours, so I am sure it takes even longer than that. > I don't have ANY Wide devices. The controller is Ultra SCSI only, but has a > Wide capable chipset nevertheless. So this fix will work for me, the only > drawback being that I have to install do an IDE disk first, learning how > to compile the kernel first, ... etc. > Yes. the quick fix allows you to use the scsi hard drive but not as your main FreeBSD hard drive -- a true bummer if the drive was purchased just for use with FreeBSD. > > As it is, this is not a real fix because you need a working system to > > make the changes in ncr.c and then recompile the system. So if a new > > user wants to install FreeBSD on his hard disk, this quick fix will not > > work as they won't be able to get through the installation. > > A totally inexperienced new user would have at least a really hard time > to install onto SCSI disks under these circumstances, that's right. > > Odds are, that there are more narrow SCSI controllers out there which have > this "feature" of a Wide chipset, so I guess an automatic fallback to > narrow mode would be a good thing(tm). > Yes. As far as I know, this has not been fixed... I guess the code only needs to add a check to see if the "wide scsi guess" doesn't kill the communication between the scsi drive and the controller. If it does, then switch to narrow. Otherwise, stay WIDE. If someone doesn't fix this by March of next year, maybe I will have time to fix it then... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 30 13:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26758 for freebsd-scsi-outgoing; Fri, 30 Oct 1998 13:26:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26747 for ; Fri, 30 Oct 1998 13:26:25 -0800 (PST) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) with SMTP id QAA03607 for ; Fri, 30 Oct 1998 16:26:10 -0500 (EST) X-Authentication-Warning: tor-dev1.nbc.netcom.ca: dacole owned process doing -bs Date: Fri, 30 Oct 1998 16:26:09 -0500 (EST) From: Dave Cole X-Sender: dacole@tor-dev1.nbc.netcom.ca To: freebsd-scsi@FreeBSD.ORG Subject: mt status Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any way to figure out which file no. and block no. a tape is sitting at? Within solaris, an 'mt status' gives you a nice useful display like: Mammoth EXB-8900 8mm Helical Scan tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 Is there any parallel in the BSD world? If not, why not? I find this far far more important than knowing what other densities I can use. ---------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator |* dacole@rik.net * | office/~dacole/ Netcom Canada |* www.rik.net/~dacole/ * 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 31 06:53:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03081 for freebsd-scsi-outgoing; Sat, 31 Oct 1998 06:53:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03074 for ; Sat, 31 Oct 1998 06:53:49 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id MAA09850 for scsi@freebsd.org; Sat, 31 Oct 1998 12:53:45 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810311453.MAA09850@roma.coe.ufrj.br> Subject: CAM: aha at 0x334 -> not found To: scsi@FreeBSD.ORG Date: Sat, 31 Oct 1998 12:53:45 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm trying -current from last week at home, and it could not detect my aha1542 at first, telling me that: Oct 31 12:27:10 dogbert /kernel: Oct 31 12:27:10 dogbert /kernel: aha_isa_probe: Invalid baseport of 0x334 specified. Oct 31 12:27:10 dogbert /kernel: aha_isa_probe: Nearest valid baseport is 0x330. Oct 31 12:27:10 dogbert /kernel: aha_isa_probe: Failing probe. Oct 31 12:27:10 dogbert /kernel: aha0 not found at 0x334 I could solve this by rearranging the order of valid isa addresses at the aha driver. The code seems to need them in reverse numeric order. struct aha_isa_port aha_isa_ports[] = { { 0x334, 0 }, { 0x330, 0 }, { 0x234, 0 }, { 0x230, 0 }, { 0x134, 0 }, { 0x130, 0 } }; Now it detects my aha without problem: Oct 31 12:35:51 dogbert /kernel: aha0 at 0x334-0x337 irq 11 drq 6 on isa Oct 31 12:35:51 dogbert /kernel: aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host A dapter, SCSI ID 7, 16 CCBs Could somebody with CAM understanding check this and fix the sources ? TIA, Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 31 18:09:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20190 for freebsd-scsi-outgoing; Sat, 31 Oct 1998 18:09:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20173 for ; Sat, 31 Oct 1998 18:09:40 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id EAA12346 for ; Sun, 1 Nov 1998 04:09:32 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id FAA00336 for freebsd-scsi@freebsd.org; Sun, 1 Nov 1998 05:09:49 +0200 (EET) (envelope-from vallo) Message-ID: <19981101050949.A291@matti.ee> Date: Sun, 1 Nov 1998 05:09:49 +0200 From: Vallo Kallaste To: freebsd-scsi@FreeBSD.ORG Subject: AIC-7895 and 20.0MB/s transfers Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I purchased new motherboard recently which have onboard AIC-7895P chip. All is well but dmesg says that I have 20MB/s transfers only. When working with old ncr controller I have 40MB/s transfers. Some bits from dmesg: ahc0: rev 0x04 int a irq 16 on pci0.18.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 10. ahc1: rev 0x04 int b irq 16 on pci0.18.1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 10. ncr0: rev 0x03 int a irq 16 on pci0.19.0 changing root device to da0s1a da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc1 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) cd0 at ncr0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present I feel that this issue was discussed lately somewhere but I'm not sure. What I can do to get back faster transfers ? Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 31 18:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21971 for freebsd-scsi-outgoing; Sat, 31 Oct 1998 18:22:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21966 for ; Sat, 31 Oct 1998 18:22:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00418; Sat, 31 Oct 1998 18:22:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811010222.SAA00418@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: vallo@matti.ee cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers In-reply-to: Your message of "Sun, 01 Nov 1998 05:09:49 +0200." <19981101050949.A291@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 18:22:15 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I purchased new motherboard recently which have onboard AIC-7895P > chip. All is well but dmesg says that I have 20MB/s transfers only. > When working with old ncr controller I have 40MB/s transfers. Some > bits from dmesg: Enable "Ultra SCSI Speed" in the BIOS setup utility. RTFM. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 31 18:25:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22188 for freebsd-scsi-outgoing; Sat, 31 Oct 1998 18:25:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22183 for ; Sat, 31 Oct 1998 18:25:47 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA27464; Sat, 31 Oct 1998 19:25:34 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811010225.TAA27464@panzer.plutotech.com> Subject: Re: AIC-7895 and 20.0MB/s transfers In-Reply-To: <19981101050949.A291@matti.ee> from Vallo Kallaste at "Nov 1, 98 05:09:49 am" To: vallo@matti.ee Date: Sat, 31 Oct 1998 19:25:34 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vallo Kallaste wrote... > I purchased new motherboard recently which have onboard AIC-7895P > chip. All is well but dmesg says that I have 20MB/s transfers only. > When working with old ncr controller I have 40MB/s transfers. Some > bits from dmesg: > [ ... ] > changing root device to da0s1a > da0 at ahc0 bus 0 target 6 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing > Enabled > da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) > da1 at ahc1 bus 0 target 6 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing > Enabled > da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) > cd0 at ncr0 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 10.0MB/s transfers (10.0MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not > present > > I feel that this issue was discussed lately somewhere but I'm not > sure. What I can do to get back faster transfers ? Well, I'll ask the obvious question: Is support for Ultra SCSI speeds enabled in the Adaptec BIOS? (ctrl-A when you boot the machine) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 31 20:14:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04628 for freebsd-scsi-outgoing; Sat, 31 Oct 1998 20:14:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04616 for ; Sat, 31 Oct 1998 20:14:12 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA02212; Sat, 31 Oct 1998 20:15:17 -0800 (PST) Message-Id: <199811010415.UAA02212@implode.root.com> To: "Kenneth D. Merry" cc: vallo@matti.ee, freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers In-reply-to: Your message of "Sat, 31 Oct 1998 19:25:34 MST." <199811010225.TAA27464@panzer.plutotech.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 31 Oct 1998 20:15:17 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Vallo Kallaste wrote... >> I purchased new motherboard recently which have onboard AIC-7895P >> chip. All is well but dmesg says that I have 20MB/s transfers only. >> When working with old ncr controller I have 40MB/s transfers. Some >> bits from dmesg: ... >Well, I'll ask the obvious question: Is support for Ultra SCSI speeds >enabled in the Adaptec BIOS? (ctrl-A when you boot the machine) Hi, Ken. I'm having the same problem here with a new Tyan 1836DLUAN. Same deal - 7895 chip on the motherboard and an Ultra-2 (LVD) Seagate Cheetah is probing at 10Mhz rather than 40Mhz. On boot -v, it reports: (ahc0 scrolled out of the message buffer, but is identical to ahc1) ahc1: rev 0x04 int b irq 10 on pci0.18.1 using shared irq10. ahc1: Reading SEEPROM...done. ahc1: internal 50 cable not present, internal 68 cable not present ahc1: external cable not present ahc1: BIOS eeprom is present ahc1: High byte termination Enabled ahc1: Low byte termination Enabled ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Resetting Channel B ahc1: Downloading Sequencer Program... 384 instructions downloaded ... Waiting 2 seconds for SCSI devices to settle (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. ahc1: Selection Timeout on A:0. 1 SCBs aborted ahc0: Selection Timeout on A:1. 1 SCBs aborted ahc1: Selection Timeout on A:1. 1 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc1: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc1: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:4. 1 SCBs aborted ahc1: Selection Timeout on A:4. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc1: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted ahc1: Selection Timeout on A:6. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc1: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc1: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc1: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc1: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc1: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc1: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc1: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 ahc1: Selection Timeout on A:15. 1 SCBs aborted pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number NJ12299500002905H40F pass0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number NJ12299500002905H40F da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) The Adaptec BIOS is configured properly - all drives are set for 40Mhz negotiation. Termination is set auto. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message