From owner-freebsd-scsi Sun Aug 15 13:48:34 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 722D814D11 for ; Sun, 15 Aug 1999 13:48:31 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id OAA47448; Sun, 15 Aug 1999 14:35:08 -0600 (MDT) Date: Sun, 15 Aug 1999 14:35:08 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199908152035.OAA47448@narnia.plutotech.com> To: Keith Mitchell Cc: scsi@FreeBSD.org Subject: Re: CAM (driver devel) question X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19990811201425.A89846@weenix.guru.org> <199908120100.TAA51068@panzer.kdm.org> <19990811223315.A93634@weenix.guru.org> 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 <19990811223315.A93634@weenix.guru.org> you wrote: > On Wed, Aug 11, 1999 at 07:00:44PM -0600, Kenneth D. Merry wrote: >> Not all of the drivers support S/G. And you're right, it isn't used in any >> of the upper level code at the moment. > > All of the drivers I looked at (aic7xxx, dpt, buslogic) all supported > scatter/gather. But it looked like they only supported scatter/gather if > they were passed a scatter/gather buffer from the upper layer (and since it > doesn't look like the upper layer sends down a scatter gather list then > I am guessing that scatter/gather never occurs). > > It looks like from the drivers they take whatever buffer they get passed > from the upper layer and pass it down to the card (if its a physical address > or maps it into DMAable memory via bus_dmamap_load() if its a virtual > address). So my initial conclusion was the drivers were architected so > that when the upper layer supported S/G they would too without modification. > but I wanted to be sure before I coded everything. When you perform a bus_dmamap_load(), you are returned a 'generic' S/G list corresponding to the virtual buffer address/size provided. The list conforms to all of the constraints listed in the DMA tag for the map. This is how 99.9% of all S/G will occur for your driver. Some applications may require operations on discontiguous chunks of 'bus addressed' buffers. In this case, the application will provide an S/G list that needs no further interpretation by the driver. I would not expect users of FreeBSD as a 'standard UNIX' to ever exercise this API, but it certainly has many uses in embedded environments. As for your other question about transaction descriptors that are DMA'ed to the card, these are usually handled by allocating DMA safe memory up front. Most of the drivers do this already. At some point in the future, we will likely add some additional calls to the bus dma API that allow you to explicitly sync DMA safe memory after you touch it. For most architectures this would be a no-op, but for those architectures that don't have bus snooping, these calls would flush the data cache. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 15 13:49: 5 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 68BA614D11 for ; Sun, 15 Aug 1999 13:49:01 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id OAA47456; Sun, 15 Aug 1999 14:37:08 -0600 (MDT) Date: Sun, 15 Aug 1999 14:37:08 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199908152037.OAA47456@narnia.plutotech.com> To: Cc: scsi@FreeBSD.org Subject: Re: Adaptec AIC-7896 flakyness X-Newsgroups: pluto.freebsd.scsi 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: > > I'm trying to get 3 IBM 9.1GB LVD SCSI drives to work with a new install > using an Adaptec AIC-7896 (imbedded on an Intel L440GX+ motherboard). The > ONLY way I got all 3 drives working was the following: There is a bug in the auto-termination logic for the Ultra2 cards in the driver. I have a fix and will be committing it later today. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 15 19:30:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id E0D8E14DEB for ; Sun, 15 Aug 1999 19:30:08 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 11568 invoked by uid 1825); 16 Aug 1999 02:30:27 -0000 Date: Sun, 15 Aug 1999 22:30:27 -0400 (EDT) From: up@3.am X-Sender: up@richard2.pil.net Reply-To: up@3.am To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Adaptec AIC-7896 flakyness In-Reply-To: <199908152037.OAA47456@narnia.plutotech.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 Sun, 15 Aug 1999, Justin T. Gibbs wrote: > In article you wrote: > > > > I'm trying to get 3 IBM 9.1GB LVD SCSI drives to work with a new install > > using an Adaptec AIC-7896 (imbedded on an Intel L440GX+ motherboard). The > > ONLY way I got all 3 drives working was the following: > > There is a bug in the auto-termination logic for the Ultra2 cards in > the driver. I have a fix and will be committing it later today. Actually, it was just as two other kind souls (Darryl and Chuck --thanks!) noted...the IBM LVD drives have no termination. I got a 68 pin SCSI 3 terminator, and everything's hunky-dory now. Now...if you could let me know what, if anything is being done for a driver for the Adaptec ARO-1130 RAIDport add-on card, I'm all ears. :) James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 15 19:36: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 767C1153AC for ; Sun, 15 Aug 1999 19:36:00 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id UAA03928; Sun, 15 Aug 1999 20:36:36 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199908160236.UAA03928@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: up@3.am Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Adaptec AIC-7896 flakyness In-reply-to: Your message of "Sun, 15 Aug 1999 22:30:27 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Aug 1999 20:36:36 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> There is a bug in the auto-termination logic for the Ultra2 cards in >> the driver. I have a fix and will be committing it later today. > >Actually, it was just as two other kind souls (Darryl and Chuck --thanks!) >noted...the IBM LVD drives have no termination. I got a 68 pin SCSI 3 >terminator, and everything's hunky-dory now. > >Now...if you could let me know what, if anything is being done for a >driver for the Adaptec ARO-1130 RAIDport add-on card, I'm all ears. :) Not much. I haven't been able to get the necessary documentation for RAID support from Adaptec. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 16 6:55:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 39BEC14CED for ; Mon, 16 Aug 1999 06:55:38 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 3968 invoked by uid 1825); 16 Aug 1999 13:55:44 -0000 Date: Mon, 16 Aug 1999 09:55:44 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Adaptec RAID support WAS Re: Adaptec AIC-7896 flakyness In-Reply-To: <199908160236.UAA03928@caspian.plutotech.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 Sun, 15 Aug 1999, Justin T. Gibbs wrote: > >Now...if you could let me know what, if anything is being done for a > >driver for the Adaptec ARO-1130 RAIDport add-on card, I'm all ears. :) > > Not much. I haven't been able to get the necessary documentation for > RAID support from Adaptec. hmmm...I just noticed that there's a kld for SCO Unix compatibility. Adaptec ships a driver for SCO Unix and SCO Unixware (why, I have no idea). I have a feeling that there'd be a chicken and egg problemtrying to load a kld before the kernel is even running though. I grep'd the LINT kernel source for any mention of SCO and saw nothing. Is this a track even worth pursuing? James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 16 9:25:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 415D3150B6 for ; Mon, 16 Aug 1999 09:25:56 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id KAA04804; Mon, 16 Aug 1999 10:25:28 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199908161625.KAA04804@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: up@3.am Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Adaptec RAID support WAS Re: Adaptec AIC-7896 flakyness In-reply-to: Your message of "Mon, 16 Aug 1999 09:55:44 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Aug 1999 10:25:28 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It would be quite difficult to get SCO kernel module compatibility to work. -- Justin >On Sun, 15 Aug 1999, Justin T. Gibbs wrote: > >> >Now...if you could let me know what, if anything is being done for a >> >driver for the Adaptec ARO-1130 RAIDport add-on card, I'm all ears. :) >> >> Not much. I haven't been able to get the necessary documentation for >> RAID support from Adaptec. > >hmmm...I just noticed that there's a kld for SCO Unix compatibility. >Adaptec ships a driver for SCO Unix and SCO Unixware (why, I have no >idea). I have a feeling that there'd be a chicken and egg problemtrying >to load a kld before the kernel is even running though. I grep'd the >LINT kernel source for any mention of SCO and saw nothing. > >Is this a track even worth pursuing? > >James Smallacombe PlantageNet, Inc. CEO and Janitor >up@3.am http://3.am >========================================================================= >ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans >3 days of clues, news, and views from the industry's best and brightest. > Visit for information and registration. >========================================================================= > > -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 16 23:26:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from portal.vegasunderwater.com (portal.vegasunderwater.com [207.138.238.78]) by hub.freebsd.org (Postfix) with ESMTP id 3FF4514D67 for ; Mon, 16 Aug 1999 23:26:32 -0700 (PDT) (envelope-from todd@portal.vegasunderwater.com) Received: (from todd@localhost) by portal.vegasunderwater.com (8.9.3/8.9.3) id XAA21615 for freebsd-scsi@freebsd.org; Mon, 16 Aug 1999 23:25:26 -0700 (MST) (envelope-from todd) Date: Mon, 16 Aug 1999 23:25:26 -0700 (MST) From: todd Message-Id: <199908170625.XAA21615@portal.vegasunderwater.com> To: freebsd-scsi@freebsd.org Subject: Compaq 3200 Smart Raid Controller support. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having a problem with large files. Mainly any large tar files. tar ends with the following error gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF on archive file tar: child returned status 1 I think I am getting errors with the ida driver on my system. Here is my configuration Compaq 3000 w/dual-pII450 and 1gig of memory. Compaq 3200 Smart Raid controller. 3 10k rpm 18gb hard drives configured as a raid 5. I have upgraded the os and kernel to freebsd 3.2-STABLE as it has support for the raid array. I did this via a full make world. Any ideas on a solution or a recomendation for a more supported raid controller would be very appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 17 4:10:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f296.hotmail.com [207.82.251.187]) by hub.freebsd.org (Postfix) with SMTP id E3D6614F62 for ; Tue, 17 Aug 1999 04:10:30 -0700 (PDT) (envelope-from mut3x@hotmail.com) Received: (qmail 89449 invoked by uid 0); 17 Aug 1999 11:10:03 -0000 Message-ID: <19990817111003.89448.qmail@hotmail.com> Received: from 24.1.228.88 by www.hotmail.com with HTTP; Tue, 17 Aug 1999 04:10:03 PDT X-Originating-IP: [24.1.228.88] From: "Mutex Records USA" To: freebsd-scsi@freebsd.org Subject: dpt scsi smartraid iv controller, in raid 5 mode... ? Date: Tue, 17 Aug 1999 04:10:03 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have read conflicting reports of dpt raid iv controllers, running in a raid 5 configuration - some people say they work well, others have alluded to a hardware bug that dpt admits to - while other people have said that dpt support doesn't know about the raid iv drivers. also there is rumor of support for the raid v card 'soon'. this all leaves my poor insomniac brain feeling mightily confused, can anyone give me the straight poop. please? this is for a 3.2-release system. please excuse the hotmail acct :/ thanks adam _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 17 5:23:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mtiwmhc03.worldnet.att.net (mtiwmhc03.worldnet.att.net [204.127.131.38]) by hub.freebsd.org (Postfix) with ESMTP id 4335B155C2 for ; Tue, 17 Aug 1999 05:23:19 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp ([12.77.131.176]) by mtiwmhc03.worldnet.att.net (InterMail v03.02.07.07 118-134) with ESMTP id <19990817122106.BLZA5700@earth.fxp>; Tue, 17 Aug 1999 12:21:06 +0000 Date: Tue, 17 Aug 1999 08:21:05 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: todd Cc: freebsd-scsi@freebsd.org Subject: Re: Compaq 3200 Smart Raid Controller support. In-Reply-To: <199908170625.XAA21615@portal.vegasunderwater.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 Mon, 16 Aug 1999, todd wrote: > > I am having a problem with large files. Mainly any large tar files. tar > ends with the following error > > gzip: stdin: invalid compressed data--format violated > tar: Unexpected EOF on archive file > tar: child returned status 1 > Please define "large files"; IIRC, the tar (1.11.2) that comes standard has a problem with files > 2GB... > > I think I am getting errors with the ida driver on my system. Here is my configuration > An error log of some sort, along with the output of dmesg may help point to hardware or software problems. Regards, Chris ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 17 16:25:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 75E7C15727 for ; Tue, 17 Aug 1999 16:24:56 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA14080; Wed, 18 Aug 1999 08:55:10 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA14126; Wed, 18 Aug 1999 08:55:09 +0930 (CST) Date: Wed, 18 Aug 1999 08:55:08 +0930 From: Greg Lehey To: Mutex Records USA Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: dpt scsi smartraid iv controller, in raid 5 mode... ? Message-ID: <19990818085508.N7187@freebie.lemis.com> References: <19990817111003.89448.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990817111003.89448.qmail@hotmail.com>; from Mutex Records USA on Tue, Aug 17, 1999 at 04:10:03AM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 17 August 1999 at 4:10:03 -0700, Mutex Records USA wrote: > i have read conflicting reports of dpt raid iv controllers, running in a > raid 5 configuration - some people say they work well, others have alluded > to a hardware bug that dpt admits to - I haven't heard of any bugs. I have heard suggestions that the RAID-5 performance is even worse than RAID-5 has to be, but I don't have much in the way of evidence. > while other people have said that dpt support doesn't know about the > raid iv drivers. I suppose that depends on who you get at DPT support. > also there is rumor of support for the raid v card 'soon'. Yes. There is a rumour. > please excuse the hotmail acct :/ I will. My mail system won't :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 18 1:26:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 82814156B3 for ; Wed, 18 Aug 1999 01:26:47 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (207-172-237-61.s315.tnt13.lnh.md.dialup.rcn.com [207.172.237.61]) by tasam.com (8.9.3/8.9.3) with SMTP id EAA25092 for ; Wed, 18 Aug 1999 04:25:19 -0400 (EDT) (envelope-from clash@tasam.com) Message-ID: <007401bee953$197c0c70$0286860a@tasam.com> From: "Joe Gleason" To: Subject: Defect Lists + camcontrol commands Date: Wed, 18 Aug 1999 04:23:14 -0400 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please excuse my ignorance on the topic of scsi stuff, but I would like to avoid learning the hard way. ;-) I ran: camcontrol defects da0 -f phys -G and the result was "Got 0 defects." Then I run: camcontrol defects da0 -f phys -P and the result was "Got 428 defects:" (I left out the list of defects because it is probably not important) It is my understanding that this is completely normal, because the -G shows that there are no new defects and the 428 defects that are there were there when the drive was in the factory. It this correct? Is this a normal number of defects? On a slightly diffrent tangent: I am aware that it is possible to pass commands to scsi devices for certain cool things. I have a command (thanks to Kenneth Merry a while ago) that shows me the current drive temp from it's internal probes: camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" Is there anywhere I can find a list of such command strings and what they do? (other than the ones in the camcontrol man page) Are they generally vendor specific? Joe Gleason Tasam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 18 8:52: 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 E765514CCA; Wed, 18 Aug 1999 08:51:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA29888; Wed, 18 Aug 1999 08:51:36 -0700 Date: Wed, 18 Aug 1999 08:51:35 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Christopher Masto , Soren Schmidt , Vince Vielhaber , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Onstream? In-Reply-To: <199908180613.AAA16101@harmony.village.org> 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 Oh- to give my status for the SCSI version: I lost time because the day and ahlf I had allocated to actually work on this got blown away by -current instabilities. I'll try and get another shot at it Sunday (*my* work schedule is such that right now that I don't have an employer I can stick this work for.....) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 18 9:51:57 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 F153214F0E for ; Wed, 18 Aug 1999 09:51:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA20599; Wed, 18 Aug 1999 10:51:03 -0600 (MDT) (envelope-from ken) Message-Id: <199908181651.KAA20599@panzer.kdm.org> Subject: Re: Defect Lists + camcontrol commands In-Reply-To: <007401bee953$197c0c70$0286860a@tasam.com> from Joe Gleason at "Aug 18, 1999 04:23:14 am" To: clash@tasam.com (Joe Gleason) Date: Wed, 18 Aug 1999 10:51:03 -0600 (MDT) Cc: freebsd-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 Joe Gleason wrote... > Please excuse my ignorance on the topic of scsi stuff, but I would like to > avoid learning the hard way. ;-) > > I ran: > camcontrol defects da0 -f phys -G > and the result was "Got 0 defects." > > Then I run: > camcontrol defects da0 -f phys -P > and the result was "Got 428 defects:" > (I left out the list of defects because it is probably not important) > > It is my understanding that this is completely normal, because the -G shows > that there are no new defects and the 428 defects that are there were there > when the drive was in the factory. It this correct? Right. > Is this a normal number of defects? It depends on how big your disk is. The best way to find out is to take a survey of a bunch of disks of the same size. Find out the average number of defects, and then you'll have a better idea of whether that's a lot of defects. Presumably the factory quality control processes will spit out a disk with too many defects, although you can't presume too much there. In general, you should be more concerned about increasing numbers of defects on the grown defect list. > On a slightly diffrent tangent: > > I am aware that it is possible to pass commands to scsi devices for certain > cool things. I have a command (thanks to Kenneth Merry a while ago) that > shows me the current drive temp from it's internal probes: > > camcontrol cmd -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1" > > Is there anywhere I can find a list of such command strings and what they > do? (other than the ones in the camcontrol man page) > Are they generally vendor specific? The temperature byte in the log page on IBM disks is vendor specific. I don't know of another drive vendor that sticks readable temperature sensors on their drives. Most things aren't vendor specific, though. To figure out what you can do with a disk, you have to look through the drive manuals or the SCSI specs: http://www.t10.org/ Quantum and Seagate post drive manuals on their web sites for most all of their disks. That's very handy thing sometimes. IBM, on the other hand, does not put SCSI manuals for most of their disks on their web site. You have to get them from a distributor, which is a pain. They do post manuals for their discontinued models, but that's not as useful. 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 Wed Aug 18 10:36:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 7E34515142 for ; Wed, 18 Aug 1999 10:36:32 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 3371 invoked by uid 1001); 18 Aug 1999 17:36:57 +0000 (GMT) To: freebsd-scsi@freebsd.org Subject: camcontrol reset 0:3:0 hangs systems From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 18 Aug 1999 19:36:56 +0200 Message-ID: <3369.934997816@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org System: FreeBSD 3.2-STABLE as of 17. august, 2xPII-450, Adaptec SCSI controller: ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs and 4 IBM disks: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) A "camcontrol reset 0" works fine, "Reset of bus 0 was successful". A "camcontrol reset 0:3:0" (trying to reset da2) reliably hangs the system (no response from the command, everything hangs). Error messages on console: (xpt0:ahc0:0:3:0): Bus Device Reset Message Sent ahc0: Bus Device Reset on A:3. 1 SCBs aborted. The hang occurs whether the system runs a uniprocessor or an SMP kernel, and it doesn't matter which disk is attempted reset either. The kernel responds to Ctrl-Alt-Esc, but the DDB backtrace doesn't seem to be very helpful: Debugger(c0244008) at Debugger+0x37 scgetc(c0277e0c,2,0,c0277e0c,0) at scgetc+0x7ec sckbdevent(c0277e0c,0,0,0,c8c82360) at sckbdevent+0x58 atkbd_intr(c0277e0c,0,0,0,c0210a8e) at atkbd_intr+0x1f atkbd_isa_intr(0,80000000,10,c0210010,0) at atkbd_isa_intr+0x28 Xresume1() at Xresume1+0x2b --- interrupt, eip = 0xc021bd71, esp = 0xc024f42c, ebp = 0 --- default_halt() at default_halt+0x1 Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #0: Wed Aug 18 19:05:05 CEST 1999 sthaug@celery.nethelp.no:/mnt2/src/sys/compile/CELERY_UP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258359296 (252304K bytes) Preloaded elf kernel "kernel" at 0xc02c6000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 fxp0: rev 0x05 int a irq 12 on pci0.10.0 fxp0: Ethernet address 00:90:27:2f:d2:5f fxp1: rev 0x05 int a irq 10 on pci0.11.0 fxp1: Ethernet address 00:90:27:2f:d2:60 ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x7a int a irq 11 on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 3 seconds for SCSI devices to settle changing root device to da0s1a da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 18 13:30:56 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 2B5D214F13 for ; Wed, 18 Aug 1999 13:30:49 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA22119; Wed, 18 Aug 1999 14:28:51 -0600 (MDT) (envelope-from ken) Message-Id: <199908182028.OAA22119@panzer.kdm.org> Subject: Re: camcontrol reset 0:3:0 hangs systems In-Reply-To: <3369.934997816@verdi.nethelp.no> from "sthaug@nethelp.no" at "Aug 18, 1999 07:36:56 pm" To: sthaug@nethelp.no Date: Wed, 18 Aug 1999 14:28:51 -0600 (MDT) Cc: freebsd-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 sthaug@nethelp.no wrote... > System: FreeBSD 3.2-STABLE as of 17. august, 2xPII-450, Adaptec SCSI > controller: > > ahc0: rev 0x00 int a irq 11 on pci0.12.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > > and 4 IBM disks: > [ ... ] > A "camcontrol reset 0" works fine, "Reset of bus 0 was successful". > > A "camcontrol reset 0:3:0" (trying to reset da2) reliably hangs the > system (no response from the command, everything hangs). Error messages > on console: > > (xpt0:ahc0:0:3:0): Bus Device Reset Message Sent > ahc0: Bus Device Reset on A:3. 1 SCBs aborted. > > The hang occurs whether the system runs a uniprocessor or an SMP kernel, > and it doesn't matter which disk is attempted reset either. [ ... ] That's a known problem. I think I know how to fix it, but I haven't had a chance to do so yet. Hopefully I'll get to it before the end of the month. 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 Wed Aug 18 20:53:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6EC4D150A0 for ; Wed, 18 Aug 1999 20:53:24 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-151.dialup.HiWAAY.net [216.180.14.151]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA23407; Wed, 18 Aug 1999 22:50:23 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id WAA76137; Wed, 18 Aug 1999 22:17:12 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908190317.WAA76137@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: clash@tasam.com (Joe Gleason), freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Defect Lists + camcontrol commands In-reply-to: Message from "Kenneth D. Merry" of "Wed, 18 Aug 1999 10:51:03 MDT." <199908181651.KAA20599@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Aug 1999 22:17:12 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > > Is this a normal number of defects? > > It depends on how big your disk is. The best way to find out is to take a > survey of a bunch of disks of the same size. Find out the average number > of defects, and then you'll have a better idea of whether that's a lot of > defects. > > Presumably the factory quality control processes will spit out a disk with > too many defects, although you can't presume too much there. At my prior employment, I kept track of such things for every HD we had. I disagree with Kenneth's statement that the number of bad blocks varies with the size of the HD. It seemed to me that in early production of a particular size such as 4.3G 3.5" drives, the bad block rate was higher than the same model 6 months or a year later. New 4G HD's of a different model would also retain a low count factory bad block list. But then out would come 9G 3.5" disks and the bad block list grew again in early production, and fell on new drives 6 to 12 months later. For most any HD, 200 factory bad blocks was low. Nearly 1000 was not common, but not unheard of. Most all drives we had were Seagate. Then again there is always an exception. We had a 1G Conner HD that insisted it had no factory bad blocks. I don't believe it partly because when put to the test it grew 7. And partly because it was a crappy drive. > In general, you should be more concerned about increasing numbers of > defects on the grown defect list. Agreed. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 18 23:39:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mw5.texas.net (mw5.texas.net [206.127.30.15]) by hub.freebsd.org (Postfix) with ESMTP id ACA19150E8 for ; Wed, 18 Aug 1999 23:39:53 -0700 (PDT) (envelope-from rsnow@lgc.com) Received: from basil.dympna.COM (mnet06-69.sat.texas.net [209.99.48.237]) by mw5.texas.net (2.4/2.4) with ESMTP id BAA06244 for ; Thu, 19 Aug 1999 01:39:19 -0500 (CDT) Received: from lgc.com (IDENT:rsnow@turbo [134.132.228.6]) by basil.dympna.COM (8.9.3/8.8.7) with ESMTP id BAA17491 for ; Thu, 19 Aug 1999 01:39:25 -0500 (CDT) (envelope-from rsnow@lgc.com) Message-ID: <37BBA678.A43895DA@lgc.com> Date: Thu, 19 Aug 1999 01:38:48 -0500 From: Rob Snow X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.10-mosix i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Exabyte 8505XL and 3.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running a 3.2 box with a 8505 on a 2940 and seem to have a problem getting the device to function properly. It is probed properly and it appears that things are going to go well: SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) and then if I try to use it: (sa0:ahc0:0:4:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 (sa0:ahc0:0:4:0): NOT READY asc:3a,0 (sa0:ahc0:0:4:0): Medium not present (sa0:ahc0:0:4:0): REWIND. CDB: 1 0 0 0 0 0 (sa0:ahc0:0:4:0): NOT READY asc:3a,0 (sa0:ahc0:0:4:0): Medium not present It seems to work for a second, however, the lights go out and it eject the tape. I thought it was a bunk tape and tried others, including a cleaning tape. No go. I should add that I've attempted to set density via mt from my previous script: /usr/bin/mt -f /dev/rsa0 density 0x8C The device has worked for a couple of years and I don't believe that it has died. I could be wrong, however, I seem to have read that othes are having a very similar problem with some 8200's. 3.2 RELEASE 2x200MHz PPro 128MB RAM ahc0 is a 2940 and ahc1 is a 2940UW. The Micropolis on the same controller works fine (I'm sure it'll follow its company to the grave soon...) I've seen some recent traffic on the subject and was wondering if there was a) resolution b) additonal debugging need to get it working. (I _need_ a backup) -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 19 3:51:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from zabagek.ihf.rwth-aachen.de (zabagek.ihf.RWTH-Aachen.DE [134.130.90.60]) by hub.freebsd.org (Postfix) with ESMTP id F16C2150E8 for ; Thu, 19 Aug 1999 03:51:18 -0700 (PDT) (envelope-from tg@zabagek.ihf.rwth-aachen.de) Received: (from tg@localhost) by zabagek.ihf.rwth-aachen.de (8.9.3/8.9.3) id MAA56650; Thu, 19 Aug 1999 12:49:29 +0200 (CEST) (envelope-from tg) To: freebsd-scsi@freebsd.org Subject: Problem with AHA-1542CF on -stable From: Thomas Gellekum Date: 19 Aug 1999 12:49:29 +0200 Message-ID: Lines: 79 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Moin, I have a curious problem with my 1542CF. When I'm using rev 1.19.2.4 of /sys/dev/aha.c, the disks hanging from it are probed fine, but the machine hangs when it tries to mount the filesystems in /etc/rc with the following output: (da2::aha0:0:2:0): CCB 0xc246c508 - timeout aha0: ahadone - Attempt to free non-active ACCB 0xc246c564 (da2::aha0:0:2:0): CCB 0xc246c508 - timeout (da2::aha0:0:2:0): CCB 0xc246c508 - timeout aha0: aha_cmd: Timeout waiting for adapter idle ahainitmboxes: Initialization command failed aha0: no longer in timeout I can only power-toggle the machine at this point; if I only hit the reset button the controller won't find the last disk. I could get a traceback from DDB, but that will have to wait until this evening. Now for the "curious" part: when I'm using rev. 1.19.2.2 of aha.c the controller hangs at the probe stage (see below for dmesg output), but recovers after a minute or so. The system works fine afterwards. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #14: Wed Aug 18 19:19:00 CEST 1999 root@fenchurch:/usr/src/sys/compile/FENCHURCH Timecounter "i8254" frequency 1193182 Hz CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) avail memory = 14393344 (14056K bytes) Preloaded elf kernel "kernel.works" at 0xc0233000. Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0: AHA-1542CF FW Rev. F.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle aha0: ahafetchtransinfo - Inquire Setup Info Failed (probe0:aha0:0:0:0): CCB 0xc246b450 - timed out (probe0:aha0:0:0:0): CCB 0xc246b450 - timed out aha0: No longer in timeout changing root device to da0s1a da0 at aha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 522MB (1070496 512 byte sectors: 64H 32S/T 522C) da1 at aha0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: 1034MB (2118144 512 byte sectors: 64H 32S/T 1034C) da2 at aha0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) WARNING: / was not properly dismounted A termination problem or failing disk seems unlikely, I think. I tried another 1542CF, but got the same behaviour. Any ideas? tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 19 8:40:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dptnotes.dpt.com (dptnotes.dpt.com [206.138.241.6]) by hub.freebsd.org (Postfix) with SMTP id 1E09B150B0 for ; Thu, 19 Aug 1999 08:40:15 -0700 (PDT) (envelope-from salyzyn_mark@dpt.com) Received: from bohica.dpt.com ([198.242.63.84]) by dptnotes.dpt.com (Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) with SMTP id 852567D2.0056180C; Thu, 19 Aug 1999 11:40:22 -0400 Received: by bohica.dpt.com [198.242.63.84] (NX5.67g/NX3.0M) id AA17493; Thu, 19 Aug 1999 11:39:38 -0400 Reply-To: Mark Salyzyn Message-Id: <199908191539.AA17493@bohica.dpt.com> Mime-Version: 1.0 (NeXT Mail 4.2mach v148) Content-Type: text/enriched; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Mark Salyzyn Date: Thu, 19 Aug 1999 11:39:37 -0400 To: Subject: Re: dpt scsi smartraid iv controller, in raid 5 mode... ? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <<19990818085508.N7187@freebie.lemis.com>, you wrote: >I haven't heard of any bugs. I have heard suggestions that the RAID-5 >performance is even worse than RAID-5 has to be, but I don't have much >in the way of evidence. It will depend on the mix of FW you are using, cache and drives. DPT's RAID-5 performance typically exceeds what is expected (IMHO) due to our use of the cache on the controller, but can also suck for something as subtle as a bogus stripe size selection. >> while other people have said that dpt support doesn't know about the >> raid iv drivers. >I suppose that depends on who you get at DPT support. Since the IV generation driver was written by Simon Shapiro, DPT support (and DPT engineering) are at somewhat of a disadvantage. This is changing as they come up to speed. LINUX ran into a similar issues with Michael Neuffer effectively becoming a volunteer DPT support person instead of DPT providing the support. >> also there is rumor of support for the raid v card 'soon'. >Yes. There is a rumour. No rumor, I released the driver to any who would ask for it on August 3 and announced it here and in freebsd-hardware. Currently, only Mirapoint has taken to testing the driver. The driver provides passthrough, so we have a working native command line based configuration tool (dptutil). An engineer is working on porting the storage manager to the X11/LessTIF environment. This driver is a SCSI based driver. Simon Shapiro is working on a higher performance Monolithic driver which should be out real soon. >> please excuse the hotmail acct :/ >I will. My mail system won't :-) I get grumpy when I see email from earthlink, considering their gross indecency back in the Cantor and Siegel days and the ensuing spam ;-/. But I learned many years ago that it doesn't matter which country, or internet service, you are on, they are all people deserving of respect! ;-> Sincerely -- Mark Salyzyn ObjDisclaimer: I know nothing, and what I say does not represent DPT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 19 8:54:44 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 AF6B215A05 for ; Thu, 19 Aug 1999 08:53:57 -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 RAA10303; Thu, 19 Aug 1999 17:34:06 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id MAA60432; Thu, 19 Aug 1999 12:19:31 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908191019.MAA60432@yedi.iaf.nl> Subject: Re: Defect Lists + camcontrol commands In-Reply-To: <199908190317.WAA76137@nospam.hiwaay.net> from David Kelly at "Aug 18, 1999 10:17:12 pm" To: dkelly@HiWAAY.net (David Kelly) Date: Thu, 19 Aug 1999 12:19:31 +0200 (CEST) Cc: ken@kdm.org, clash@tasam.com, 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 David Kelly wrote ... > "Kenneth D. Merry" writes: > > > Is this a normal number of defects? > > ... > Then again there is always an exception. We had a 1G Conner HD that > insisted it had no factory bad blocks. I don't believe it partly because > when put to the test it grew 7. And partly because it was a crappy > drive. There is nothing that stops a manufacturer from remapping bad blocks 'below the surface' and presenting the drive as having no factory bad blocks. Maybe that is what happened to your Conner. -- | / 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 Thu Aug 19 11:24:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id C6E3914C18 for ; Thu, 19 Aug 1999 11:24:38 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA16401; Thu, 19 Aug 1999 14:24:19 -0400 (EDT) Message-ID: <19990819142419.A15358@netmonger.net> Date: Thu, 19 Aug 1999 14:24:19 -0400 From: Christopher Masto To: Mark Salyzyn , freebsd-scsi@FreeBSD.ORG Subject: Re: dpt scsi smartraid iv controller, in raid 5 mode... ? Mail-Followup-To: Mark Salyzyn , freebsd-scsi@FreeBSD.ORG References: <199908191539.AA17493@bohica.dpt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199908191539.AA17493@bohica.dpt.com>; from Mark Salyzyn on Thu, Aug 19, 1999 at 11:39:37AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Aug 19, 1999 at 11:39:37AM -0400, Mark Salyzyn wrote: > >> also there is rumor of support for the raid v card 'soon'. > >Yes. There is a rumour. > > No rumor, I released the driver to any who would ask for it on > August 3 and announced it here and in freebsd-hardware. Currently, > only Mirapoint has taken to testing the driver. It sounds maybe like DPT is the kind of company that listens to customer feedback, so I'll mention this in case you have an opportunity to pass it on. The reason I haven't gone with the V stuff is because we need to be able to run an up-to-date version of FreeBSD (that means 3.x-STABLE right now). IIRC the driver that came out was for the dead 2.2 branch. We're buying two big (Pentium III, 256MB RAM, 4 x 9GB) machines this afternoon, and they're going to end up with Adaptec 3950U2Bs in them because the DPT stuff we have drivers for is too expensive. I prefer DPT, and hopefully for the next machine there will be CAM support for the newer cards. I'm not complaining, just providing a real-world example where a port to 3.x would have helped. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Thu Aug 19 11:49:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 6658A1514D for ; Thu, 19 Aug 1999 11:49:38 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from boomer (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id OAA14920 for ; Thu, 19 Aug 1999 14:47:47 -0400 (EDT) Message-Id: <4.2.0.58.19990819144627.00a71670@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 19 Aug 1999 14:46:53 -0400 To: freebsd-scsi@freebsd.org From: Forrest Aldrich Subject: SCSI boot order (multiple host adapters) control Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an ASUS motherboard which has an integrated Adaptec SCSI controller. I just installed an adaptec 2940, and the system insists on trying to boot from the external case that's attached to the 2940. I read through the LINT file for the kernel config and tried using: controller scbus0 ahc0 controller scbus1 ahc1 ... and some variations of that, but no go. It's not clear to me if the BIOS is to blame or not... I tried looking through the SCSI Select Setup and the system BIOS, but did not see anything that would change this behavior. What am I missing here? Thanks -F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 19 12:13: 8 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 7452014E5C for ; Thu, 19 Aug 1999 12:13:04 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA31671; Thu, 19 Aug 1999 13:13:01 -0600 (MDT) (envelope-from ken) Message-Id: <199908191913.NAA31671@panzer.kdm.org> Subject: Re: SCSI boot order (multiple host adapters) control In-Reply-To: <4.2.0.58.19990819144627.00a71670@216.67.12.69> from Forrest Aldrich at "Aug 19, 1999 02:46:53 pm" To: forrie@forrie.com (Forrest Aldrich) Date: Thu, 19 Aug 1999 13:13:01 -0600 (MDT) Cc: freebsd-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 Forrest Aldrich wrote... > I have an ASUS motherboard which has an integrated Adaptec SCSI controller. > > I just installed an adaptec 2940, and the system insists on trying to boot from the > external case that's attached to the 2940. I read through the LINT file for the > kernel config and tried using: > > controller scbus0 ahc0 > controller scbus1 ahc1 > > ... and some variations of that, but no go. > > It's not clear to me if the BIOS is to blame or not... I tried looking through the > SCSI Select Setup and the system BIOS, but did not see anything that would > change this behavior. > > What am I missing here? You haven't mentioned whether you're running -current or -stable or what. There are some bugs in the probe order in -current when you have multiple PCI busses. But, in general, what you're missing is that the system will probably boot with the first bootable device on the first it finds. Normally you could "fix" this by swapping controllers around, but since one of them is on the motherboard, you can't do that. You should probably hardwire things in your kernel config file, like you were trying to do: controller ahc0 controller ahc1 controller scbus0 at ahc1 controller scbus1 at ahc0 That should swap your SCSI busses around and make the system boot off the internal controller, assuming it pops up as ahc1. You can also hardwire disks, like this: device da0 at scbus0 target 0 unit 0 device da1 at scbus1 target 5 unit 0 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 Thu Aug 19 12:35:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f178.hotmail.com [207.82.251.64]) by hub.freebsd.org (Postfix) with SMTP id 4F82C14E32 for ; Thu, 19 Aug 1999 12:35:27 -0700 (PDT) (envelope-from mut3x@hotmail.com) Received: (qmail 42246 invoked by uid 0); 19 Aug 1999 19:34:27 -0000 Message-ID: <19990819193427.42245.qmail@hotmail.com> Received: from 24.1.228.88 by www.hotmail.com with HTTP; Thu, 19 Aug 1999 12:34:27 PDT X-Originating-IP: [24.1.228.88] From: "Mutex Records USA" To: freebsd-scsi@freebsd.org Subject: Re: dpt scsi smartraid iv controller, in raid 5 mode... ? Date: Thu, 19 Aug 1999 12:34:27 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990818085508.N7187@freebie.lemis.com>, you wrote: >>I haven't heard of any bugs. I have heard suggestions that the RAID-5 >>performance is even worse than RAID-5 has to be, but I don't have much in >>the way of evidence. >It will depend on the mix of FW you are using, cache and drives. DPT's >RAID-5 performance typically exceeds what is expected (IMHO) due to our use >of the cache on the controller, but can also suck for >something as subtle >as a bogus stripe size selection. not sure exactly what you mean, there...? >>while other people have said that dpt support doesn't know about the raid >>iv drivers. >I> suppose that depends on who you get at DPT support. >Since the IV generation driver was written by Simon Shapiro, DPT support >(and DPT engineering) are at somewhat of a disadvantage. This is changing >as they come up to speed. LINUX ran into a similar issues with Michael >Neuffer effectively becoming a volunteer DPT support person instead of DPT >providing the support. >>>also there is rumor of support for the raid v card 'soon'. >>Yes. There is a rumour. >No rumor, I released the driver to any who would ask for it on August 3 and >announced it here and in freebsd-hardware. Currently, only >Mirapoint has >taken to testing the driver. so, the driver is not ready for production use? i need to buy a raid controller this week... up until now my only real option was the dpt smartraid iv. note, this is for a (for the next month and a half or 2) testbed nfs server i am setting up, using 3.2-release. how stable is the driver, at this point? i would like to see it, if you wouldn't mind sending it my way via email. >The driver provides passthrough, so we have a working native command line >based configuration tool (dptutil). An engineer is working on >porting the >storage manager to the X11/LessTIF environment. This >driver is a SCSI >based driver. nice. >Simon Shapiro is working on a higher performance Monolithic driver which >should be out real soon. for the V i assume? >>>please excuse the hotmail acct :/ >>I will. My mail system won't :-) >I get grumpy when I see email from earthlink, considering their gross >indecency back in the Cantor and Siegel days and the ensuing spam ;-/. someone stuck me on the phone once with someone who wanted a technical reviewer for a new book... turned out to be siegel. (this was for a book after the original green-card-spam-thingy) Needless to say, I turned it down.... >But I learned many years ago that it doesn't matter which country, or >internet service, you are on, they are all people deserving of respect! except aolusers :) thanks adam _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 20 12:34:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E6AE2155B3 for ; Fri, 20 Aug 1999 12:33:57 -0700 (PDT) (envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA00457 for freebsd-scsi@freebsd.org; Fri, 20 Aug 1999 21:33:46 +0200 (CEST) (envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m11HsaQ-000WyUC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Fri, 20 Aug 1999 19:36:18 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: tape: can't set blocksize on Wangtek Date: 20 Aug 1999 19:38:41 +0200 Message-ID: <7pk3r1$89o$1@bigeye.rhein-neckar.de> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 4.0-CURRENT from a few days ago, QIC-1000 tape drive: sa0: Removable Sequential Access SCSI-CCS device Inserting a QIC-150 tape, and $ mt blocksize 512 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST csi:10,8,0,0 I've also had similar problems in other contexts, both with SA_QUIRK_FIXED and SA_QUIRK_VARIABLE: "unable to set fixed blocksize to 1024", "unable to set variable blocksize". It seems the drive refuses any command to change the blocksize from the hardcoded quirk entry in scsi_sa.c. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 20 15:34:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 3903815245 for ; Fri, 20 Aug 1999 15:34:42 -0700 (PDT) (envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA14373 for freebsd-scsi@freebsd.org; Sat, 21 Aug 1999 00:33:51 +0200 (CEST) (envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m11HuqG-000WyUC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Fri, 20 Aug 1999 22:00:48 +0200 (CEST) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Bizarre effect reading old tape Date: 20 Aug 1999 22:03:10 +0200 Message-ID: <7pkc9u$btm$1@bigeye.rhein-neckar.de> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been trying to read an old QIC-150 tape of mine. It was written either on the Wangtek 51000 drive I use now or on an earlier Wangtek 5525ES, I forgot. Under Linux. I have no idea what size blocks etc. are on the tape. I use the unmodified quirk entry from CURRENT, i.e. fixed/1024. After a "tar tv" stopped after the first couple of files, I transferred the whole archive from tape to disk with "dd bs=20b". The result was enlightening. There were 5k of data, followed by 5k of null bytes, followed by 5k of data, and so on. I repeated the tape->disk transfer with "dd bs=10b", resulting in 2.5k data, 2.5k nulls, 2.5k data, ... Tried again with "dd bs=1k", and sure enough, now there were 512-byte chunks of data interspersed with equally-sized chunks of null bytes. Removing the interleaved null blocks produces an uncorrupted archive. I assume that this, er, unexpected behavior is somehow connected to QIC-150 using 512-byte blocks. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 20 16:30:59 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 7EE8C14E81 for ; Fri, 20 Aug 1999 16:30:55 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA05520; Fri, 20 Aug 1999 16:30:51 -0700 Date: Fri, 20 Aug 1999 16:30:49 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bizarre effect reading old tape In-Reply-To: <7pkc9u$btm$1@bigeye.rhein-neckar.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 You didn't say what drive you are reading it on. My guess is that if you're reading this on a 51000 that it is adding in the nulls, but I could be wrong. On 20 Aug 1999, Christian Weisgerber wrote: > I've been trying to read an old QIC-150 tape of mine. It was written > either on the Wangtek 51000 drive I use now or on an earlier Wangtek > 5525ES, I forgot. Under Linux. I have no idea what size blocks etc. > are on the tape. I use the unmodified quirk entry from CURRENT, > i.e. fixed/1024. > > After a "tar tv" stopped after the first couple of files, I transferred > the whole archive from tape to disk with "dd bs=20b". The result was > enlightening. There were 5k of data, followed by 5k of null bytes, > followed by 5k of data, and so on. I repeated the tape->disk transfer > with "dd bs=10b", resulting in 2.5k data, 2.5k nulls, 2.5k data, ... > Tried again with "dd bs=1k", and sure enough, now there were 512-byte > chunks of data interspersed with equally-sized chunks of null bytes. > Removing the interleaved null blocks produces an uncorrupted archive. > > I assume that this, er, unexpected behavior is somehow connected > to QIC-150 using 512-byte blocks. > > -- > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > > > > 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 Sat Aug 21 7:24:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from db.geocrawler.com (db.gotocity.com [165.90.140.10]) by hub.freebsd.org (Postfix) with ESMTP id AD047151BF for ; Sat, 21 Aug 1999 07:24:08 -0700 (PDT) (envelope-from nobody@db.geocrawler.com) Received: (from nobody@localhost) by db.geocrawler.com (8.8.8/8.8.8) id JAA17659; Sat, 21 Aug 1999 09:21:52 -0500 Date: Sat, 21 Aug 1999 09:21:52 -0500 Message-Id: <199908211421.JAA17659@db.geocrawler.com> To: freebsd-scsi@freebsd.org Subject: SCSI 53C876 poor? From: "Geocrawler.com" Reply-To: "Martin Dvorak" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message was sent from Geocrawler.com by "Martin Dvorak" Be sure to reply to that address. Hi all, I've got a question regarding performance of SMP FreeBSD system. I've got an Intel N440BX machine with two 400Mhz Pentium II processors and dual Symbios SCSI controller (53C876) running FreeBSD 3.2-RELEASE. The machine is serving as an Internet server (not workstation). I had RedHat installed on this machine, but because of machine purpose, stability and inclination to FreeBSD, I recently moved to FreeBSD. Immediately after the installation of FreeBSD I noticed that the system is much more slower than it was with RedHat. So I tried to optimize the kernel, I tried to play with different configuration parameters etc. but nothing... While on RedHat I was copying large files in speed around 20MB/sec, now I am glad if I get to 5MB/sec. Also, untarring 1.5 MB file takes about 40sec which is not what anyone could expect mentioned hardware. Is there something I could do to speed up the system? I can send my kernel config file if anyone is so kind to give me some advice. Or is it because of slow SMP implementation in FreeBSD? Or are the SCSI drivers for SymBIOS 53C876 controller so much slower the RedHats' (I tried it with or without CAM, both were the same). Thanks very much for any advice or opinion. Martin Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 9:16:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 371F114EBD for ; Sat, 21 Aug 1999 09:16:44 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id CAA28462; Sun, 22 Aug 1999 02:13:12 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma028456; Sun, 22 Aug 99 02:12:42 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id CAA15542 for ; Sun, 22 Aug 1999 02:12:42 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id CAA29270 for ; Sun, 22 Aug 1999 02:12:42 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id CAA10348; Sun, 22 Aug 1999 02:12:41 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908211612.CAA10348@nymph.detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Can I rescue this 2940UW? Date: Sun, 22 Aug 1999 02:12:40 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been given a "dead" 2940UW. In this case "dead" means that someone flashed the wrong bios on it, and it no longer works in Windoze. I've confirmed that Windoze locks solid if this card is present. But... it looks at least half alive. It is seen as a PCI device by the BIOS, it announces itself (claiming to be bios v1.34.3 if that helps), and the ^A setup thingy works. But after that it says "Host Adapter Configuration Error" and doesn't probe any devices or attach its bit of BIOS. FreeBSD 3.2-R recognises the card (aic7880) and probes all the devices. It even gets all the speeds and stuff right. Sadly, it doesn't fully work. When I try to access data I get a panic: sequencer parity error. So, do I have any chance? Would it help to get more precise error messages? By the way, it has a sticker on it: AHA-2940UW/GATEWAY Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 9:23:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from puffer.quadrunner.com (puffer.quadrunner.com [205.166.195.4]) by hub.freebsd.org (Postfix) with ESMTP id 51BA114BDD for ; Sat, 21 Aug 1999 09:23:30 -0700 (PDT) (envelope-from adoane@puffer.quadrunner.com) Received: (from adoane@localhost) by puffer.quadrunner.com (8.9.2/QUAD-2.1) id JAA18898; Sat, 21 Aug 1999 09:21:43 -0700 (PDT) From: Andrew Doane Message-Id: <199908211621.JAA18898@puffer.quadrunner.com> Subject: Re: Can I rescue this 2940UW? In-Reply-To: <199908211612.CAA10348@nymph.detir.qld.gov.au> from Stephen McKay at "Aug 22, 1999 02:12:40 am" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Sat, 21 Aug 1999 09:21:43 -0700 (PDT) Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Mailer: ELM [version 2.4ME+ PL49 (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 > I've been given a "dead" 2940UW. In this case "dead" means that someone > flashed the wrong bios on it, and it no longer works in Windoze. I've > confirmed that Windoze locks solid if this card is present. > > But... it looks at least half alive. It is seen as a PCI device by the > BIOS, it announces itself (claiming to be bios v1.34.3 if that helps), and > the ^A setup thingy works. But after that it says "Host Adapter Configuration > Error" and doesn't probe any devices or attach its bit of BIOS. > > FreeBSD 3.2-R recognises the card (aic7880) and probes all the devices. It > even gets all the speeds and stuff right. Sadly, it doesn't fully work. > > When I try to access data I get a panic: sequencer parity error. > > So, do I have any chance? Would it help to get more precise error messages? > By the way, it has a sticker on it: AHA-2940UW/GATEWAY > > Stephen. Try to flash it with a proper BIOS. If that doesn't work try to send it in for warrenty repair - but you'll have to send it to Gateway, not Adaptec (isn't OEM fun?). -Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 9:35:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 1700114BDD for ; Sat, 21 Aug 1999 09:35:23 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id CAA28744; Sun, 22 Aug 1999 02:32:12 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma028734; Sun, 22 Aug 99 02:31:48 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id CAA16413; Sun, 22 Aug 1999 02:31:48 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id CAA29698; Sun, 22 Aug 1999 02:31:47 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id CAA10552; Sun, 22 Aug 1999 02:31:46 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908211631.CAA10552@nymph.detir.qld.gov.au> To: Andrew Doane Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Can I rescue this 2940UW? References: <199908211621.JAA18898@puffer.quadrunner.com> In-Reply-To: <199908211621.JAA18898@puffer.quadrunner.com> from Andrew Doane at "Sat, 21 Aug 1999 09:21:43 -0700" Date: Sun, 22 Aug 1999 02:31:46 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 21st August 1999, Andrew Doane wrote: >> I've been given a "dead" 2940UW. In this case "dead" means that someone >> flashed the wrong bios on it, and it no longer works in Windoze. I've >> confirmed that Windoze locks solid if this card is present. >> So, do I have any chance? Would it help to get more precise error messages? >> By the way, it has a sticker on it: AHA-2940UW/GATEWAY >Try to flash it with a proper BIOS. I think the original owner got into this mess by trying to flash a "proper" BIOS. That is, I think he just grabbed something from Adaptec and whacked it on. Then he read this note about "don't flash this on an OEM card". >If that doesn't work try to send >it in for warrenty repair - but you'll have to send it to Gateway, >not Adaptec (isn't OEM fun?). I'm willing to try flashing the BIOS again if people who have played with OEM cards recommend it, but I'm not going to be mailing it anywhere. If the original owner couldn't get them to fix it, I can't see how they would do it for me. (It's over 2 years old). And I'd have to use a telephone! Yuck! Since FreeBSD can talk to it a little bit, I was hoping for a driver hack. Maybe if the driver assumed it was a dumb slow card it would work and I could get some use out of it. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 9:35:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 93AA91503E for ; Sat, 21 Aug 1999 09:35:33 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id SAA25643; Sat, 21 Aug 1999 18:33:32 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m11IBPY-000WyPC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sat, 21 Aug 1999 15:42:20 +0200 (CEST) Message-ID: <19990821154220.H16148@mips.rhein-neckar.de> Date: Sat, 21 Aug 1999 15:42:20 +0200 From: Christian Weisgerber To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bizarre effect reading old tape References: <7pkc9u$btm$1@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Matthew Jacob on Fri, Aug 20, 1999 at 04:30:49PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob: > You didn't say what drive you are reading it on. My guess is that if > you're reading this on a 51000 that it is adding in the nulls, but I could > be wrong. Yes, I'm reading it on the 51000. I'm fairly sure that I've previously read that tape on the 51000 under Linux *without* inserted null blocks, so I think it can't be the drive alone. If I always got 512-byte chunks of data and nulls, that would be more plausible. But I always get contiguous data for half the read size. "dd bs=10k" does 10,240-byte reads. "mt stat" confirms that the driver is in 1024-byte fixed blocksize mode. According to sa(4), this should mean that each 10,240-byte read() is converted into a series of ten 1024-byte block reads. So why do I end up with 5,120 bytes of straight data followed bt 5,120 bytes of straight nulls? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 10: 7:25 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 9CF8914F64 for ; Sat, 21 Aug 1999 10:07:19 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA07417; Sat, 21 Aug 1999 10:03:53 -0700 Date: Sat, 21 Aug 1999 10:03:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bizarre effect reading old tape In-Reply-To: <19990821154220.H16148@mips.rhein-neckar.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 Sat, 21 Aug 1999, Christian Weisgerber wrote: > Matthew Jacob: > > > You didn't say what drive you are reading it on. My guess is that if > > you're reading this on a 51000 that it is adding in the nulls, but I could > > be wrong. > > Yes, I'm reading it on the 51000. > I'm fairly sure that I've previously read that tape on the 51000 under > Linux *without* inserted null blocks, so I think it can't be the drive > alone. > > If I always got 512-byte chunks of data and nulls, that would be more > plausible. But I always get contiguous data for half the read size. "dd > bs=10k" does 10,240-byte reads. "mt stat" confirms that the driver is in > 1024-byte fixed blocksize mode. According to sa(4), this should mean > that each 10,240-byte read() is converted into a series of ten 1024-byte > block reads. So why do I end up with 5,120 bytes of straight data > followed bt 5,120 bytes of straight nulls? > Put it in variable mode and see what happens- I suspect that the 'fake' variable that some QIC drives have might be at fault. = -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 15:34: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 5C06E1511B for ; Sat, 21 Aug 1999 15:34:01 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA21524; Sun, 22 Aug 1999 00:33:55 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m11IJFB-000WyPC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 22 Aug 1999 00:04:09 +0200 (CEST) Message-ID: <19990822000408.J16148@mips.rhein-neckar.de> Date: Sun, 22 Aug 1999 00:04:08 +0200 From: Christian Weisgerber To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bizarre effect reading old tape References: <19990821154220.H16148@mips.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Matthew Jacob on Sat, Aug 21, 1999 at 10:03:52AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob: > Put it in variable mode and see what happens- Oh, that's easy: (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST csi:10,8,0,0 (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST csi:10,8,0,0 Which leads us straight to my other problem. I guess I'll need to keep both a fixed and a variable mode kernel handy. And enable CAMDEBUG. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de See another pointless homepage at . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 21 15:38:38 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 DCB8914FEB for ; Sat, 21 Aug 1999 15:38:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA08275; Sat, 21 Aug 1999 15:37:07 -0700 Date: Sat, 21 Aug 1999 15:37:06 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bizarre effect reading old tape In-Reply-To: <19990822000408.J16148@mips.rhein-neckar.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 > Matthew Jacob: > > > Put it in variable mode and see what happens- > > Oh, that's easy: > > (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 > (sa0:ncr0:0:6:0): ILLEGAL REQUEST csi:10,8,0,0 > (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 > (sa0:ncr0:0:6:0): ILLEGAL REQUEST csi:10,8,0,0 I take it this means that an attempt to put it in variable failed? > > Which leads us straight to my other problem. I guess I'll need to keep > both a fixed and a variable mode kernel handy. And enable CAMDEBUG. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message