From owner-freebsd-scsi@FreeBSD.ORG Sun May 9 20:29:01 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4914B16A4CE; Sun, 9 May 2004 20:29:01 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id D09E943D1D; Sun, 9 May 2004 20:29:00 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Sun, 9 May 2004 23:29:00 -0400 Message-ID: From: Don Bowman To: 'Scott Long' , Don Bowman Date: Sun, 9 May 2004 23:28:58 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-scsi@freebsd.org Subject: RE: cvs commit: src/sys/dev/asr asr.c X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 03:29:01 -0000 ... It appears that 1.61 of asr.c breaks the asr raidutils # ln -s asr0 rdptr0 # ls -al rdptr0 lrwxr-xr-x 1 root wheel 4 May 9 23:25 rdptr0 -> asr0 # raidutil -L all Engine connect failed: COMPATILITY number osdIOrequest : File /dev/rdptr17 Could Not Be Opened# # !ls ls -al rdptr0 ls: rdptr0: No such file or directory its removing the link to the driver i've created when i run it? From owner-freebsd-scsi@FreeBSD.ORG Sun May 9 20:54:27 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDCA716A4CE for ; Sun, 9 May 2004 20:54:27 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 752A343D5F for ; Sun, 9 May 2004 20:54:27 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4A3x5u6053003; Sun, 9 May 2004 21:59:06 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <409EFCBB.7080401@freebsd.org> Date: Sun, 09 May 2004 21:53:31 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: cvs commit: src/sys/dev/asr asr.c X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 03:54:28 -0000 Don Bowman wrote: > ... > > It appears that 1.61 of asr.c breaks the asr raidutils > > # ln -s asr0 rdptr0 > # ls -al rdptr0 > lrwxr-xr-x 1 root wheel 4 May 9 23:25 rdptr0 -> asr0 > # raidutil -L all > > Engine connect failed: COMPATILITY number > osdIOrequest : File /dev/rdptr17 Could Not Be Opened# > # !ls > ls -al rdptr0 > ls: rdptr0: No such file or directory > > its removing the link to the driver i've created when > i run it? > What happens if you change ASR_REVISION back to 0 and set ASR_SUBREVISION to 9? Scott From owner-freebsd-scsi@FreeBSD.ORG Mon May 10 11:17:05 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3EA416A4CE for ; Mon, 10 May 2004 11:17:05 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171B843D1D for ; Mon, 10 May 2004 11:17:05 -0700 (PDT) (envelope-from AdilK@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Mon, 10 May 2004 14:17:04 -0400 Message-ID: From: Adil Katchi To: "'freebsd-scsi@freebsd.org'" Date: Mon, 10 May 2004 14:17:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: VMIoctl command timeout X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 18:17:05 -0000 I'm running FreeBSD 4.7 and have an Adaptec SCSI RAID 2200S controller. Whenever I reboot my box, the aac0 device times out after 30 seconds while trying to send a VMIoctl command and I get the following error message on the screen: aacd0: on aac0 aacd0: 419944MB (860045568 sectors) aac0: Error 5 sending VMIoctl command aac0: Error 5 sending VMIoctl command The pciconf for the controller card is as follows: aac0@pci5:2:0: class=0x010400 card=0x02859005 chip=0x02859005 rev=0x01 hdr=0x00 vendor = 'Adaptec' device = 'AAC-RAID RAID Controller' class = mass storage subclass = RAID I am using the SCSI passthrough device, aacp, and so my kernel configuration file has the following in it: device aac # Adaptec FSA RAID, Dell PERC2/PERC3 device aacp # SCSI Passthrough interface (optional, CAM required) As shown above, the RAID configuration is 3 drives on a RAID 5 configuration. The system continues to boot without a problem. I tried upgrading my aac device to the latest RELENG_4 branch without success. Furthermore, I tried upgrading the whole kernel to 4.10, again without success. I looked through the code in sys/dev/aac/aac_cam.c and I traced the problem to a timeout that occurs while doing a AAC_MONKER_SYNCFIB command. I've also contacted Scott Long, the owner of the device driver, but he hasn't been able to reproduce this problem. He's the one who suggested that I upgrade the driver. Can anyone help? Adil From owner-freebsd-scsi@FreeBSD.ORG Mon May 10 16:10:26 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05C4616A4CF for ; Mon, 10 May 2004 16:10:26 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id C450C43D2D for ; Mon, 10 May 2004 16:10:11 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i4ANABBp004518 for ; Mon, 10 May 2004 19:10:11 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i4ANABF7067846 for ; Mon, 10 May 2004 19:10:11 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i4ANABGD067845 for freebsd-scsi@freebsd.org; Mon, 10 May 2004 19:10:11 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200405102310.i4ANABGD067845@himinbjorg.tucs-beachin-obx-house.com> To: freebsd-scsi@freebsd.org Date: Mon, 10 May 2004 19:10:11 -0400 (EDT) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Geometry issues X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 23:10:26 -0000 Hi, Having a SCSI Geometry issue on a 5.2.1-RELEASE-p4 system. It has a Symbios SDMS PCI SCSI, 53C1010-66 adapter that shows up as : sym0: <1010-66> port 0xa000-0xa0ff mem 0xf6000000-0xf6001fff,0xf6800000-0xf68003 ff irq 25 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. And to it I'm connecting an EasyRaid II RAID box. There is LITTLE I can configure on it, basically termination, SCSI ID, and Raid 0/1/0+1/3/5 and thats pretty much it. When the system boots, the splash screen claims the geometry is 1024/255/63 at 40M sync, and 16 wide. In the controller I've used "Alternate CHS Mapping" and "SCSI Plug and Play Mapping" without any differences. When FreeBSD boots, it sees : (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. da0 at sym1 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 1060184MB (2171256832 512 byte sectors: 255H 63S/T 135154C) When I try to /stand/sysinstall it, fdisk pitches a serious fit about it. What can I do to get this configured properly? It seems that if I bring it down to RAID-1+0, it configures up fine (Not sure what the geometry shows as, sorry). Thanks, Tuc/TTSG Internet Services, Inc. From owner-freebsd-scsi@FreeBSD.ORG Tue May 11 13:38:44 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FF6C16A4CE for ; Tue, 11 May 2004 13:38:44 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FB9C43D5E for ; Tue, 11 May 2004 13:38:43 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id A178C3BB1A; Tue, 11 May 2004 22:38:41 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) i4BKbUxU002617 for ; Tue, 11 May 2004 22:37:30 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.11/8.12.11/Submit) id i4BKbULk002616 for freebsd-scsi@freebsd.org; Tue, 11 May 2004 22:37:30 +0200 (CEST) (envelope-from schweikh) Date: Tue, 11 May 2004 22:37:30 +0200 From: Jens Schweikhardt To: freebsd-scsi@freebsd.org Message-ID: <20040511203730.GB2256@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 20:38:44 -0000 hello, world\n I hoped that my new Adaptec 2120S U320 RAID in my new Supermicro P4SCT board with 64bit/66MHz PCI would turn my disk IO into a desktop blitz, but the opposite has happened. While my old ASUS A7N8X with vinum would read 100MB/s from 2 Fujitsu MAP3367 connected to an 29160, I get only 29MB/sec from the stripe built with the 2120S (as measured with dd to /dev/null). What I have done so far: o have reset the 2120S config to factory defaults. o set the transfer speed to U160 and disabled "packetized" because I could not low level format the drives otherwise. Until that point I had a lot of trouble even getting the 2120S to boot its controller kernel. Effect has been seemingly endless (5min) twirling baton. o low level formatted both MAPs, initialized them and then built the stripe with 64kb stripe size. o I have enabled caching in both directions. The dmesg says schweikh@hal9000:~ $ dmesg|grep aac aac0: mem 0xe8000000-0xebffffff irq 9 at device 1.0 on pci3 aac0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xe8000000 aac0: [FAST] aac0: i960RX 100MHz, 48MB cache memory, optional battery present aac0: Kernel 4.0-0, Build 6011, S/N ba12c0 aac0: Supported Options=1f7e aacd0: on aac0 aacd0: 69997MB (143354880 sectors) Any enlightenment on how to improve disk io greatly appreciated. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-scsi@FreeBSD.ORG Tue May 11 14:01:31 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB45A16A4CE for ; Tue, 11 May 2004 14:01:31 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A2743D49 for ; Tue, 11 May 2004 14:01:30 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4BL6Hu6062841; Tue, 11 May 2004 15:06:18 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A13F22.80505@freebsd.org> Date: Tue, 11 May 2004 15:01:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jens Schweikhardt References: <20040511203730.GB2256@schweikhardt.net> In-Reply-To: <20040511203730.GB2256@schweikhardt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 21:01:31 -0000 Jens Schweikhardt wrote: > hello, world\n > > I hoped that my new Adaptec 2120S U320 RAID in my new Supermicro P4SCT > board with 64bit/66MHz PCI would turn my disk IO into a desktop blitz, > but the opposite has happened. While my old ASUS A7N8X with vinum would > read 100MB/s from 2 Fujitsu MAP3367 connected to an 29160, I get only > 29MB/sec from the stripe built with the 2120S (as measured with dd to > /dev/null). > > What I have done so far: > o have reset the 2120S config to factory defaults. > o set the transfer speed to U160 and disabled "packetized" because > I could not low level format the drives otherwise. Until that point > I had a lot of trouble even getting the 2120S to boot its controller > kernel. Effect has been seemingly endless (5min) twirling baton. This means that you have a bad cable and/or poor termination. Backing down to u160 is only going to hurt performance; the 2120 needs every little bit of help that it can get. > o low level formatted both MAPs, initialized them and then built the > stripe with 64kb stripe size. > o I have enabled caching in both directions. Read caching should be turned off unless you have a very specific need for it. Having it on is going to hurt sequential read performance by a 2x factor. The only time is makes sense is when you have a relatively small data set that gets read repeatedly, with few other reads mixed in. > > The dmesg says > schweikh@hal9000:~ $ dmesg|grep aac > aac0: mem 0xe8000000-0xebffffff irq 9 at device 1.0 on pci3 > aac0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xe8000000 > aac0: [FAST] > aac0: i960RX 100MHz, 48MB cache memory, optional battery present > aac0: Kernel 4.0-0, Build 6011, S/N ba12c0 > aac0: Supported Options=1f7e > aacd0: on aac0 > aacd0: 69997MB (143354880 sectors) > > Any enlightenment on how to improve disk io greatly appreciated. > The 2120 is the 'value' card of the family. It has an Intel 80302 instead of an 80303 processor, which means that it's internal i/o thoroughput is cut in half. Add in the 2x hit from having the read cache on, and yes, you will get horribly performance. At the very least you need to fix your cable configuration and turn off the read cache. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 02:37:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97F2316A4CE for ; Wed, 12 May 2004 02:37:42 -0700 (PDT) Received: from acc.nensi.net (acc.nensi.net [193.203.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E5643D54 for ; Wed, 12 May 2004 02:37:39 -0700 (PDT) (envelope-from val@nensi.net) Received: from smtp.nensi.net (smtp.nensi.net [193.203.236.65]) by acc.nensi.net (8.9.3p2/8.9.3) with ESMTP id MAA11941 for ; Wed, 12 May 2004 12:37:34 +0300 (EEST) Date: Wed, 12 May 2004 12:37:34 +0300 (EEST) From: "Valery V. Lunyov" X-X-Sender: admin@acc.nensi.net To: freebsd-scsi@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Zero-Channel RAID Support (Adaptec 2010S) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Valery V. Lunyov" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 09:37:42 -0000 Hi! I want to buy SuperMicro SuperServer 5013C-M8 with onboard SCSI Ultra320 Adaptec 7902 Controller and ZCR Adaptec 2010S, but in 4.9-STABLE only 2000S is supported officially. When support of 2010S will be added in ASR driver? (About testing I read in this mailing list). May I wait this support in 4.9-STABLE? Or only in 5.X? And may I use this hardware solution to run critical applications (such a DNS, Web-hosting, etc). Thanks! --- My Bests! Valery V. Lunyov, UNIX SysAdmin From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 02:49:09 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B132A16A4CF; Wed, 12 May 2004 02:49:09 -0700 (PDT) Received: from mail.errors.firstcallgroup.co.uk (mail.errors.firstcallgroup.co.uk [213.167.69.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CB5E43D39; Wed, 12 May 2004 02:49:09 -0700 (PDT) (envelope-from petefrench@keithprowse.com) Received: from smaug.rattatosk ([172.16.1.8]) by mail.errors.firstcallgroup.co.uk with esmtp (Exim 4.22) id 1BNqMN-000DTw-3g; Wed, 12 May 2004 10:49:07 +0100 Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by smaug.rattatosk with esmtp (Exim 4.22) id 1BNqMM-0000QR-Si; Wed, 12 May 2004 10:49:06 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.30; FreeBSD) id 1BNqMM-0002EO-Ry; Wed, 12 May 2004 10:49:06 +0100 To: schweikh@schweikhardt.net, scottl@freebsd.org In-Reply-To: <40A13F22.80505@freebsd.org> Message-Id: From: Pete French Date: Wed, 12 May 2004 10:49:06 +0100 cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 09:49:09 -0000 > Read caching should be turned off unless you have a very specific need > for it. Having it on is going to hurt sequential read performance by a > 2x factor. The only time is makes sense is when you have a relatively > small data set that gets read repeatedly, with few other reads mixed in. Interesting comment. Does that refer to this particular controller, to caches on RAID controllers in general, or to caches on the drives themselves ? -pete. From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 05:25:28 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D115416A4CE for ; Wed, 12 May 2004 05:25:28 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6669443D45 for ; Wed, 12 May 2004 05:25:28 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CCULu6066795; Wed, 12 May 2004 06:30:21 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A21780.3030604@freebsd.org> Date: Wed, 12 May 2004 06:24:32 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Valery V. Lunyov" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: Zero-Channel RAID Support (Adaptec 2010S) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 12:25:28 -0000 Valery V. Lunyov wrote: > Hi! > > I want to buy SuperMicro SuperServer 5013C-M8 > with onboard SCSI Ultra320 Adaptec 7902 Controller > and ZCR Adaptec 2010S, but in 4.9-STABLE only 2000S > is supported officially. > > When support of 2010S will be added in ASR driver? > (About testing I read in this mailing list). > May I wait this support in 4.9-STABLE? Or only in 5.X? > > And may I use this hardware solution to run critical > applications (such a DNS, Web-hosting, etc). > > > Thanks! > > --- > My Bests! > Valery V. Lunyov, > UNIX SysAdmin FreeBSD 4.9 supports the 2010. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 05:32:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FE8F16A4CE for ; Wed, 12 May 2004 05:32:36 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E694F43D54 for ; Wed, 12 May 2004 05:32:35 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CCbSu6066840; Wed, 12 May 2004 06:37:28 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A2192B.3010201@freebsd.org> Date: Wed, 12 May 2004 06:31:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 12:32:36 -0000 Pete French wrote: >>Read caching should be turned off unless you have a very specific need >>for it. Having it on is going to hurt sequential read performance by a >>2x factor. The only time is makes sense is when you have a relatively >>small data set that gets read repeatedly, with few other reads mixed in. > > > Interesting comment. Does that refer to this particular controller, to > caches on RAID controllers in general, or to caches on the drives themselves ? > > -pete. With the read cache on, every time that the OS requests a new logical block that isn't in the cache, the controller has to first DMA that block from the disks into the cache, then DMA from the cache to host memory. With the read cache off, it only has to DMA from the disks straight to host memory. Some older AAC controllers also don't balance the cache well between read and write, so having both enabled winds up thrashing both. The read cache on the drive is a good thing since it will do a bit of read-ahead which will help reduce latency. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 09:00:43 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B6EB16A4D1 for ; Wed, 12 May 2004 09:00:43 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E03F43D53 for ; Wed, 12 May 2004 09:00:42 -0700 (PDT) (envelope-from freebsd-scsi@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BNw9x-0005xs-00 for ; Wed, 12 May 2004 18:00:41 +0200 Received: from 86.red-213-97-212.pooles.rima-tde.net ([213.97.212.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2004 18:00:41 +0200 Received: from lists-gmane by 86.red-213-97-212.pooles.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2004 18:00:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-scsi@freebsd.org From: Joan Picanyol i Puig Date: Wed, 12 May 2004 17:55:04 +0200 Lines: 22 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 86.red-213-97-212.pooles.rima-tde.net Sender: news Subject: setting WCE on SCSI disks across reboots X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 16:00:43 -0000 Hi, I'm trying to disable the write-cache on these two disks: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 6 lun 0 (pass2,da1) both sitting on an Adaptec 2940 U2W controller ahc0: port 0x1000-0x10ff mem 0xd0020000-0xd0020fff irq 11 at device 14.0 on pci0 I can set WCE to 0 using camcontrol modepage -e -m 0x08, but upon reboot WCE is set to 1 again. AFAIK this can't be set interactively, so I am at a loss as to how to disable the wc forever. Any ideas? tks -- pica From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 09:05:28 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A08D16A4CE for ; Wed, 12 May 2004 09:05:28 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF2943D39 for ; Wed, 12 May 2004 09:05:28 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CGA3u6067729; Wed, 12 May 2004 10:10:03 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A24B2C.2010602@freebsd.org> Date: Wed, 12 May 2004 10:05:00 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joan Picanyol i Puig References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: setting WCE on SCSI disks across reboots X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 16:05:28 -0000 Joan Picanyol i Puig wrote: > Hi, > > I'm trying to disable the write-cache on these two disks: > > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 6 lun 0 (pass2,da1) > > both sitting on an Adaptec 2940 U2W controller > > ahc0: port 0x1000-0x10ff mem > 0xd0020000-0xd0020fff irq 11 at device 14.0 on pci0 > > I can set WCE to 0 using camcontrol modepage -e -m 0x08, but upon reboot > WCE is set to 1 again. AFAIK this can't be set interactively, so I am at a > loss as to how to disable the wc forever. > > Any ideas? > > tks Check the Adaptec BIOS. You probably have WCE set in there. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 09:13:37 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BEF616A4CE for ; Wed, 12 May 2004 09:13:37 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id B772543D5F for ; Wed, 12 May 2004 09:13:31 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i4CGDICd007044; Wed, 12 May 2004 10:13:18 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i4CGDIVs007043; Wed, 12 May 2004 10:13:18 -0600 (MDT) (envelope-from ken) Date: Wed, 12 May 2004 10:13:18 -0600 From: "Kenneth D. Merry" To: Joan Picanyol i Puig Message-ID: <20040512161318.GA7014@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org Subject: Re: setting WCE on SCSI disks across reboots X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 16:13:37 -0000 On Wed, May 12, 2004 at 17:55:04 +0200, Joan Picanyol i Puig wrote: > Hi, > > I'm trying to disable the write-cache on these two disks: > > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 6 lun 0 (pass2,da1) > > both sitting on an Adaptec 2940 U2W controller > > ahc0: port 0x1000-0x10ff mem > 0xd0020000-0xd0020fff irq 11 at device 14.0 on pci0 > > I can set WCE to 0 using camcontrol modepage -e -m 0x08, but upon reboot > WCE is set to 1 again. AFAIK this can't be set interactively, so I am at a > loss as to how to disable the wc forever. > > Any ideas? By default, you're only editing the current parameters. If you specify the saved parameters, hopefully it'll last across reboots. (Add -P 3 to the command you're using above.) Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 10:30:15 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BF2E16A4CE for ; Wed, 12 May 2004 10:30:15 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCFC843D4C for ; Wed, 12 May 2004 10:30:14 -0700 (PDT) (envelope-from freebsd-scsi@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BNxYb-0007R8-00 for ; Wed, 12 May 2004 19:30:13 +0200 Received: from 86.red-213-97-212.pooles.rima-tde.net ([213.97.212.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2004 19:30:13 +0200 Received: from lists-gmane by 86.red-213-97-212.pooles.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 May 2004 19:30:13 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-scsi@freebsd.org From: Joan Picanyol i Puig Date: Wed, 12 May 2004 19:30:22 +0200 Lines: 19 Message-ID: References: <20040512161318.GA7014@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 86.red-213-97-212.pooles.rima-tde.net Sender: news Subject: Re: setting WCE on SCSI disks across reboots X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 17:30:15 -0000 On Wed, 12 May 2004 11:13:18 -0600, Kenneth D. Merry wrote: > On Wed, May 12, 2004 at 17:55:04 +0200, Joan Picanyol i Puig wrote: >> I can set WCE to 0 using camcontrol modepage -e -m 0x08, but upon reboot >> WCE is set to 1 again. AFAIK this can't be set interactively, so I am at a >> loss as to how to disable the wc forever. >> >> Any ideas? > > By default, you're only editing the current parameters. If you specify the > saved parameters, hopefully it'll last across reboots. (Add -P 3 to the > command you're using above.) That did the trick. tks -- pica From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 10:36:17 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7C9F16A4CE; Wed, 12 May 2004 10:36:17 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id D637843D41; Wed, 12 May 2004 10:36:16 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 12 May 2004 13:36:15 -0400 Message-ID: From: Don Bowman To: 'Scott Long' , Pete French Date: Wed, 12 May 2004 13:36:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-scsi@freebsd.org Subject: RE: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 17:36:18 -0000 From: Scott Long [mailto:scottl@freebsd.org] > Pete French wrote: > > >>Read caching should be turned off unless you have a very > specific need > >>for it. Having it on is going to hurt sequential read > performance by a > >>2x factor. The only time is makes sense is when you have a > relatively > >>small data set that gets read repeatedly, with few other > reads mixed in. > > > > > > Interesting comment. Does that refer to this particular > controller, to > > caches on RAID controllers in general, or to caches on the > drives themselves ? > > > > -pete. > > > With the read cache on, every time that the OS requests a new logical > block that isn't in the cache, the controller has to first DMA that > block from the disks into the cache, then DMA from the cache to host > memory. With the read cache off, it only has to DMA from the disks > straight to host memory. Some older AAC controllers also don't > balance the cache well between read and write, so having both enabled > winds up thrashing both. > > The read cache on the drive is a good thing since it will do a bit of > read-ahead which will help reduce latency. Scott, how does one disable the read cache? Its not available in the bios on the AAC (on the 2100). Is there a modepage for this? --don From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 10:48:17 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1763E16A4CE for ; Wed, 12 May 2004 10:48:17 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F73843D54 for ; Wed, 12 May 2004 10:48:16 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CHrAu6068290; Wed, 12 May 2004 11:53:10 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A26356.409@freebsd.org> Date: Wed, 12 May 2004 11:48:06 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 17:48:17 -0000 Don Bowman wrote: > From: Scott Long [mailto:scottl@freebsd.org] > >>Pete French wrote: >> >> >>>>Read caching should be turned off unless you have a very >> >>specific need >> >>>>for it. Having it on is going to hurt sequential read >> >>performance by a >> >>>>2x factor. The only time is makes sense is when you have a >> >>relatively >> >>>>small data set that gets read repeatedly, with few other >> >>reads mixed in. >> >>> >>>Interesting comment. Does that refer to this particular >> >>controller, to >> >>>caches on RAID controllers in general, or to caches on the >> >>drives themselves ? >> >>>-pete. >> >> >>With the read cache on, every time that the OS requests a new logical >>block that isn't in the cache, the controller has to first DMA that >>block from the disks into the cache, then DMA from the cache to host >>memory. With the read cache off, it only has to DMA from the disks >>straight to host memory. Some older AAC controllers also don't >>balance the cache well between read and write, so having both enabled >>winds up thrashing both. >> >>The read cache on the drive is a good thing since it will do a bit of >>read-ahead which will help reduce latency. > > > Scott, how does one disable the read cache? Its not available > in the bios on the AAC (on the 2100). Is there a modepage for this? > > --don I can't remember how the 2100 BIOS works, I'll have to take a look. I thought that it was an attribute that was set when the array is created. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 11:33:24 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D59716A4CE for ; Wed, 12 May 2004 11:33:24 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0B7B43D1D for ; Wed, 12 May 2004 11:33:23 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 12 May 2004 14:33:22 -0400 Message-ID: From: Don Bowman To: "'scsi@freebsd.org'" Date: Wed, 12 May 2004 14:33:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: Intel SRCU42X raid support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 18:33:24 -0000 Does anyone know if the intel SRCU42X works with FreeBSD? Does the iir driver support it? http://www.intel.com/design/servers/SRCU42X/ It seems like a pretty good product from the specs. The iir driver man page indicates it supports Intel RAID Controller SRCMR Intel Server RAID Controller U3-l (SRCU31a) Intel Server RAID Controller U3-1L (SRCU31La) Intel Server RAID Controller U3-2 (SRCU32) All past and future releases of Intel and ICP RAID Controllers. That last is a bold statement :) From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 11:33:43 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68BE516A4CE; Wed, 12 May 2004 11:33:43 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4539143D1D; Wed, 12 May 2004 11:33:42 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 3A1F03BBBA; Wed, 12 May 2004 20:33:41 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) i4CIWVa4003326; Wed, 12 May 2004 20:32:31 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost)i4CIWV9N003325; Wed, 12 May 2004 20:32:31 +0200 (CEST) (envelope-from schweikh) Date: Wed, 12 May 2004 20:32:31 +0200 From: Jens Schweikhardt To: Scott Long Message-ID: <20040512183231.GB3137@schweikhardt.net> References: <40A26356.409@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40A26356.409@freebsd.org> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 18:33:43 -0000 On Wed, May 12, 2004 at 11:48:06AM -0600, Scott Long wrote: ... # I can't remember how the 2100 BIOS works, I'll have to take a look. # I thought that it was an attribute that was set when the array is # created. Yes, and once its set at array creation time it apparently can not be changed. I deleted the array and created it anew to disable read caching. This did not yield any perfomance gain by itself. After I changed the cables I now have 79MB/s (formerly only 29MB/s, a single disk has a sustained read speed of 71MB/s at the outer sectors). Next thing will be going back from forced U160 mode to U320. I'll report the results, so watch this space :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 11:37:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F2316A4CE; Wed, 12 May 2004 11:37:36 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 944F243D4C; Wed, 12 May 2004 11:37:35 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 12 May 2004 14:37:32 -0400 Message-ID: From: Don Bowman To: 'Jens Schweikhardt' , Scott Long Date: Wed, 12 May 2004 14:37:31 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: freebsd-scsi@freebsd.org Subject: RE: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 18:37:36 -0000 From: Jens Schweikhardt [mailto:schweikh@schweikhardt.net] > > On Wed, May 12, 2004 at 11:48:06AM -0600, Scott Long wrote: > ... > # I can't remember how the 2100 BIOS works, I'll have to take a look. > # I thought that it was an attribute that was set when the array is > # created. > > Yes, and once its set at array creation time it apparently can not be > changed. I deleted the array and created it anew to disable read > caching. This did not yield any perfomance gain by itself. After I > changed the cables I now have 79MB/s (formerly only 29MB/s, a single > disk has a sustained read speed of 71MB/s at the outer sectors). Next > thing will be going back from forced U160 mode to U320. I'll > report the > results, so watch this space :-) > With aaccli, one can see the values of the cache: AAC0> container show cache 0 Executing: container show cache 0 Global Container Read Cache Size : 0 Global Container Write Cache Size : 16203776 Read Cache Setting : DISABLE Write Cache Setting : ENABLE ALWAYS Write Cache Status : Active, not protected, battery not present and set it: AAC0> ? container set cache Executing: container set cache help container set cache - Sets caching parameters for a container. Useful only if a native operating system's file system resides on the container. FORMAT - container set cache {container} /read_cache_enable - If you set this switch to TRUE, the command enables the read cache for the specified container. /unprotected - Specifies whether to set the container's write cache to disable, enable when protected, or enable always. You use this switch in conjunction with the /unprotected switch to accomplish the desired setting. See the CLI Reference Guide for more information. /write_cache_enable - Specifies whether to set the container's write cache to disable, enable when protected, or enable always. You use this switch in conjunction with the /unprotected switch to accomplish the desired setting. See the CLI Reference Guide for more information. From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 11:40:56 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C93816A4CE for ; Wed, 12 May 2004 11:40:56 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D7AD43D70 for ; Wed, 12 May 2004 11:40:55 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CIjnu6068573; Wed, 12 May 2004 12:45:50 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A26F7E.3060203@freebsd.org> Date: Wed, 12 May 2004 12:39:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'scsi@freebsd.org'" Subject: Re: Intel SRCU42X raid support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 18:40:56 -0000 Don Bowman wrote: > Does anyone know if the intel SRCU42X > works with FreeBSD? Does the iir driver support > it? > > http://www.intel.com/design/servers/SRCU42X/ > > It seems like a pretty good product from the > specs. > > The iir driver man page indicates it supports > > Intel RAID Controller SRCMR > Intel Server RAID Controller U3-l (SRCU31a) > Intel Server RAID Controller U3-1L (SRCU31La) > Intel Server RAID Controller U3-2 (SRCU32) > All past and future releases of Intel and ICP RAID Controllers. > > That last is a bold statement :) > I'll ask the iir folks. If not, it might be interesting to write a driver for it. Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 12:05:39 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 117A616A4CE; Wed, 12 May 2004 12:05:39 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E9D643D46; Wed, 12 May 2004 12:05:38 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 56E803BBB2; Wed, 12 May 2004 21:05:37 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) i4CJ4Te3001372; Wed, 12 May 2004 21:04:29 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost)i4CJ4TVQ001371; Wed, 12 May 2004 21:04:29 +0200 (CEST) (envelope-from schweikh) Date: Wed, 12 May 2004 21:04:29 +0200 From: Jens Schweikhardt To: Scott Long Message-ID: <20040512190429.GA1315@schweikhardt.net> References: <40A26356.409@freebsd.org> <20040512183231.GB3137@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040512183231.GB3137@schweikhardt.net> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 19:05:39 -0000 On Wed, May 12, 2004 at 08:32:31PM +0200, Jens Schweikhardt wrote: # On Wed, May 12, 2004 at 11:48:06AM -0600, Scott Long wrote: # ... # # I can't remember how the 2100 BIOS works, I'll have to take a look. # # I thought that it was an attribute that was set when the array is # # created. # # Yes, and once its set at array creation time it apparently can not be # changed. I deleted the array and created it anew to disable read # caching. This did not yield any perfomance gain by itself. After I # changed the cables I now have 79MB/s (formerly only 29MB/s, a single # disk has a sustained read speed of 71MB/s at the outer sectors). Next # thing will be going back from forced U160 mode to U320. I'll report the # results, so watch this space :-) Went back to U320 and enabled packetized--even with the Adaptec cable that came with the controller no joy :-( At first, dd reported 83MB/s but after skipping the first 1G the controller(?) made a high pitched beep, and this was in dmesg aac0: **Monitor** SCSI bus reset issued on channel 0 aac0: **Monitor** <...repeats 2 more times> aac0: **Monitor** Drive 0:14:0 online on container 0: aac0: **Monitor** Drive 0:15:0 online on container 0: aac0: **Monitor** SCSI bus reset issued on channel 0 aac0: **Monitor** <...repeats 1 more times> aac0: **Monitor** Drive 0:14:0 online on container 0: aac0: **Monitor** Drive 0:15:0 online on container 0: aac0: **Monitor** SCSI bus reset issued on channel 0 aac0: **Monitor** Drive 0:15:0 returning error aac0: **Monitor** ID(0:15:0) - Cmd[0x28] failed (retries exhausted) aac0: **Monitor** Alarm Adapter Event -- turning Alarm On! aac0: **Monitor** Container 0 returning error on drive 0:15:0 aacd0: hard error cmd=read 2551359-2551486 aacd0: hard error cmd=read 5013567-5013694 ... aacd0: hard error cmd=read 35094591-35094718 aacd0: hard error cmd=read 35094719-35094846 aacd0: hard error cmd=read 35094591-35094718 aacd0: hard error cmd=read 35094719-35094846 aacd0: hard error cmd=read 37601343-37601470 aacd0: hard error cmd=read 37601471-37601598 aacd0: hard error cmd=read 37601343-37601470 aacd0: hard error cmd=read 37601471-37601598 aacd0: hard error cmd=read 37601343-37601470 aacd0: hard error cmd=read 37601471-37601598 aac0: **Monitor** ID(0:15:0) - Cmd[0x2a] failed (retries exhausted) aac0: **Monitor** Last Adapter Alarm Event -- Alarm turning off! Error probing container 0 aacd0: detached aac0: **Monitor** Drive 0:14:0 online Hmm. Should I still go for another U320 cable? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 12:08:49 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBA0716A4CE for ; Wed, 12 May 2004 12:08:49 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 092EC43D5D for ; Wed, 12 May 2004 12:08:49 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (g4.samsco.home [192.168.0.12]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4CJDhu6068728; Wed, 12 May 2004 13:13:43 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A27607.9040801@freebsd.org> Date: Wed, 12 May 2004 13:07:51 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20040214 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jens Schweikhardt References: <40A26356.409@freebsd.org> <20040512183231.GB3137@schweikhardt.net> <20040512190429.GA1315@schweikhardt.net> In-Reply-To: <20040512190429.GA1315@schweikhardt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 19:08:50 -0000 Jens Schweikhardt wrote: > On Wed, May 12, 2004 at 08:32:31PM +0200, Jens Schweikhardt wrote: > # On Wed, May 12, 2004 at 11:48:06AM -0600, Scott Long wrote: > # ... > # # I can't remember how the 2100 BIOS works, I'll have to take a look. > # # I thought that it was an attribute that was set when the array is > # # created. > # > # Yes, and once its set at array creation time it apparently can not be > # changed. I deleted the array and created it anew to disable read > # caching. This did not yield any perfomance gain by itself. After I > # changed the cables I now have 79MB/s (formerly only 29MB/s, a single > # disk has a sustained read speed of 71MB/s at the outer sectors). Next > # thing will be going back from forced U160 mode to U320. I'll report the > # results, so watch this space :-) > > Went back to U320 and enabled packetized--even with the Adaptec > cable that came with the controller no joy :-( > > At first, dd reported 83MB/s but after skipping the first 1G the > controller(?) made a high pitched beep, and this was in dmesg > > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** <...repeats 2 more times> > aac0: **Monitor** Drive 0:14:0 online on container 0: > aac0: **Monitor** Drive 0:15:0 online on container 0: > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** <...repeats 1 more times> > aac0: **Monitor** Drive 0:14:0 online on container 0: > aac0: **Monitor** Drive 0:15:0 online on container 0: > aac0: **Monitor** SCSI bus reset issued on channel 0 > aac0: **Monitor** Drive 0:15:0 returning error > aac0: **Monitor** ID(0:15:0) - Cmd[0x28] failed (retries exhausted) > aac0: **Monitor** Alarm Adapter Event -- turning Alarm On! > aac0: **Monitor** Container 0 returning error on drive 0:15:0 > aacd0: hard error cmd=read 2551359-2551486 > aacd0: hard error cmd=read 5013567-5013694 > ... > aacd0: hard error cmd=read 35094591-35094718 > aacd0: hard error cmd=read 35094719-35094846 > aacd0: hard error cmd=read 35094591-35094718 > aacd0: hard error cmd=read 35094719-35094846 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aacd0: hard error cmd=read 37601343-37601470 > aacd0: hard error cmd=read 37601471-37601598 > aac0: **Monitor** ID(0:15:0) - Cmd[0x2a] failed (retries exhausted) > aac0: **Monitor** Last Adapter Alarm Event -- Alarm turning off! > Error probing container 0 > aacd0: detached > aac0: **Monitor** Drive 0:14:0 online > > Hmm. Should I still go for another U320 cable? > > Regards, > > Jens Something on the SCSI bus is very unhappy. What drives are they? What firmware rev? Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 12 12:21:01 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8259F16A4CE; Wed, 12 May 2004 12:21:01 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 395CD43D46; Wed, 12 May 2004 12:21:01 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 367163BA5F; Wed, 12 May 2004 21:21:00 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) i4CJJnGv001035; Wed, 12 May 2004 21:19:49 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost)i4CJJndc001034; Wed, 12 May 2004 21:19:49 +0200 (CEST) (envelope-from schweikh) Date: Wed, 12 May 2004 21:19:49 +0200 From: Jens Schweikhardt To: Scott Long Message-ID: <20040512191949.GA1016@schweikhardt.net> References: <40A26356.409@freebsd.org> <20040512183231.GB3137@schweikhardt.net> <20040512190429.GA1315@schweikhardt.net> <40A27607.9040801@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40A27607.9040801@freebsd.org> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 19:21:01 -0000 On Wed, May 12, 2004 at 01:07:51PM -0600, Scott Long wrote: ... # Something on the SCSI bus is very unhappy. What drives are they? What # firmware rev? 2 Fujitsu MAP3367NP with fw 0105. They've been working for a year on my 29160 without a hitch. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 07:32:22 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 664C916A4CE; Thu, 13 May 2004 07:32:22 -0700 (PDT) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5D2A43D66; Thu, 13 May 2004 07:32:21 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.11/8.12.8) with ESMTP id i4DEWLIM071537; Thu, 13 May 2004 08:32:21 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Thu, 13 May 2004 08:32:21 -0600 From: "Justin T. Gibbs" To: Jens Schweikhardt , Scott Long Message-ID: <2991245408.1084458741@aslan.scsiguy.com> In-Reply-To: <20040512191949.GA1016@schweikhardt.net> References: <40A26356.409@freebsd.org><20040512190429.GA1315@schweikhardt.net> <40A27607.9040801@freebsd.org> <20040512191949.GA1016@schweikhardt.net> X-Mailer: Mulberry/3.1.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: freebsd-scsi@freebsd.org Subject: Re: 2120S Stripe - abysmal performance X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 14:32:22 -0000 > On Wed, May 12, 2004 at 01:07:51PM -0600, Scott Long wrote: > ... ># Something on the SCSI bus is very unhappy. What drives are they? What ># firmware rev? > > 2 Fujitsu MAP3367NP with fw 0105. They've been working for a year > on my 29160 without a hitch. At U320 speeds, I believe you need 0107 or better to have these drives work. You should contact Fujitsu to ensure you have the latest firmware. -- Justin From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 08:57:10 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9598916A4CE for ; Thu, 13 May 2004 08:57:10 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF3043D49 for ; Thu, 13 May 2004 08:57:10 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4DG20u6073990; Thu, 13 May 2004 10:02:00 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A39AC3.40600@freebsd.org> Date: Thu, 13 May 2004 09:56:51 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: <40A26F7E.3060203@freebsd.org> In-Reply-To: <40A26F7E.3060203@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'scsi@freebsd.org'" Subject: Re: Intel SRCU42X raid support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 15:57:10 -0000 Scott Long wrote: > Don Bowman wrote: > >> Does anyone know if the intel SRCU42X works with FreeBSD? Does the iir >> driver support it? >> >> http://www.intel.com/design/servers/SRCU42X/ >> >> It seems like a pretty good product from the >> specs. >> >> The iir driver man page indicates it supports >> >> Intel RAID Controller SRCMR >> Intel Server RAID Controller U3-l (SRCU31a) >> Intel Server RAID Controller U3-1L (SRCU31La) >> Intel Server RAID Controller U3-2 (SRCU32) >> All past and future releases of Intel and ICP RAID Controllers. >> >> That last is a bold statement :) >> > > I'll ask the iir folks. If not, it might be interesting to write a > driver for it. > > Scott I just got word back that this card is not supported by the IIR driver. I'll try to contact Intel about getting specs. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 09:01:15 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 645AB16A4CE for ; Thu, 13 May 2004 09:01:15 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDE9543D64 for ; Thu, 13 May 2004 09:01:14 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Thu, 13 May 2004 12:01:13 -0400 Message-ID: From: Don Bowman To: "'scsi@freebsd.org'" Date: Thu, 13 May 2004 12:01:13 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: smartmontools with aac X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 16:01:15 -0000 is there a way to use smartmontools with aac? e.g. smartctl wants to see 'ad0' or 'da0' as the disk to connect to. For aac, it is aacd0. Specifying: smartctl -i -d scsi -a aacd0 gives Smartctl open device: aacd0 failed: Inappropriate ioctl for device I'm not really sure what ioctl are being used, i guess i should look in the smartmontool source. --don From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 09:06:53 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CD2016A4CE for ; Thu, 13 May 2004 09:06:53 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96D3643D53 for ; Thu, 13 May 2004 09:06:52 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4DGBcu6074047; Thu, 13 May 2004 10:11:38 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A39D05.9010405@freebsd.org> Date: Thu, 13 May 2004 10:06:29 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "'scsi@freebsd.org'" Subject: Re: smartmontools with aac X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 16:06:53 -0000 Don Bowman wrote: > is there a way to use smartmontools with > aac? > > e.g. smartctl wants to see 'ad0' or 'da0' > as the disk to connect to. For aac, it is > aacd0. Specifying: > > smartctl -i -d scsi -a aacd0 > gives > Smartctl open device: aacd0 failed: Inappropriate ioctl for device > > I'm not really sure what ioctl are being used, > i guess i should look in the smartmontool source. > > --don AAC containers do not export SMART events. You can monitor individual disks by enabling the aacp driver and watching the /dev/passN devices, or you can script the aaccli to report events for you. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 10:49:57 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 867BE16A4CE; Thu, 13 May 2004 10:49:57 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89EED43D2D; Thu, 13 May 2004 10:49:56 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Thu, 13 May 2004 13:49:55 -0400 Message-ID: From: Don Bowman To: 'Scott Long' , Don Bowman Date: Thu, 13 May 2004 13:49:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'scsi@freebsd.org'" Subject: RE: smartmontools with aac X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 17:49:57 -0000 From: Scott Long [mailto:scottl@freebsd.org] > Don Bowman wrote: > > is there a way to use smartmontools with > > aac? > > > > e.g. smartctl wants to see 'ad0' or 'da0' > > as the disk to connect to. For aac, it is > > aacd0. Specifying: > > > > smartctl -i -d scsi -a aacd0 > > gives > > Smartctl open device: aacd0 failed: Inappropriate ioctl for device > > > > I'm not really sure what ioctl are being used, > > i guess i should look in the smartmontool source. > > > > --don > > AAC containers do not export SMART events. You can monitor individual > disks by enabling the aacp driver and watching the /dev/passN devices, > or you can script the aaccli to report events for you. The problem i am trying to work around is with camcontrol inq on the pass through device (on releng_4). I would like to get the serial number (also would like to monitor the drives, but that's next, i have aaccli scripted into nagios for drive failure). Smartmontools doesn't seem to understand pass devices, or at least, i don't know how to make it. I do have the aacp configured, and it works somewhat. The bug i am seeing with the serial number fetch via camcontrol is: (wheel)# camcontrol inq 0:0:0 -v pass0: Fixed unknown SCSI-3 device CAM status is 0x12 camcontrol: error getting transfer settings CAM status is 0x6 (wheel)# (wheel)# shows the error, on a system with aac. (wheel)# camcontrol devlist at scbus0 target 0 lun 0 (pass0) at scbus0 target 2 lun 0 (pass1) at scbus0 target 3 lun 0 (pass2) at scbus0 target 4 lun 0 (pass3) at scbus0 target 8 lun 0 (ses0,pass4) at scbus1 target 8 lun 0 (ses1,pass5) >From the hitachi manual for the disk (http://www.hitachigst.com/tech/techlib.nsf/techdocs/6BB69573F9D1537687256BD 600697AAA/$file/U146Z10_sp22H.pdf) it does support this message, and it works with ahd (i think, i haven't recently checked). --don From owner-freebsd-scsi@FreeBSD.ORG Thu May 13 20:12:19 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E8B616A4CE for ; Thu, 13 May 2004 20:12:19 -0700 (PDT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEDEE43D31 for ; Thu, 13 May 2004 20:12:18 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id EE9DD388DC; Fri, 14 May 2004 00:12:17 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E79AB36115 for ; Fri, 14 May 2004 00:12:17 -0300 (ADT) Date: Fri, 14 May 2004 00:12:17 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20040514000959.R58152@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Intel SRCU42L on Tyan Thunder K7X Pro S2469UGN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 03:12:19 -0000 Does anyone know of any issues with that combination? I'm runing the above card on an Intel system right now, and have been quite happy with it (especially since getting the storcon utility) ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Fri May 14 07:00:41 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0E6F16A4D0; Fri, 14 May 2004 07:00:41 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2389E43D41; Fri, 14 May 2004 07:00:40 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Fri, 14 May 2004 10:00:38 -0400 Message-ID: From: Don Bowman To: 'Scott Long' , Don Bowman , Zac Thompson Date: Fri, 14 May 2004 10:00:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'scsi@freebsd.org'" Subject: RE: smartmontools with aac X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 14:00:42 -0000 From: Scott Long [mailto:scottl@freebsd.org] > Don Bowman wrote: > > is there a way to use smartmontools with > > aac? > > > > e.g. smartctl wants to see 'ad0' or 'da0' > > as the disk to connect to. For aac, it is > > aacd0. Specifying: > > > > smartctl -i -d scsi -a aacd0 > > gives > > Smartctl open device: aacd0 failed: Inappropriate ioctl for device > > > > I'm not really sure what ioctl are being used, > > i guess i should look in the smartmontool source. > > > > --don > > AAC containers do not export SMART events. You can monitor individual > disks by enabling the aacp driver and watching the /dev/passN devices, > or you can script the aaccli to report events for you. So i was tracking down why i can't do a 'camcontrol inq' on aac. When i do: camcontrol inq 0:2 -v I get: pass1: Fixed unknown SCSI-3 device CAM status is 0x12 [long pause, ~30s?] camcontrol: error getting transfer settings CAM status is 0x6 camcontrol cmd pass1 -v -c "12 01 00 00 01 00" -i 1 "b3 b5" 0 31 ---------- According to the docs, the second of these numbers should be 0, unless the LUN (pass1) is not present, in which case 31 is correct, but then the first number should be 3. Maybe this is what the RAID is botching, and what "camcontrol inquiry" can't handle to get the serial number. Byte | Bit | 7 6 5 | 4 3 2 1 0 0 | Peripheral Device Type | Peripheral Qualifier "Peripheral Qualifier is set to zero to indicate that the LUN specified in the IDENTIFY Message is currently supported. Peripheral Qualifier is set to 011b when the LUN specified in the IDENTIFY Message is not present. Peripheral Device Type is set to zero to indicate that the device is a Direct-Access. Peripheral Device Type is set to 1Fh when the LUN specified in the IDENTIFY Message is not present." From owner-freebsd-scsi@FreeBSD.ORG Fri May 14 09:40:06 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D86BE16A4CE for ; Fri, 14 May 2004 09:40:06 -0700 (PDT) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44EC743D41 for ; Fri, 14 May 2004 09:40:06 -0700 (PDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c09852.dyn.optonline.net [68.192.152.82]) (authenticated bits=128)i4EGe5A3033702 for ; Fri, 14 May 2004 12:40:05 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1])id i4EGe4cN056792 for ; Fri, 14 May 2004 12:40:04 -0400 (EDT) (envelope-from tuc@tucs-beachin-obx-house.com) Received: (from tucobx@localhost)i4EGe4sC056791 for freebsd-scsi@freebsd.org; Fri, 14 May 2004 12:40:04 -0400 (EDT) (envelope-from tucobx) From: Tuc at Beach House Message-Id: <200405141640.i4EGe4sC056791@himinbjorg.tucs-beachin-obx-house.com> To: freebsd-scsi@freebsd.org Date: Fri, 14 May 2004 12:40:04 -0400 (EDT) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Issues with SYM/EasyRaid X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 16:40:07 -0000 Hi, Having a SCSI Geometry issue on a 5.2.1-RELEASE-p4 system. It has a Symbios SDMS PCI SCSI, 53C1010-66 adapter that shows up as : sym0: <1010-66> port 0xa000-0xa0ff mem 0xf6000000-0xf6001fff,0xf6800000-0xf68003 ff irq 25 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. And to it I'm connecting an EasyRaid II RAID box. There is LITTLE I can configure on it, basically termination, SCSI ID, and Raid 0/1/0+1/3/5 and thats pretty much it. When the system boots, the splash screen claims the geometry is 1024/255/63 at 40M sync, and 16 wide. In the controller I've used "Alternate CHS Mapping" and "SCSI Plug and Play Mapping" without any differences. When FreeBSD boots, it sees : (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. da0 at sym1 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 1060184MB (2171256832 512 byte sectors: 255H 63S/T 135154C) When I try to /stand/sysinstall it, fdisk pitches a serious fit about it. What can I do to get this configured properly? It seems that if I bring it down to RAID-1+0, it configures up fine (Not sure what the geometry shows as, sorry). Thanks, Tuc/TTSG Internet Services, Inc. From owner-freebsd-scsi@FreeBSD.ORG Fri May 14 12:08:52 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBD4916A4CE for ; Fri, 14 May 2004 12:08:52 -0700 (PDT) Received: from us038mx00.amp.com (nat208239159208.amp.com [208.239.159.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4067C43D39 for ; Fri, 14 May 2004 12:08:52 -0700 (PDT) (envelope-from jspiro-colwell@tycoelectronics.com) Received: from US038MX02.us.tycoelectronics.com ([163.241.175.208]) by us038mx00.amp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id K7N5SGMT; Fri, 14 May 2004 15:08:51 -0400 Received: by us038mx02.us.tycoelectronics.com with Internet Mail Service (5.5.2657.72) id ; Fri, 14 May 2004 15:08:51 -0400 Message-ID: <98435D0AC03ED711972A00508BF9F6720DDDAC7A@ammex008.amp.com> From: "Spiro-Colwell, John P." To: "'freebsd-scsi@freebsd.org'" Date: Fri, 14 May 2004 15:08:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Subject: Raidutil and DPT PM3334UW on 4.7-Release X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 19:08:53 -0000 Hi, I have a DPT PM3334UW FW Rev. 07M0 on 4.7-release and I am trying to administer it. I installed the asrutil package, but raidutil fails with the following error. Engine connect failed: COMPATILITY number osdIOrequest : File /dev/rdptr17 Could Not Be Opened According to dmesg the card is at dpt0. dpt0: port 0x1060-0x107f irq 11 at device 9.0 on pci0 dpt0: DPT PM3334UW FW Rev. 07M0, 1 channel, 64 CCBs But there is no dpt0 in /dev. Camcontrol gives this output: laserdiode# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 14 lun 0 (ses0,pass1) at scbus0 target 15 lun 0 (ses1,pass2) Thanks for any help, John Paul From owner-freebsd-scsi@FreeBSD.ORG Sat May 15 14:36:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4222A16A4CE for ; Sat, 15 May 2004 14:36:36 -0700 (PDT) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.208.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id E979D43D5D for ; Sat, 15 May 2004 14:36:34 -0700 (PDT) (envelope-from lambert@lambertfam.org) Received: from localhost (localhost [127.0.0.1]) by mail.lambertfam.org (Postfix) with ESMTP id 198E734D66 for ; Sat, 15 May 2004 17:36:32 -0400 (EDT) Received: from mail.lambertfam.org ([127.0.0.1]) by localhost (www.lambertfam.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41677-05 for ; Sat, 15 May 2004 17:36:31 -0400 (EDT) Received: from laptop.lambertfam.org (cdm-66-233-132-205.rsvl.cox-internet.com [66.233.132.205]) by mail.lambertfam.org (Postfix) with ESMTP id D42D234D69 for ; Sat, 15 May 2004 17:36:30 -0400 (EDT) Received: by laptop.lambertfam.org (Postfix, from userid 1001) id BA2EFC1F8; Sat, 15 May 2004 16:36:29 -0500 (CDT) Date: Sat, 15 May 2004 16:36:29 -0500 From: Scott Lambert To: The FreeBSD SCSI List Message-ID: <20040515213629.GB787@laptop.lambertfam.org> Mail-Followup-To: The FreeBSD SCSI List References: <98435D0AC03ED711972A00508BF9F6720DDDAC7A@ammex008.amp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98435D0AC03ED711972A00508BF9F6720DDDAC7A@ammex008.amp.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at lambertfam.org Subject: Re: Raidutil and DPT PM3334UW on 4.7-Release X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: The FreeBSD SCSI List List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 21:36:36 -0000 On Fri, May 14, 2004 at 03:08:50PM -0400, Spiro-Colwell, John P. wrote: > Hi, > I have a DPT PM3334UW FW Rev. 07M0 on 4.7-release and I am trying to > administer it. I installed the asrutil package, but raidutil fails with the > following error. > > Engine connect failed: COMPATILITY number > osdIOrequest : File /dev/rdptr17 Could Not Be Opened > > According to dmesg the card is at dpt0. > > dpt0: port 0x1060-0x107f irq 11 at device > 9.0 on pci0 > dpt0: DPT PM3334UW FW Rev. 07M0, 1 channel, 64 CCBs > > But there is no dpt0 in /dev. > > Camcontrol gives this output: > laserdiode# camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 14 lun 0 (ses0,pass1) > at scbus0 target 15 lun 0 (ses1,pass2) I have the same symptoms with a different card on a system which has been up and functioning for 100 days. I've been checking the raid status every five minutes with a nagios plugin script. That has been working until early this morning. 3:05 a.m. to be exact. I have another system which is still working. I've verified the MD5 sums of the /usr/dpt files. The working system has: 15:39:27 Sat May 15 # ls -la /dev/*dpt* crw------- 1 root wheel 154, 0 Oct 3 2002 /dev/rdpti0 The non-working system removes that node when I create it. Non-working: 16:20:48 Sat May 15 # ./raidutil -A ? Engine connect failed: COMPATIBILITY number osdIOrequest : File /dev/rdptr17 Could Not Be Opened 16:08:12 Sat May 15 # uname -a FreeBSD mail.example.com 4.7-STABLE FreeBSD 4.7-STABLE #4: Fri Apr 11 12:13:11 CDT 2003 root@mail.example.com:/usr/src/sys/compile/mail i386 asr0: mem 0xf8000000-0xf9ffffff,0xfb000000-0xfbffffff,0xfea00000-0xfeafffff irq 18 at device 8.0 on pci4 asr0: major=154 asr0: ADAPTEC 2000S FW Rev. 380E, 2 channel, 256 CCBs, Protocol I2O Working: 16:35:14 Sat May 15 # ./raidutil -A ? # b0 b1 b2 Controller Alarm Status Alarm Enable --------------------------------------------------------------------------- d0 -- -- 2000S Off Enabled FreeBSD ns.example.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Thu Nov 20 03:11:25 CST 2003 root@ns.example.com:/usr/src/sys/compile/test i386 asr0: mem 0xfc000000-0xfdffffff,0xfb000000-0xfbffffff,0xfa000000-0xfa0fffff irq 9 at device 9.0 on pci2 asr0: major=154 asr0: ADAPTEC 2000S FW Rev. 380E, 2 channel, 256 CCBs, Protocol I2O -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org