From owner-freebsd-scsi Sun Oct 17 7:51:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front1m.grolier.fr (front1m.grolier.fr [195.36.216.51]) by hub.freebsd.org (Postfix) with ESMTP id 49A6A14BEE for ; Sun, 17 Oct 1999 07:51:40 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-99-68.villette.club-internet.fr [194.158.99.68]) by front1m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id QAA22985; Sun, 17 Oct 1999 16:51:09 +0200 (MET DST) Date: Sun, 17 Oct 1999 17:13:19 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: Matthew Jacob Cc: "Kenneth D. Merry" , "Chris D. Faulhaber" , Andrew Gallatin , scsi@FreeBSD.ORG Subject: Re: FreeBSD 3.2 / Slow SCSI Dell PowerEdge 4300 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 16 Oct 1999, Matthew Jacob wrote: > > Hmmm... This can only happened with too old or poor designed SCSI > > controllers. Well designed SCSI controllers do not interrupt uselessly. > > About disabling SCSI disconnections, I would have been glad not to have > > read that. Note that I am not going to ever choose a SUN originated > > system for numerous reasons. ;-) >=20 > I'm talking about 14 years ago, btw... So, before you slam Sun for this, At that early time, they could use low-cost processors like Z80 or 68XX for the handling of SCSI phases sequence. Given skilled ingenieers, they couldn't miss that, in my opinion. > remember it was pretty good for the time and price class. I would buy Sun= s > *now*, but for other reasons and for certain properties that may popular > OSS systems have no clue about yet. A supplier that does not apply standards or reinvent parts of standards is a great burden for the industry. > > > I suspect that the right thing here is to to ultimately do completely > > > adaptive scheduling with hints- this would also solve the arguments I > >=20 > > May be, a simple but kind bug that add some mess-up to disksort would > > solve the problem. :-) > >=20 > > > constantly have with Matt Dillon over whether MAXPHYS is too small at > > > 128KB (it most certainly is if you have a job mix that's mainly large > > > sequential writes or reads)- but until that point, document the tools= that > > > allow you to tune things and tell users "Knock yerself out... have a = great > > > time!" > >=20 > > I have measured 35MB/s throughtput on a 80MB/s LVD SCSI BUS using 4K > > actual IO chunks. This let me think that 64 KB is not that small given = not > > ridiculouly high IO latency. May-be for Ultra-160 (and probably for fut= ure > > Ultra-320), 64KB will be to small. >=20 > Again- it depends. I doubt that it's the bus speed that makes this a fine > thing here- it's very likely the faster microprocessors on the newer LVD > disks. Fibre Channel disks have some of the same properties, but even > better is the fact that non-data phases pretty much don't exist in > fibre channel, so there's no such thing as blowing through a 4k data phas= e > at 40Mhz+ only to sit and pick your nose for hundreds of microseconds for > status and message in and bus settle delay and arb delay..... In most applications, the average actual IO size is less than 8KB. So, unless most are rewritten for making good use of large actual IO chunks, such a facility will not make most existing systems faster. For now, only a small number of applications can take advantage of actual IOs larger than 64 KB. On the other hand, SPI is still widely used on our planet and will probably still be used for a long time. With Ultra-160, 8KB can be transferred in 50 micro-seconds. Using interfaces with high latency will not allow to take advantage of this technology for real applications. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 17 22:14:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6F31214C35 for ; Sun, 17 Oct 1999 22:14:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA70335; Sun, 17 Oct 1999 23:13:40 -0600 (MDT) (envelope-from ken) Message-Id: <199910180513.XAA70335@panzer.kdm.org> Subject: Re: FreeBSD 3.2 / Slow SCSI Dell PowerEdge 4300 In-Reply-To: from Matthew Jacob at "Oct 16, 1999 10:44:10 am" To: mjacob@feral.com Date: Sun, 17 Oct 1999 23:13:39 -0600 (MDT) Cc: groudier@club-internet.fr (Gerard Roudier), cdf.lists@fxp.org (Chris D. Faulhaber), gallatin@cs.duke.edu (Andrew Gallatin), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Matthew Jacob wrote... > > > What seems to happen when tagged command queuing is disabled, is that the > > IO scheduling policy can stay a long time (seconds) on one IO stream and > > then switch to another one, and so on ... This seem to be due (just > > guessing) to a side effect of the disksort algorithm that just makes the > > supposed multi-threaded IO streams become a succession of single-threaded > > IO streams that may each last seconds. > > It's conceivable that with tagged queing there *shouldn't* be a disksort > function on the processor except with respect to synchronization > barriers. Well, we could disable the sort for tagged queueing drives, and enable it for drives that aren't capable of it. The only complication would come when tagged queueing is enabled/disabled for a given drive. I suppose it wouldn't be that complicated, though. You could probably just switch back and forth between bufqdisksort() and bufq_insert_tail() without too much trouble. The transport layer necessarily does things a little differently, but my guess is that it probably wouldn't do too much harm in the bufq to just switch on the fly. Before we go off and do anything like that, though, someone (i.e. not me) should probably do some benchmarks and see just what the difference is between sorting and not sorting. This may largely depend on how deep the bufq in the da(4) driver gets. If it doesn't get very deep, it won't make much difference whether you sort or not. And what do you mean by synchronization barriers? Ordered writes? If you aren't sorting, you're putting things through in FIFO order, and so every write ends up being an ordered write. (bufqdisksort() just uses bufq_insert_tail() if the request in question is B_ORDERED, and then everything before that in the queue is locked against any change in ordering.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 18 15:11:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2951114A12 for ; Mon, 18 Oct 1999 15:11:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA19559 for freebsd-scsi@freebsd.org; Mon, 18 Oct 1999 23:57:20 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA43931 for freebsd-scsi@freebsd.org; Mon, 18 Oct 1999 23:53:08 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910182153.XAA43931@yedi.iaf.nl> Subject: interesting(?) message from CAM on Alpha? To: freebsd-scsi@freebsd.org (FreeBSD SCSI hackers) Date: Mon, 18 Oct 1999 23:53:08 +0200 (CEST) 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+ PL43 (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 By sheer accident: alpine#camcontrol devlist at scbus1 target 0 lun 0 (pass0,da0) at scbus1 target 1 lun 0 (pass1,da1) at scbus1 target 4 lun 0 (pass2,cd0) alpine#Oct 18 22:35:31 alpine /kernel: WARNING: driver xpt should register devices with make_dev() (dev_t = "#xpt/0") Only happened once BTW. I haven't checked if it is anything serious. Never seen it on an Intel, this is -current on an Alpha Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://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 Mon Oct 18 15:15:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 4072715199 for ; Mon, 18 Oct 1999 15:15:02 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id RAA60829; Mon, 18 Oct 1999 17:14:43 -0500 (CDT) (envelope-from bob) Date: Mon, 18 Oct 1999 17:14:43 -0500 From: Bob Willcox To: Stephen McKay Cc: Wilko Bulte , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI surprise! (was: Softupdates reliability?) Message-ID: <19991018171443.B89307@luke.pmr.com> Reply-To: Bob Willcox References: <199908311524.RAA53070@yedi.iaf.nl> <199909020359.NAA11043@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199909020359.NAA11043@nymph.detir.qld.gov.au>; from Stephen McKay on Thu, Sep 02, 1999 at 01:59:32PM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Sep 02, 1999 at 01:59:32PM +1000, Stephen McKay wrote: > On Tuesday, 31st August 1999, Wilko Bulte wrote: > > >As Stephen McKay wrote ... > >> I'll check the drive more carefully tonight for "power terminator from BUS" > >> stuff to see if there is any possible silly stuff there. But I think the > >> fact is that sometimes it's not safe to just pull the power plug. > > > >Maybe there is something really weird about your particular drive. I can > >only repeat my experience which is different :/ > > I checked the problem drive last night. The drive was set to power its own > terminator, but the terminator is definitely off. It can also power the > SCSI bus, but that's off too. So, all looks normal. > > I'll just assume this is a rogue drive until I see another one. I still > don't understand how it's possible though. In my experiences with SCSI, I believe that just about anything is possible! I have spent several years developing SCSI device drivers and, more importantly, much of that time was devoted to testing. In many of these tests I would deliberatly use defective and/or questionable devices (its easy to collect defective SCSI devices, it turns out). Really bad stuff can occur on the bus (you really need a SCSI bus analyzer if you're doing serious SCSI testing) due to various combinations of devices, cables, and terminators. I suppose partly as a result of my experiences in my SCSI testing days (haven't done it in a few years), for production systems that I depend on, I always keep my SCSI busses as simple as possible. I try not to mix device speeds and types by installing multiple controller cards and installing all of my disks on one (or more, as necessary), and all the other devices (tape, cdrom, etc.) on a separate bus. Makes me feel better (and in my experience, increases stability). As a further anecdotal note, I once had a sudden and catastrophic SCSI bus failure on a system that had been running fine and I hadn't had open in over a year. Upon diagnosing the failure I was surprised to discover a terminator installed on one of the devices in the middle of the chain (this resulted in three terminators on the bus!). Upon removing the bogus terminator everything began working fine again. Guess some driver(s) on the bus just finally got tired of driving the additional load. :-( Bob -- Bob Willcox Don't tell me that worry doesn't do any good. bob@pmr.com I know better. The things I worry about don't Austin, TX happen. -- Watchman Examiner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 18 21:56:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7A36615E70 for ; Mon, 18 Oct 1999 21:56:12 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA76104; Mon, 18 Oct 1999 22:56:01 -0600 (MDT) (envelope-from ken) Message-Id: <199910190456.WAA76104@panzer.kdm.org> Subject: Re: interesting(?) message from CAM on Alpha? In-Reply-To: <199910182153.XAA43931@yedi.iaf.nl> from Wilko Bulte at "Oct 18, 1999 11:53:08 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Mon, 18 Oct 1999 22:56:01 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI hackers) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Wilko Bulte wrote... > By sheer accident: > > alpine#camcontrol devlist > at scbus1 target 0 lun 0 (pass0,da0) > at scbus1 target 1 lun 0 (pass1,da1) > at scbus1 target 4 lun 0 (pass2,cd0) > alpine#Oct 18 22:35:31 alpine /kernel: WARNING: driver xpt should register > devices with make_dev() (dev_t = "#xpt/0") > > Only happened once BTW. I haven't checked if it is anything serious. > Never seen it on an Intel, this is -current on an Alpha It probably just means that the xpt peripheral driver needs to be tweaked for the latest cdev interface change. Ken -- Kenneth Merry ken@kdm.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 19 0:26:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 101D71612A for ; Tue, 19 Oct 1999 00:26:41 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id JAA21496; Tue, 19 Oct 1999 09:26:32 +0200 (CEST) (envelope-from erik@habatech.no) 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: <199910182153.XAA43931@yedi.iaf.nl> Date: Tue, 19 Oct 1999 09:26:15 +0200 (CEST) From: "Erik H. Bakke" To: Wilko Bulte Subject: RE: interesting(?) message from CAM on Alpha? Cc: (FreeBSD SCSI hackers) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18-Oct-99 Wilko Bulte wrote: > alpine#Oct 18 22:35:31 alpine /kernel: WARNING: driver xpt should register > devices with make_dev() (dev_t = "#xpt/0") > > Only happened once BTW. I haven't checked if it is anything serious. > Never seen it on an Intel, this is -current on an Alpha > This was covered on the list recently, and is due to a change in the way devices are registered. It is nothing serious, just a reminder to the author of the driver in question that the code should be rewritten to the new API. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 19 6:37:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay4.mail.uk.psi.net (relay4.mail.uk.psi.net [154.32.111.6]) by hub.freebsd.org (Postfix) with ESMTP id BD8EC17002 for ; Tue, 19 Oct 1999 06:37:36 -0700 (PDT) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay4.mail.uk.psi.net with smtp (Exim 2.12 #2) id 11dZPw-0004bP-00 for freebsd-scsi@freebsd.org; Tue, 19 Oct 1999 14:35:08 +0100 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 8025680F.004AD247 ; Tue, 19 Oct 1999 14:37:14 +0100 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: freebsd-scsi@freebsd.org Message-ID: <8025680F.004AD14E.00@mail.plasmon.co.uk> Date: Tue, 19 Oct 1999 14:37:11 +0100 Subject: Disabling Disconnects on 53c810a Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to disable disconnects in order to test a theory about a problem that I'm seeing. However, looking at the bus on a SCSI analyzer, the CAM_DIS_DISCONNECT flag doesn't seem to have the desired effect. The identify message is still reporting as 0xC0, i.e. disconnects allowed. This isn't surprising, as I can't find any mention of the CAM flag in ncr.c. Is there any method of disabling disconnects with the NCR driver? What's the difference between CAM_DIS_AUTODISC and CAM_DIS_DISCONNECT? (Sorry if that's a stupid question, I'm not very familier with low-level SCSI). Thanks, Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 19 10:31:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 5E7ED1778D for ; Tue, 19 Oct 1999 10:31:39 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id LAA45021; Tue, 19 Oct 1999 11:21:16 -0600 (MDT) Date: Tue, 19 Oct 1999 11:21:16 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199910191721.LAA45021@narnia.plutotech.com> To: Leif Neland Cc: scsi@FreeBSD.org Subject: Re: adv hanging at boot X-Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Current, cvsup'ed daily. > > My adv is hanging now at "Waiting 5 seconds for SCSI devices to settle" > Two weeks or so it then gave 4 messages about "bus timeout" or so (Sorry I > can't remember the exact wording; it doesn't say so now.) You should send these kinds of reports to the SCSI list. My guess is that there is some problem with interrupt routing to your ISA card. I should be able to test out the ISA ADV cards when I get back from FreeBSD-con. -- 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 19 11:39:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8BCE8178FF for ; Tue, 19 Oct 1999 11:39:14 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA14736; Tue, 19 Oct 1999 20:14:34 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01084; Tue, 19 Oct 1999 20:14:58 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910191814.UAA01084@yedi.iaf.nl> Subject: Re: interesting(?) message from CAM on Alpha? In-Reply-To: from "Erik H. Bakke" at "Oct 19, 1999 9:26:15 am" To: erik@habatech.no (Erik H. Bakke) Date: Tue, 19 Oct 1999 20:14:58 +0200 (CEST) Cc: freebsd-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+ PL43 (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 Erik H. Bakke wrote ... > > On 18-Oct-99 Wilko Bulte wrote: > > alpine#Oct 18 22:35:31 alpine /kernel: WARNING: driver xpt should register > > devices with make_dev() (dev_t = "#xpt/0") > > > > Only happened once BTW. I haven't checked if it is anything serious. > > Never seen it on an Intel, this is -current on an Alpha > > > This was covered on the list recently, and is due to a change in the way > devices are registered. OK, must have missed that one. > It is nothing serious, just a reminder to the author of the driver in question > that the code should be rewritten to the new API. Fair enough -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://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 19 13: 8:31 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 7178A17B8B for ; Tue, 19 Oct 1999 13:08:22 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 11dfZK-000IdO-00; Tue, 19 Oct 1999 16:09:14 -0400 To: Tom Cc: Joao Pagaime , scsi@freebsd.org From: "Gary Palmer" Subject: Re: FreeBSD 3.2 / Slow SCSI Dell PowerEdge 4300 In-reply-to: Your message of "Thu, 14 Oct 1999 06:28:09 PDT." Date: Tue, 19 Oct 1999 16:09:13 -0400 Message-ID: <71632.940363753@noop.colo.erols.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom wrote in message ID : > > pass2 at ahc0 bus 0 target 6 lun 0 > > pass2: Fixed Processor SCSI-2 device > > pass2: 3.300MB/s transfers > > That isn't a backplane. That looks like some kind of special SCSI > device on your chain. Perhaps it is a backplane status reporting device > of some sort. But it is not the backplane itself. Its probably the environmental monitoring device (voltage levels, etc) that Dell provide. I bet Solaris would report it as a SES (SCSI Environmental Services) device. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 19 15:24:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from s5.elec.uq.edu.au (s5.elec.uq.edu.au [130.102.96.5]) by hub.freebsd.org (Postfix) with ESMTP id D0CE917AE8; Tue, 19 Oct 1999 15:24:47 -0700 (PDT) (envelope-from clary@s5.elec.uq.edu.au) Received: (from clary@localhost) by s5.elec.uq.edu.au (8.8.8/8.8.5) id IAA12877; Wed, 20 Oct 1999 08:24:46 +1000 (EST) From: Clary Harridge Message-Id: <199910192224.IAA12877@s5.elec.uq.edu.au> Subject: RAID V driver for DPT SCSI host adapter To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Date: Wed, 20 Oct 1999 08:24:46 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (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 have been told by Susan Handley at DPT Tech Support "that you can obtain a copy of our beta driver via the FreeBSD User News Group." Does anyone know where the driver can be obtained ? I need a driver for a DPT PM1554U2. Thanks! -- regards Department of Computer Science and Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-3365-3636 Fax: +61-7-3365-4999 INTERNET: clary@csee.uq.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 19 15:27:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AB6517F53 for ; Tue, 19 Oct 1999 15:27:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA31399; Tue, 19 Oct 1999 15:26:28 -0700 Date: Tue, 19 Oct 1999 15:26:28 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gary Palmer Cc: Tom , Joao Pagaime , scsi@FreeBSD.ORG Subject: Re: FreeBSD 3.2 / Slow SCSI Dell PowerEdge 4300 In-Reply-To: <71632.940363753@noop.colo.erols.net> 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 And it's on my list to write a driver for it... actually, this is likely not an SES but a SAF-TE device... On Tue, 19 Oct 1999, Gary Palmer wrote: > Tom wrote in message ID > : > > > pass2 at ahc0 bus 0 target 6 lun 0 > > > pass2: Fixed Processor SCSI-2 device > > > pass2: 3.300MB/s transfers > > > > That isn't a backplane. That looks like some kind of special SCSI > > device on your chain. Perhaps it is a backplane status reporting device > > of some sort. But it is not the backplane itself. > > Its probably the environmental monitoring device (voltage levels, etc) > that Dell provide. I bet Solaris would report it as a SES (SCSI > Environmental Services) device. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" 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 Tue Oct 19 22:43:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id C52B71ACE8; Tue, 19 Oct 1999 22:43:18 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id HAA16808; Wed, 20 Oct 1999 07:42:52 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id HAA13557; Wed, 20 Oct 1999 07:42:51 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199910192224.IAA12877@s5.elec.uq.edu.au> References: <199910192224.IAA12877@s5.elec.uq.edu.au> Date: Wed, 20 Oct 1999 00:38:30 -0400 To: Clary Harridge , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: Brad Knowles Subject: Re: RAID V driver for DPT SCSI host adapter Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:24 AM +1000 1999/10/20, Clary Harridge wrote: > I have been told by Susan Handley at DPT Tech Support > "that you can obtain a copy of our beta driver via the FreeBSD User >News Group." > > Does anyone know where the driver can be obtained ? This might be true (they were originally shooting for a 15 Oct release date), but I was supposed to get a copy of the drivers and a loaner card to benchmark about a month before release. Since I haven't seen or heard hide nor hair of this, I would be rather doubtful that the drivers have actually been released. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 20 7: 1:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from post2.fast.net (post2.fast.net [198.69.204.22]) by hub.freebsd.org (Postfix) with ESMTP id CD2671B92E for ; Wed, 20 Oct 1999 07:01:44 -0700 (PDT) (envelope-from Michael.Sinz@sinz.org) Received: from vixen.sinz.org (maxtnt09-abe-1.fast.net [209.92.14.1]) by post2.fast.net (8.9.1/8.8.5) with ESMTP id KAA07255; Wed, 20 Oct 1999 10:01:37 -0400 (EDT) Received: from Shepard (shepard.sinz.org [192.168.1.2]) by vixen.sinz.org (8.9.3/8.9.3/Sinz.org) with SMTP id KAA25925; Wed, 20 Oct 1999 10:01:32 -0400 Message-Id: <199910201401.KAA25925@vixen.sinz.org> From: "Michael Sinz" To: "Geoff Buckingham" , "Gerard Roudier" Cc: "Mike Sinz" , "Randell Jesup" , "scsi@FreeBSD.ORG" Date: Wed, 20 Oct 1999 10:01:46 -0400 Reply-To: "Michael Sinz" X-Mailer: Sinz.ORG MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 3.2 / Slow SCSI Dell PowerEdge 4300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 16 Oct 1999 16:00:33 +0200 (MET DST), Gerard Roudier wrote: >On Sat, 16 Oct 1999, Geoff Buckingham wrote: > >> On Fri, Oct 15, 1999 at 07:14:15PM +0000, Randell Jesup wrote: >> > Looking at the bonnie results from 10398: >> > >> > write cache enabled >> > -------Sequential Output-------- ---Sequential Input-- --Random-- >> > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >> > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >> > Number of Tags >> > NO 100 7222 89.2 6801 21.8 2347 8.5 7330 93.3 7368 14.6 226.5 4.7 >> > 2 100 7263 90.3 6357 20.3 2730 9.9 7025 90.5 7321 14.9 209.4 4.6 >> > 3 100 7115 88.1 6406 20.8 2289 8.9 7307 93.9 7335 15.0 212.6 4.5 [...] >> >> Having brough bonnie into this I must offer some words of caution. >> >> Bonnie only has three seekers for the random seek test, which is potentialy >> very different from a heavily loaded qmail/exim/apache box. Most server operators who run large FreeBSD (or other) servers also have multiple spindles. While single large 50gig drives seem nice (and are rather fast for a single drive) actual drive performance is well below the bus bandwidth of quality SCSI or FibreChannel devices. Tags and deselection are very important and related concepts. On systems that really get the disks hit a lot, you spread the areas out over multiple spindles (each of which may or may not be a RAID) and thus the mail queue, http server, and pop server may well be on different spindles. This lets the I/O of one device complete while another is still seeking. Command tagging is much the same only it lets the SCSI device do this. If the SCSI device happens to be a multi-drive storage array, this may again provide larger benefits than a single drive. In fact, on multi-drive solutions, overall time may be significantly faster with tag/deselect operations even though single operations in such environments would be a bit slower (more overhead) >Indeed. As I noted in some other posting, it seems there is some subtle >side effect when tags are disabled that makes multithreaded IO-streams >replaced by a succession of single-threaded IO-streams that may last >seconds. Just thinking to disk IOs sorting + reading ahead at the same >time let guess the reasons. > >I also suggest to measure _interactivity_. No need to be overall faster if >a user that download a large file, for example, can take precedence over >another user that download a small file due to the IO scheduling policy >performing mostly batching instead of multi-threaded IOs. Interactivity is a difficult thing to actually measure. It is a "feel" to the system. Sometimes the "feel" can be very fast and yet the actual performance be rather poor. Interactivity is most important when users are directly noticing the effects. On servers this is many times less so since there are a number of things that come between the user and the server. (The client program tends to be the most important in providing the interactivity "feel") In general, one does not want to hold off a process for very long. Thus a single large I/O by another process should not cause your process to have to wait until that I/O completes. One of the tricks is to never do very large I/O operations in a single block. Another is to have the I/O subsystem multi-threaded. (There is a limit to this since with a single disk drive you only have a single head and thus can only do a single operation at any given instance) However, breaking up I/O operations into smaller operations will increase overhead... >> Most machines nowdays have a lot of RAM so large testfiles need to be used >> to minimise cacheing effects (I have allways used -s 1024 but this takes >> some time :-) This is partially a testing issue but it also brings up the point of how much I/O performance has an impact on observed system performance. This depends very much on the working set of data that is being processed. Data that is the same over and over again (such as simple static web pages or CGI scripts on a web server) will generally end up in the cache. It is when you get cache misses that you end up really hitting the I/O performance limits. Given the right (or wrong) set of parameters as far as cache size, working set, and users, you can either make things worse by adding a bit of I/O overhead in order to improve overall I/O performance. If it turns out that the I/O *happens* to behave in a single-threaded way, adding tags will just add overhead and no benefit. If the I/O does not work out single threaded and the I/O subsystem does not multi-thread you can get into lower responsiveness and even lower performance. IMHO: For a general purpose server, one must assume that the special case of the I/O working out to be single threaded will not happen. Multiple things will be going on and the working set will be larger than the cache size. A bit of overhead added to the "simple" cases will make the general operation better. Benchmarks, however, may well show this as slower since some extra overhead had to be added. Benchmarks would need to become much more complex in order to show the real benefit or lack of benefit for any one technique. -- Michael Sinz -- Director of Research & Development, NextBus Inc. mailto:michael.sinz@nextbus.com --------- http://www.nextbus.com My place on the web ---> http://www.users.fast.net/~michael_sinz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 21 14:26: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id 5950514FA9; Thu, 21 Oct 1999 14:26:02 -0700 (PDT) (envelope-from ssamalin@ionet.net) Received: from ionet.net (sam.ops.best.com [205.149.163.53]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id OAA02282; Thu, 21 Oct 1999 14:22:35 -0700 (PDT) Message-ID: <380F840F.66FAADF3@ionet.net> Date: Thu, 21 Oct 1999 17:22:23 -0400 From: Sam Samalin X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, "freebsd-hackers@Freebsd.org" Subject: Barcode reader on a scsi tape changer Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anybody hear of this one? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 21 14:32:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 4C22B14FD0; Thu, 21 Oct 1999 14:32:34 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id QAA97277; Thu, 21 Oct 1999 16:32:02 -0500 (CDT) (envelope-from dan) Date: Thu, 21 Oct 1999 16:32:01 -0500 From: Dan Nelson To: Sam Samalin Cc: freebsd-scsi@FreeBSD.ORG, "freebsd-hackers@Freebsd.org" Subject: Re: Barcode reader on a scsi tape changer Message-ID: <19991021163201.A96845@dan.emsphone.com> References: <380F840F.66FAADF3@ionet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <380F840F.66FAADF3@ionet.net>; from ssamalin@ionet.net on Thu, Oct 21, 1999 at 05:22:23PM -0400 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Oct 21), Sam Samalin said: > Barcode reader on a scsi tape changer. > Anybody hear of this one? Overland Data's ( http://www.ovrland.com ) LibraryExpress line have a barcode option. And it works really well, too. I printed out some labels using Word and a free 3of9 font and it scanned them in just fine. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 21 14:36:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 29C5914FF6; Thu, 21 Oct 1999 14:36:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA11794; Thu, 21 Oct 1999 14:36:02 -0700 Date: Thu, 21 Oct 1999 14:36:01 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Samalin Cc: freebsd-scsi@FreeBSD.ORG, "freebsd-hackers@Freebsd.org" Subject: Re: Barcode reader on a scsi tape changer In-Reply-To: <380F840F.66FAADF3@ionet.net> 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 of course. that is volume tags On Thu, 21 Oct 1999, Sam Samalin wrote: > Anybody hear of this one? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" 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 Thu Oct 21 14:57:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id 88C5E14C95; Thu, 21 Oct 1999 14:57:28 -0700 (PDT) (envelope-from ssamalin@ionet.net) Received: from ionet.net (sam.ops.best.com [205.149.163.53]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id OAA01662; Thu, 21 Oct 1999 14:51:59 -0700 (PDT) Message-ID: <380F8AF2.11003DF5@ionet.net> Date: Thu, 21 Oct 1999 17:51:46 -0400 From: Sam Samalin X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-hackers@Freebsd.org" , "freebsd-scsi@freebsd.org" Subject: 3.3 Driver for Qualstar TLS 4000 tape changer? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I need this driver because the standard one lacks barcode support. Either wise I'll have to port the hack of the 2.2.8 driver. Any one know of one? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 21 15: 1: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EE5914C95; Thu, 21 Oct 1999 15:01:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA11978; Thu, 21 Oct 1999 15:01:01 -0700 Date: Thu, 21 Oct 1999 15:00:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Samalin Cc: "freebsd-hackers@Freebsd.org" , "freebsd-scsi@freebsd.org" Subject: Re: 3.3 Driver for Qualstar TLS 4000 tape changer? In-Reply-To: <380F8AF2.11003DF5@ionet.net> 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 is nonsense. See the chio man page. Primary volume tag is barcode. On Thu, 21 Oct 1999, Sam Samalin wrote: > I need this driver because the standard one lacks barcode support. > Either wise I'll have to port the hack of the 2.2.8 driver. Any one > know of one? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" 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 Thu Oct 21 15: 3:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id 079B514E01; Thu, 21 Oct 1999 15:03:44 -0700 (PDT) (envelope-from ssamalin@ionet.net) Received: from ionet.net (sam.ops.best.com [205.149.163.53]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id OAA28789; Thu, 21 Oct 1999 14:58:09 -0700 (PDT) Message-ID: <380F8C64.FC7A303F@ionet.net> Date: Thu, 21 Oct 1999 17:57:56 -0400 From: Sam Samalin X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-hackers@Freebsd.org" , "freebsd-scsi@freebsd.org" Subject: volume tag does barcodes? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The volume tags of the ch driver and chio works on a scsi tape changer (Qualstar TLS 4000) reads barcodes? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 23 10: 8: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from alpha.mynet.dhs.org (cr612197-a.wlfdle1.on.wave.home.com [24.112.74.34]) by hub.freebsd.org (Postfix) with ESMTP id BDE1614BF4; Sat, 23 Oct 1999 10:07:50 -0700 (PDT) (envelope-from cybermac@tuna.egate.net) Received: from localhost (cybermac@localhost) by alpha.mynet.dhs.org (8.9.2/8.9.3) with ESMTP id NAA06832; Sat, 23 Oct 1999 13:14:01 -0400 (EDT) Date: Sat, 23 Oct 1999 13:14:01 -0400 (EDT) From: CyberMac X-Sender: cybermac@alpha.mynet.dhs.org To: freebsd-scsi@freebsd.org Cc: freebsd-questions@freebsd.org Subject: DPT SmartRAID V ready yet? 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 Hi all! I noticed that FreeBSD has support for DPT SmartRAID III and IV, and is still in the process of making SmartRAID V + I2O drivers available for this great OS. However, is there any other way to make SmartRAID V working under FreeBSD 3.3-Release (e.g. use the current available Linux driver etc..)? If there is, can someone please give me some hints or URLs for such workaround? I'm keeping my fingers crossed... Great thanks! Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message