From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 12 03:54:46 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 F232616A41F; Sun, 12 Jun 2005 03:54:45 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5687743D48; Sun, 12 Jun 2005 03:54:45 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j5C3siTO021294; Sat, 11 Jun 2005 21:54:44 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j5C3seJv021293; Sat, 11 Jun 2005 21:54:40 -0600 (MDT) (envelope-from ken) Date: Sat, 11 Jun 2005 21:54:40 -0600 From: "Kenneth D. Merry" To: "Raphael H. Becker" Message-ID: <20050612035440.GA21262@nargothrond.kdm.org> References: <20050608152459.BF24E16A45C@hub.freebsd.org> <1118248386.7479.10.camel@zappa.Chelsea-Ct.Org> <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050612002508.B25098@p-i-n.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.85.1/925/Sat Jun 11 12:55:32 2005 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2005 03:54:46 -0000 On Sun, Jun 12, 2005 at 00:25:08 +0200, Raphael H. Becker wrote: > On Fri, Jun 10, 2005 at 09:07:18AM -0600, Kenneth D. Merry wrote: > > > > and here the relevant diffs: > > > http://rabe.uugrn.org/temp/FreeBSD/bigraid/dmesg.knoppix_diff.txt > > > > This is quite interesting: > [....] > > Linux notices that the device returned 0xffffffff as the capacity in > > response to a READ CAPACITY(10) command, so it tries a READ CAPACITY(16) > > command, which *fails*. > > > > So even under Linux you aren't getting the full capacity of your device, > > you're only getting 2TB. > > The support told me, SuSE Linux is known to work with >2TB in one device, > means they might have some patches to work around. I will try a SuSE > live system next days just to get sure it works. But the System won't > be SuSE in future. It would be interesting to see whether that works. That would help narrow down the problem slightly. > > > Second I rebooted FreeBSD with CAMDEBUG in kernel and enabled it via > > > "camcontrol debug ..." and did a "camcontrol rescan 1" then: > > > http://rabe.uugrn.org/temp/FreeBSD/bigraid/freebsd54_camdebug.txt > > > > camcontrol debug -I isn't quite what we need in this situation. Instead, > > you should try 'camcontrol debug -c'. > > # camcontrol debug -c 1:0 > # camcontrol rescan 1 > Re-scan of bus 1 was successful > > in /var/log/messages: > > kernel: (probe0:ahc1:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > kernel: (probe0:ahc1:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 > kernel: (probe0:ahc1:0:0:0): INQUIRY. CDB: 12 0 0 0 fc 0 > kernel: (probe0:ahc1:0:0:0): MODE SENSE(06). CDB: 1a 0 a 0 14 0 > kernel: (probe0:ahc1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 > kernel: (probe0:ahc1:0:0:1): INQUIRY. CDB: 12 20 0 0 24 0 > kernel: (probe0:ahc1:0:0:2): INQUIRY. CDB: 12 40 0 0 24 0 > kernel: (probe0:ahc1:0:0:3): INQUIRY. CDB: 12 60 0 0 24 0 > kernel: (probe0:ahc1:0:0:4): INQUIRY. CDB: 12 80 0 0 24 0 > kernel: (probe0:ahc1:0:0:5): INQUIRY. CDB: 12 a0 0 0 24 0 > kernel: (probe0:ahc1:0:0:6): INQUIRY. CDB: 12 c0 0 0 24 0 > kernel: (probe0:ahc1:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 > > Does not say anything to me. Hmm, well, you're not going to see the problem CDB that way, because the probe has already happened. To see it, you either need to compile in the debugging flags, or do the following: - unplug the cable from the machine to the RAID array - camcontrol rescan 1 - plug the cable back in - camcontrol rescan 1 > > > Any idea, whats wrong with it? > > > > >From what I can see, it's likely the device is misbehaving. The fact that > > the 16 byte read capacity fails under Linux is telling. If you've got a > > device that supports a LUN size greater than 2TB, it must support the 16 > > byte read capacity and read/write commands. > > So you would say this is a misbehaviour of the RAID's firmware/controller? It's either the RAID box or the ahc driver from what I can see at this point. See below. > > Here are some more things you can try. Does your system boot? > Well, that RAID is just one of 3 RAIDs, the system is on the internal PERC-RAID. > > > If so, we > > can try sending a few commands to the device via the pass(4) driver and see > > what happens. > > > First, run 'camcontrol devlist' and see if the array is there and whether > > there is a pass device attached. If so, try this: > > > > camcontrol cmd passX -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" > > at scbus1 target 0 lun 0 (pass3) > # camcontrol cmd pass3 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" > -1 512 Okay, that's good. The -1 means that the RAID box is telling us that we need to send the 16 byte read capacity command to get the true capacity. (That's what a capacity of 0xffffffff, or -1, means.) > > That will send a standard 10 byte read capacity command to the device. > > Next, try a 16 byte read capacity. This is where things are likely failing > > in the da(4) driver attach, and apparantly where things are failing under > > Linux: > > > > camcontrol cmd passX -v -c "9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0" -i 12 "i4 i4 i4" > > # camcontrol cmd pass3 -v -c "9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0" -i 12 "i4 i4 i4" > camcontrol: error sending command > (pass3:ahc1:0:0:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 > (pass3:ahc1:0:0:0): CAM Status: Target Bus Phase Sequence Failure > > dmesg: > (pass3:ahc1:0:0:0): No or incomplete CDB sent to device. > (pass3:ahc1:0:0:0): Protocol violation in Message-in phase. Attempting to abort. > (pass3:ahc1:0:0:0): Abort Tag Message Sent > (pass3:ahc1:0:0:0): SCB 8 - Abort Tag Completed. Hmm, okay, at this point, we have a SCSI protocol violation. (Which is the same thing you saw before.) So this pretty much means it is the 16 byte read capacity that is triggering the problem. The question is, is this problem on the RAID box or in the ahc driver? I would lean towards saying the RAID box has the issue, but Justin (CCed) may be able to give a little more insight. > > If that works, there is some other problem. If it fails, then we're > > fairly close to the problem. > > So, if it's a problem with the RAIDs firmware and/or maybe hardware, > do you expect there's a workaround in FreeBSD for it? It's either a problem with the firmware on the RAID controller or with the ahc driver. If it turns out that the RAID controller is at fault, then you'll need to get fixed firmware. It'll be interesting to see whether a SuSE live system works with it. (And reports a capacity that is greater than 2TB.) Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 13 04:32:16 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 E7F8616A41C; Mon, 13 Jun 2005 04:32:16 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 462BE43D1F; Mon, 13 Jun 2005 04:32:16 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) (authenticated bits=0) by aslan.scsiguy.com (8.13.3/8.13.3) with ESMTP id j5D4WE64043586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 12 Jun 2005 22:32:14 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Sun, 12 Jun 2005 22:32:14 -0600 From: "Justin T. Gibbs" To: "Kenneth D. Merry" , "Raphael H. Becker" Message-ID: In-Reply-To: <20050612035440.GA21262@nargothrond.kdm.org> References: <20050608152459.BF24E16A45C@hub.freebsd.org> <1118248386.7479.10.camel@zappa.Chelsea-Ct.Org> <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> X-Mailer: Mulberry/3.1.6 (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, freebsd-current@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 04:32:17 -0000 >> # camcontrol cmd pass3 -v -c "9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0" -i 12 "i4 i4 i4" >> camcontrol: error sending command >> (pass3:ahc1:0:0:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 c 0 0 >> (pass3:ahc1:0:0:0): CAM Status: Target Bus Phase Sequence Failure >> >> dmesg: >> (pass3:ahc1:0:0:0): No or incomplete CDB sent to device. >> (pass3:ahc1:0:0:0): Protocol violation in Message-in phase. Attempting to abort. >> (pass3:ahc1:0:0:0): Abort Tag Message Sent >> (pass3:ahc1:0:0:0): SCB 8 - Abort Tag Completed. > > Hmm, okay, at this point, we have a SCSI protocol violation. (Which is the > same thing you saw before.) > > So this pretty much means it is the 16 byte read capacity that is > triggering the problem. > > The question is, is this problem on the RAID box or in the ahc driver? I > would lean towards saying the RAID box has the issue, but Justin (CCed) may > be able to give a little more insight. The diagnostics indicate that the aic7xxx chip believes the entire CDB was not transferred to the target before the target attempted to disconnect or complete the command. While 16byte cdb support in this driver was reported to work correctly in the past, that does not guarantee that I haven't somehow broken it - the firmware could be incorrectly determining cdb transfer completion status in this case even though the logic appears to be correct. I'll try to setup a target mode emulation environment this week to see if I can replicate the problem. What controller/chip are you using? -- Justin From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 13 10:19:20 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 0BA8C16A41C; Mon, 13 Jun 2005 10:19:20 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from dns.p-i-n.com (dns.p-i-n.com [145.253.185.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0EEA43D48; Mon, 13 Jun 2005 10:19:18 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from p-i-n.com (inside.p-i-n.com [129.10.9.21]) by dns.p-i-n.com (8.12.9p2/8.12.9) with ESMTP id j5DAJGOf032084; Mon, 13 Jun 2005 12:19:16 +0200 (CEST) (envelope-from rabe@p-i-n.com) Received: (from rabe@localhost) by p-i-n.com (8.11.6/8.11.6) id j5DAJFJ69759; Mon, 13 Jun 2005 12:19:15 +0200 (CEST) (envelope-from rabe) Date: Mon, 13 Jun 2005 12:19:15 +0200 From: "Raphael H. Becker" To: "Justin T. Gibbs" Message-ID: <20050613121915.C25098@p-i-n.com> References: <1118248386.7479.10.camel@zappa.Chelsea-Ct.Org> <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gibbs@scsiguy.com on Sun, Jun 12, 2005 at 10:32:14PM -0600 Organization: PHOENIX Pharmahandel AG & Co KG, Mannheim, Deutschland Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, "Kenneth D. Merry" Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 10:19:20 -0000 On Sun, Jun 12, 2005 at 10:32:14PM -0600, Justin T. Gibbs wrote: > even though the logic appears to be correct. I'll try to setup a > target mode emulation environment this week to see if I can replicate > the problem. What controller/chip are you using? dmesg: [...] acpi0: on motherboard acpi0: Power Button (fixed) [...] pcib5: on acpi0 pci1: on pcib5 [...] ahc0: port 0xdc00-0xdcff mem 0xfcf01000-0xfcf01fff irq 20 at device 8.0 on pci1 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0xd800-0xd8ff mem 0xfcf00000-0xfcf00fff irq 21 at device 8.1 on pci1 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs [...] pciconf -lv [...] ahc0@pci1:8:0: class=0x010000 card=0xf6209005 chip=0x00c09005 rev=0x01 hdr=0x00 vendor = 'Adaptec Inc' device = 'AHA-39160 (AIC-7899A) Ultra160 SCSI Host Adapter' class = mass storage subclass = SCSI ahc1@pci1:8:1: class=0x010000 card=0xf6209005 chip=0x00c09005 rev=0x01 hdr=0x00 vendor = 'Adaptec Inc' device = 'AHA-39160 (AIC-7899A) Ultra160 SCSI Host Adapter' class = mass storage subclass = SCSI [...] Hopefully this is what you need. TIA Raphael Becker PS+BTW: any idea why the internal PERC is not listed in camcontrol devlist? In dmesg its listed like aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: i960RX 100MHz, 118MB cache memory, optional battery present aac0: Kernel 2.7-1, Build 3170, S/N 5410d3 aac0: Supported Options=75c [...] aacd0: on aac0 aacd0: 69425MB (142182912 sectors) pciconf: aac0@pci4:8:1: class=0x010400 card=0x01211028 chip=0x000a1028 rev=0x01 hdr=0x00 vendor = 'Dell Computer Corporation' device = 'PowerEdge 3/Di Expandable RAID Controller' class = mass storage subclass = RAID It's not SCSI? From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 13 11:02:15 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 9C65816A420 for ; Mon, 13 Jun 2005 11:02:15 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78E6043D53 for ; Mon, 13 Jun 2005 11:02:15 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5DB2Fu1046266 for ; Mon, 13 Jun 2005 11:02:15 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5DB2EK7046259 for freebsd-scsi@freebsd.org; Mon, 13 Jun 2005 11:02:14 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 13 Jun 2005 11:02:14 GMT Message-Id: <200506131102.j5DB2EK7046259@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 11:02:15 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi (symbios) SCSI subsystem hangs under heav o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug s [2003/09/30] kern/57398 scsi Current fails to install on mly(4) based o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with a [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/09/15] kern/71778 scsi 5.3 BETA3 doesnt see Adaptec 2015S FW Rev o [2004/12/02] kern/74607 scsi FreeBSD 5.3 install CD crashes on SCSI de o [2004/12/02] kern/74627 scsi Adaptec 2940U2W Can't boot 5.3 10 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57469 scsi [patch] Quirk for Conner CP3500 6 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 13 17:43:46 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 04C5C16A41C for ; Mon, 13 Jun 2005 17:43:46 +0000 (GMT) (envelope-from paul.wisniewski@icecube.wisc.edu) Received: from snow.icecube.wisc.edu (snow.icecube.wisc.edu [128.104.255.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id B519143D5C for ; Mon, 13 Jun 2005 17:43:45 +0000 (GMT) (envelope-from paul.wisniewski@icecube.wisc.edu) Received: from [172.16.55.162] (unknown [128.104.34.126]) by snow.icecube.wisc.edu (Postfix) with ESMTP id 4802C13C17C for ; Mon, 13 Jun 2005 12:43:45 -0500 (CDT) Message-ID: <42ADC5D6.2020403@icecube.wisc.edu> Date: Mon, 13 Jun 2005 12:43:50 -0500 From: paw Organization: UW-IceCube User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Scsi problems with MPT-Fusion-based HBA X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paul.wisniewski@icecube.wisc.edu List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 17:43:46 -0000 Hi, I am hoping that the experts on the list may be able to give me some insight with an a scsi-related problem I am experiencing. I am simply looking for an interpretation of what this I/O means, or what I might be able to try to solve the problem. The equipment is in a remote location, and spare parts are not available to try swapping things out. Thanks in advance for all your help, --paw Kernel: 2.4 Server: HP Proliant 380DL Scsi: (HP Part # 268351-B21, LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 Device: Western Scientific EonStor A16F/A16U Disk Array 16-disk, 6TB RAID divvied into 2TB partitions Connection: Single 3 foot scsi cable rated to U320. Problems: Extremly poor throughput, and intermittant, debilitating Scsi errors causing lockups. Server reboots necessary to clear error conditions Example of errors: scsi : aborting command due to timeout : pid 541102, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 14 80 00 01 40 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c06e00) scsi : aborting command due to timeout : pid 541099, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 11 f0 00 00 10 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c48200) SCSI host 0 abort (pid 541097) timed out - resetting SCSI bus is being reset for host 0 channel 0. mptscsih: OldReset scheduling BUS_RESET (sc=c6c07200) SCSI host 0 abort (pid 541095) timed out - resetting SCSI bus is being reset for host 0 channel 0. mptscsih: OldReset scheduling BUS_RESET (sc=c6d04200) scsi : aborting command due to timeout : pid 541100, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 12 00 00 01 40 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c59200) scsi : aborting command due to timeout : pid 541103, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 15 c0 00 01 38 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c48e00) scsi : aborting command due to timeout : pid 541098, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 11 48 00 00 a8 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c06c00) SCSI host 0 abort (pid 541096) timed out - resetting SCSI bus is being reset for host 0 channel 0. mptscsih: OldReset scheduling BUS_RESET (sc=c6c48400) scsi : aborting command due to timeout : pid 541101, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 13 40 00 01 40 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6d04400) scsi : aborting command due to timeout : pid 541102, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 14 80 00 01 40 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c06e00) scsi : aborting command due to timeout : pid 541099, scsi0, channel 0, id 0, lun 0 Write (10) 00 51 05 11 f0 00 00 10 00 mptscsih: OldAbort scheduling ABORT SCSI IO (sc=c6c48200) SCSI host 0 abort (pid 541097) timed out - resetting SCSI bus is being reset for host 0 channel 0. --------------------------- Flushing ide devices: hda mptbase: Initiating ioc0 recovery mptbase: ioc0: WARNING - Unexpected doorbell active mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus = ffffffff! From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 13 23:47:03 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 4C87516A41C for ; Mon, 13 Jun 2005 23:47:03 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD61243D4C for ; Mon, 13 Jun 2005 23:47:02 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so1356108rne for ; Mon, 13 Jun 2005 16:47:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GqV1TkTCiyFjro6OEr8r8CtaVQVEKyThaP/bulP/LLuTkFYeay55jcuwgVaikJ1JTBcL9VouzTCnJoEDjMGUvsQYT5nbtG1b29lxNuWP9tmBqRgfdgIYU7VhOn6agN4xtKJjn0sNZ92u/C4NM1Ab7sTOoi5Zob1v9McGVCYB7as= Received: by 10.38.75.14 with SMTP id x14mr745041rna; Mon, 13 Jun 2005 16:47:01 -0700 (PDT) Received: by 10.38.104.13 with HTTP; Mon, 13 Jun 2005 16:47:01 -0700 (PDT) Message-ID: <7579f7fb050613164747c547a8@mail.gmail.com> Date: Mon, 13 Jun 2005 16:47:01 -0700 From: Matthew Jacob To: paul.wisniewski@icecube.wisc.edu In-Reply-To: <42ADC5D6.2020403@icecube.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42ADC5D6.2020403@icecube.wisc.edu> Cc: freebsd-scsi@freebsd.org Subject: Re: Scsi problems with MPT-Fusion-based HBA X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthew Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 23:47:03 -0000 Wrong mailing list. The messsages indicate that you are runnning Linux. Perhaps you should install FreeBSD instead. On 6/13/05, paw wrote: > Hi, >=20 > I am hoping that the experts on the list may be able to give me some > insight with an a scsi-related problem I am experiencing. I am simply > looking for an interpretation of what this I/O means, or what I might be > able to try to solve the problem. The equipment is in a remote > location, and spare parts are not available to try swapping things out. > Thanks in advance for all your help, --paw >=20 >=20 > Kernel: 2.4 > Server: HP Proliant 380DL > Scsi: (HP Part # 268351-B21, LSI Logic / Symbios Logic 53c1030 PCI-X > Fusion-MPT Dual Ultra320 > Device: Western Scientific EonStor A16F/A16U Disk Array 16-disk, 6TB > RAID divvied into 2TB partitions > Connection: Single 3 foot scsi cable rated to U320. >=20 > Problems: > Extremly poor throughput, and intermittant, debilitating Scsi errors > causing lockups. Server reboots necessary to clear error conditions >=20 > Example of errors: >=20 > scsi : aborting command due to timeout : pid 541102, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 14 80 00 01 40 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c06e00) > scsi : aborting command due to timeout : pid 541099, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 11 f0 00 00 10 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c48200) > SCSI host 0 abort (pid 541097) timed out - resetting > SCSI bus is being reset for host 0 channel 0. > mptscsih: OldReset scheduling BUS_RESET (sc=3Dc6c07200) > SCSI host 0 abort (pid 541095) timed out - resetting > SCSI bus is being reset for host 0 channel 0. > mptscsih: OldReset scheduling BUS_RESET (sc=3Dc6d04200) > scsi : aborting command due to timeout : pid 541100, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 12 00 00 01 40 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c59200) > scsi : aborting command due to timeout : pid 541103, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 15 c0 00 01 38 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c48e00) > scsi : aborting command due to timeout : pid 541098, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 11 48 00 00 a8 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c06c00) > SCSI host 0 abort (pid 541096) timed out - resetting > SCSI bus is being reset for host 0 channel 0. > mptscsih: OldReset scheduling BUS_RESET (sc=3Dc6c48400) > scsi : aborting command due to timeout : pid 541101, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 13 40 00 01 40 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6d04400) > scsi : aborting command due to timeout : pid 541102, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 14 80 00 01 40 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c06e00) > scsi : aborting command due to timeout : pid 541099, scsi0, channel 0, > id 0, lun 0 Write (10) 00 51 05 11 f0 00 00 10 00 > mptscsih: OldAbort scheduling ABORT SCSI IO (sc=3Dc6c48200) > SCSI host 0 abort (pid 541097) timed out - resetting > SCSI bus is being reset for host 0 channel 0. >=20 > --------------------------- >=20 > Flushing ide devices: hda > mptbase: Initiating ioc0 recovery > mptbase: ioc0: WARNING - Unexpected doorbell active > mptbase: ioc0: ERROR - Doorbell ACK timeout (count=3D4999), IntStatus =3D > ffffffff! >=20 >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 02:00:01 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 19FED16A41C; Tue, 14 Jun 2005 02:00:01 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id A051443D53; Tue, 14 Jun 2005 02:00:00 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j5E1xxN0033941; Mon, 13 Jun 2005 19:59:59 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j5E1xw73033940; Mon, 13 Jun 2005 19:59:58 -0600 (MDT) (envelope-from ken) Date: Mon, 13 Jun 2005 19:59:58 -0600 From: "Kenneth D. Merry" To: "Raphael H. Becker" Message-ID: <20050614015958.GA33865@nargothrond.kdm.org> References: <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> <20050613121915.C25098@p-i-n.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050613121915.C25098@p-i-n.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.85.1/937/Mon Jun 13 15:46:03 2005 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 02:00:01 -0000 On Mon, Jun 13, 2005 at 12:19:15 +0200, Raphael H. Becker wrote: > PS+BTW: any idea why the internal PERC is not listed in camcontrol devlist? > > In dmesg its listed like > aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 > aac0: i960RX 100MHz, 118MB cache memory, optional battery present > aac0: Kernel 2.7-1, Build 3170, S/N 5410d3 > aac0: Supported Options=75c > [...] > aacd0: on aac0 > aacd0: 69425MB (142182912 sectors) > > pciconf: > aac0@pci4:8:1: class=0x010400 card=0x01211028 chip=0x000a1028 rev=0x01 hdr=0x00 > vendor = 'Dell Computer Corporation' > device = 'PowerEdge 3/Di Expandable RAID Controller' > class = mass storage > subclass = RAID > > It's not SCSI? It is a SCSI RAID controller, but the interface to the OS is a block interface, not a SCSI interface (*). It isn't routed through the SCSI layer, since that wouldn't really help it that much. (*) There is a SCSI passthrough interface for some aac controllers that can be enabled via the aacp driver. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 04:39:13 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 582A816A41C; Tue, 14 Jun 2005 04:39:13 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD40C43D1F; Tue, 14 Jun 2005 04:39:12 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j5E4i0Im008862; Mon, 13 Jun 2005 22:44:00 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42AE5ED7.8070309@samsco.org> Date: Mon, 13 Jun 2005 22:36:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Kenneth D. Merry" References: <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> <20050613121915.C25098@p-i-n.com> <20050614015958.GA33865@nargothrond.kdm.org> In-Reply-To: <20050614015958.GA33865@nargothrond.kdm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 04:39:13 -0000 Kenneth D. Merry wrote: > On Mon, Jun 13, 2005 at 12:19:15 +0200, Raphael H. Becker wrote: > >>PS+BTW: any idea why the internal PERC is not listed in camcontrol devlist? >> >>In dmesg its listed like >>aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 >>aac0: i960RX 100MHz, 118MB cache memory, optional battery present >>aac0: Kernel 2.7-1, Build 3170, S/N 5410d3 >>aac0: Supported Options=75c >>[...] >>aacd0: on aac0 >>aacd0: 69425MB (142182912 sectors) >> >>pciconf: >>aac0@pci4:8:1: class=0x010400 card=0x01211028 chip=0x000a1028 rev=0x01 hdr=0x00 >> vendor = 'Dell Computer Corporation' >> device = 'PowerEdge 3/Di Expandable RAID Controller' >> class = mass storage >> subclass = RAID >> >>It's not SCSI? > > > It is a SCSI RAID controller, but the interface to the OS is a block > interface, not a SCSI interface (*). It isn't routed through the SCSI > layer, since that wouldn't really help it that much. > > (*) There is a SCSI passthrough interface for some aac controllers that > can be enabled via the aacp driver. > > Ken And the aacp device causes many more problems than it solves, so I'll likely be disabling it soon. It only provides simple userland SCSI access to cdroms and tape drives, anyways. Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 07:34:19 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 2B0CD16A41C for ; Tue, 14 Jun 2005 07:34:19 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id E96BD43D1D for ; Tue, 14 Jun 2005 07:34:18 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j5E7YHEg017744 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Tue, 14 Jun 2005 00:34:17 -0700 Message-Id: <6.1.0.6.2.20050613235825.09e52810@cobalt.antimatter.net> X-Sender: lists@cobalt.antimatter.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Tue, 14 Jun 2005 00:30:34 -0700 To: freebsd-scsi@freebsd.org From: Glenn Dawson In-Reply-To: <42AE5ED7.8070309@samsco.org> References: <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> <20050613121915.C25098@p-i-n.com> <20050614015958.GA33865@nargothrond.kdm.org> <42AE5ED7.8070309@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 07:34:19 -0000 At 09:36 PM 6/13/2005, Scott Long wrote: >>It is a SCSI RAID controller, but the interface to the OS is a block >>interface, not a SCSI interface (*). It isn't routed through the SCSI >>layer, since that wouldn't really help it that much. >>(*) There is a SCSI passthrough interface for some aac controllers that >>can be enabled via the aacp driver. >>Ken > >And the aacp device causes many more problems than it solves, so I'll >likely be disabling it soon. It only provides simple userland SCSI access >to cdroms and tape drives, anyways. This is a little OT for this thread, but I'm currently trying to solve a problem which might be related to the aac driver, so I'll toss this out there and see if anyone has any ideas for me. It trying to make the transition from 4.x to 5.x I've noticed that performance of the md(4) (in 5.x) driver seems to be much worse than the vn(4) driver under 4.x. Here's the scenario: A pair of mirrored disks on an adaptec 2120S using the aac(4) driver is being used to house files that are the backing store for a number of virtual disks. Each file is typically about 4GB. Under 4.11 using the vn(4) driver I see throughput of about 17MB/sec when writing to one of the virtual disks (using dd). Under 5.4 using the md(4) driver I only see throughput of about 7MB/sec when writing to the virtual disk. Tests were run using the exact same hardware. >Scott >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 07:36:37 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 E1F8016A41C for ; Tue, 14 Jun 2005 07:36:37 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDD8843D49 for ; Tue, 14 Jun 2005 07:36:37 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j5E7aZjc017778 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Tue, 14 Jun 2005 00:36:35 -0700 Message-Id: <6.1.0.6.2.20050614003252.0bfc5eb0@cobalt.antimatter.net> X-Sender: lists@cobalt.antimatter.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Tue, 14 Jun 2005 00:34:48 -0700 To: freebsd-scsi@freebsd.org From: Glenn Dawson Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 07:36:38 -0000 At 09:36 PM 6/13/2005, Scott Long wrote: >>It is a SCSI RAID controller, but the interface to the OS is a block >>interface, not a SCSI interface (*). It isn't routed through the SCSI >>layer, since that wouldn't really help it that much. >>(*) There is a SCSI passthrough interface for some aac controllers that >>can be enabled via the aacp driver. >>Ken > >And the aacp device causes many more problems than it solves, so I'll >likely be disabling it soon. It only provides simple userland SCSI access >to cdroms and tape drives, anyways. This is a little OT for this thread, but I'm currently trying to solve a problem which might be related to the aac driver, so I'll toss this out there and see if anyone has any ideas for me. It trying to make the transition from 4.x to 5.x I've noticed that performance of the md(4) (in 5.x) driver seems to be much worse than the vn(4) driver under 4.x. Here's the scenario: A pair of mirrored disks on an adaptec 2120S using the aac(4) driver is being used to house files that are the backing store for a number of virtual disks. Each file is typically about 4GB. Under 4.11 using the vn(4) driver I see throughput of about 17MB/sec when writing to one of the virtual disks (using dd). Under 5.4 using the md(4) driver I only see throughput of about 7MB/sec when writing to the virtual disk. Tests were run using the exact same hardware. Is this something that might be caused by the aac(4) driver? or should I be looking at md(4)? Sorry for sending this twice..accidently sent before I was finished. -Glenn >Scott >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 11:22:12 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 6F6CD16A41F for ; Tue, 14 Jun 2005 11:22:12 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id E155243D53 for ; Tue, 14 Jun 2005 11:22:11 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-1) with ESMTP id j5EBM2iB024372; Tue, 14 Jun 2005 21:22:02 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-1) with ESMTP id j5EBLxOg027395; Tue, 14 Jun 2005 21:22:00 +1000 Date: Tue, 14 Jun 2005 21:22:01 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Glenn Dawson In-Reply-To: <6.1.0.6.2.20050613235825.09e52810@cobalt.antimatter.net> Message-ID: <20050614211046.G38218@delplex.bde.org> References: <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> <20050613121915.C25098@p-i-n.com> <20050614015958.GA33865@nargothrond.kdm.org> <42AE5ED7.8070309@samsco.org> <6.1.0.6.2.20050613235825.09e52810@cobalt.antimatter.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 11:22:12 -0000 On Tue, 14 Jun 2005, Glenn Dawson wrote: > This is a little OT for this thread, but I'm currently trying to solve a > problem which might be related to the aac driver, so I'll toss this out there > and see if anyone has any ideas for me. It seems to be very OT :-). > It trying to make the transition from 4.x to 5.x I've noticed that > performance of the md(4) (in 5.x) driver seems to be much worse than the > vn(4) driver under 4.x. > > Here's the scenario: > > A pair of mirrored disks on an adaptec 2120S using the aac(4) driver is being > used to house files that are the backing store for a number of virtual disks. > Each file is typically about 4GB. > > Under 4.11 using the vn(4) driver I see throughput of about 17MB/sec when > writing to one of the virtual disks (using dd). > > Under 5.4 using the md(4) driver I only see throughput of about 7MB/sec when > writing to the virtual disk. This seems to be from sync writes now being the default for md. Try using "mdconfig -o async ...". I will reply with more details to your message in freebsd-performnance. Bruce From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 14 17:10:08 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 459F816A41C for ; Tue, 14 Jun 2005 17:10:08 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B6B843D48 for ; Tue, 14 Jun 2005 17:10:08 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 5E74D64B953 for ; Tue, 14 Jun 2005 14:10:07 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 11981-04 for ; Tue, 14 Jun 2005 17:10:06 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id F1B1164B809 for ; Tue, 14 Jun 2005 14:10:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id BB8B139771; Tue, 14 Jun 2005 14:10:06 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id B89D337DDF for ; Tue, 14 Jun 2005 14:10:06 -0300 (ADT) Date: Tue, 14 Jun 2005 14:10:06 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20050614140507.C90456@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: SCSI controller recommendation ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 17:10:08 -0000 G'day ... I'm just in the process of putting together a new server ... Intel SR1400 based, Dual Xeon ... the plan, at this time, is to make this my first 5.x based box, and am curious as to what is considered a *well supported and stable* card? Two of my 4.x servers are running Intel RAID controllers, and I just love the storcon CLI, since it provides me with everything I need, from the command line, to remote admin the machine, minus a set of hands to swap drives, including the 'real time' monitor of the drives ... So, I'd prefer something that has a similar CLI, in terms of functionality, but I also want something that is going to be rock solid with the operating system as well ... I like the Zero-Channel stuff ... smaller footprint ... since the motherboard already has the onboard SCSI ... but it would have to be a 0CH card that works with the Intel SE7520JR2 motherboard ... Recommendations? Thanks ... ---- 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 Wed Jun 15 07:33:13 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 9AC0616A41C; Wed, 15 Jun 2005 07:33:13 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from aposerv.p-i-n.com (aposerv.p-i-n.com [145.253.185.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3BFE43D48; Wed, 15 Jun 2005 07:33:12 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from p-i-n.com (inside.p-i-n.com [129.10.9.21]) by aposerv.p-i-n.com (8.12.11/8.12.11) with ESMTP id j5F7X9mt000539; Wed, 15 Jun 2005 09:33:09 +0200 (CEST) (envelope-from rabe@p-i-n.com) Received: (from rabe@localhost) by p-i-n.com (8.11.6/8.11.6) id j5F7X4491079; Wed, 15 Jun 2005 09:33:04 +0200 (CEST) (envelope-from rabe) Date: Wed, 15 Jun 2005 09:33:04 +0200 From: "Raphael H. Becker" To: "Kenneth D. Merry" Message-ID: <20050615093304.D25098@p-i-n.com> References: <20050608152459.BF24E16A45C@hub.freebsd.org> <1118248386.7479.10.camel@zappa.Chelsea-Ct.Org> <20050608171130.GA64736@over-yonder.net> <1118252322.7479.28.camel@zappa.Chelsea-Ct.Org> <20050609113616.I41471@p-i-n.com> <20050609130511.GA732@uk.tiscali.com> <20050610162814.A25098@p-i-n.com> <20050610150718.GA7005@nargothrond.kdm.org> <20050612002508.B25098@p-i-n.com> <20050612035440.GA21262@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20050612035440.GA21262@nargothrond.kdm.org>; from ken@freebsd.org on Sat, Jun 11, 2005 at 09:54:40PM -0600 Organization: PHOENIX Pharmahandel AG & Co KG, Mannheim, Deutschland Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Accessing SCSI-Devices >2TB X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 07:33:13 -0000 On Sat, Jun 11, 2005 at 09:54:40PM -0600, Kenneth D. Merry wrote: > On Sun, Jun 12, 2005 at 00:25:08 +0200, Raphael H. Becker wrote: > > The support told me, SuSE Linux is known to work with >2TB in one device, > > means they might have some patches to work around. I will try a SuSE > > live system next days just to get sure it works. But the System won't > > be SuSE in future. > > It would be interesting to see whether that works. That would help narrow > down the problem slightly. I had some things to seek out last days. First, it doesn't work with SuSE 9.2 Live system! See http://rabe.uugrn.org/temp/FreeBSD/bigraid/dmesg.suse92_onebig.txt [...] scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs (scsi1:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit) Vendor: IFT Model: A12U-G2421 Rev: 342D Type: Direct-Access ANSI SCSI revision: 03 scsi1:A:0:0: Tagged Queuing enabled. Depth 32 [...] sdb : very big device. try to use READ CAPACITY(16). sdb : READ CAPACITY(16) failed. sdb : status=0, message=00, host=5, driver=00 sdb : use 0xffffffff as device size SCSI device sdb: 4294967296 512-byte hdwr sectors (2199023 MB) SCSI device sdb: drive cache: write back sdb:<6>tg3.c:v3.9 (August 30, 2004) ACPI: PCI interrupt 0000:03:06.0[A] -> GSI 7 (level, low) -> IRQ 7 unknown partition table Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 [...] Some mail with the RAID's distributor and his manufacturers support I got the information in Linux(!) the support depends on the scsi controllers (kernel)driver and (just?) LSI cards are know to work with LBA64 under linux this time. So the manufacturers position is "it works if you support LBA64 on the host". > > # camcontrol debug -c 1:0 > > # camcontrol rescan 1 > > Re-scan of bus 1 was successful > > > > in /var/log/messages: > > Hmm, well, you're not going to see the problem CDB that way, because the > probe has already happened. To see it, you either need to compile in the > debugging flags, or do the following: > > - unplug the cable from the machine to the RAID array > - camcontrol rescan 1 > - plug the cable back in > - camcontrol rescan 1 Did: - remote disconnected the RAID via internal controller - camcontrol rescan 1 - camcontrol devlist (RAID disappeared) - remote attach the RAID - turn on debugging - camcontrol rescan 1 (needed some time) - camcontrol devlist (RAID reemerged) See http://rabe.uugrn.org/temp/FreeBSD/bigraid/freebsd54_camdebug_rescan.txt > It's either the RAID box or the ahc driver from what I can see at this > point. See below. [...] > So this pretty much means it is the 16 byte read capacity that is > triggering the problem. > > The question is, is this problem on the RAID box or in the ahc driver? I > would lean towards saying the RAID box has the issue, but Justin (CCed) may > be able to give a little more insight. According to the manufacturer it just depends on the controllers LBA64 support. Regards Raphael Becker From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 15 08:02:12 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 44BBC16A41C for ; Wed, 15 Jun 2005 08:02:12 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (plab.ku.dk [130.225.107.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07BBF43D1F for ; Wed, 15 Jun 2005 08:02:12 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (Postfix) with SMTP id 2977A5623F6 for ; Wed, 15 Jun 2005 10:02:10 +0200 (CEST) Received: from [130.225.107.63] (eagle.plab.ku.dk [130.225.107.63]) by plab.ku.dk (Postfix) with ESMTP id 921B15623C2 for ; Wed, 15 Jun 2005 10:02:10 +0200 (CEST) Message-ID: <42AFE081.9040003@plab.ku.dk> Date: Wed, 15 Jun 2005 10:02:09 +0200 From: Anatoliy Dmytriyev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: asr-utils under 5.4 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 08:02:12 -0000 Hello everybody! I have found that port sysutils/asr-utils does not work under FreeBSD 5.4. Maybe somebody can recommend any other software for checking status of a RAID? (I'm using card Adaptec 2110S) Regards, Anatoliy Dmytriyev. -- Anatoliy Dmytriyev From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 15 13:33:06 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 DCBFF16A41C for ; Wed, 15 Jun 2005 13:33:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 812D843D53 for ; Wed, 15 Jun 2005 13:33:06 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j5FDbdU5018452; Wed, 15 Jun 2005 07:37:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42B02D7A.4040600@samsco.org> Date: Wed, 15 Jun 2005 07:30:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anatoliy Dmytriyev References: <42AFE081.9040003@plab.ku.dk> In-Reply-To: <42AFE081.9040003@plab.ku.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: asr-utils under 5.4 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 13:33:07 -0000 Anatoliy Dmytriyev wrote: > Hello everybody! > > I have found that port sysutils/asr-utils does not work under FreeBSD > 5.4. Maybe somebody can recommend any other software for checking status > of a RAID? > (I'm using card Adaptec 2110S) > > Regards, > Anatoliy Dmytriyev. > I thought that it was fixed. What doesn't work? Scott From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 15 13:46:53 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 F2AEB16A41C for ; Wed, 15 Jun 2005 13:46:52 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (plab.ku.dk [130.225.107.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B171E43D1F for ; Wed, 15 Jun 2005 13:46:52 +0000 (GMT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (Postfix) with SMTP id BCE565623F7 for ; Wed, 15 Jun 2005 15:46:51 +0200 (CEST) Received: from [130.225.107.63] (eagle.plab.ku.dk [130.225.107.63]) by plab.ku.dk (Postfix) with ESMTP id 8E3125623F6 for ; Wed, 15 Jun 2005 15:46:49 +0200 (CEST) Message-ID: <42B03149.1080206@plab.ku.dk> Date: Wed, 15 Jun 2005 15:46:49 +0200 From: Anatoliy Dmytriyev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <42AFE081.9040003@plab.ku.dk> <42B02D7A.4040600@samsco.org> In-Reply-To: <42B02D7A.4040600@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: asr-utils under 5.4 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 13:46:53 -0000 Scott Long wrote: > Anatoliy Dmytriyev wrote: > >> Hello everybody! >> >> I have found that port sysutils/asr-utils does not work under FreeBSD >> 5.4. Maybe somebody can recommend any other software for checking >> status of a RAID? >> (I'm using card Adaptec 2110S) >> >> Regards, >> Anatoliy Dmytriyev. >> > > I thought that it was fixed. What doesn't work? > > Scott future# /usr/local/bin/raidutil -L Engine connect failed: COMPATILITY number future# /usr/local/bin/raidutil -L all Engine connect failed: COMPATILITY number future# /usr/local/bin/raidutil -L physical Engine connect failed: COMPATILITY number future# dmesg | grep asr asr0: mem 0xf4000000-0xf5ffffff irq 21 at device 9.0 on pci2 asr0: ADAPTEC 2110S FW Rev. 380E, 1 channel, 256 CCBs, Protocol I2O da0 at asr0 bus 0 target 1 lun 0 Anatoliy -- Anatoliy Dmytriyev