From owner-freebsd-scsi@FreeBSD.ORG Sun Mar 1 18:51:20 2009 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CFA0106568A; Sun, 1 Mar 2009 18:51:20 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E57468FC1C; Sun, 1 Mar 2009 18:51:19 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n21IpJoG069604; Sun, 1 Mar 2009 18:51:19 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n21IpJYf069600; Sun, 1 Mar 2009 18:51:19 GMT (envelope-from gavin) Date: Sun, 1 Mar 2009 18:51:19 GMT Message-Id: <200903011851.n21IpJYf069600@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-scsi@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/132206: [mpt] system panics on boot when mirroring and 2nd drive is resyncing 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, 01 Mar 2009 18:51:20 -0000 Old Synopsis: mpt driver: system panics on boot when mirroring and 2nd drive is resyncing New Synopsis: [mpt] system panics on boot when mirroring and 2nd drive is resyncing Responsible-Changed-From-To: freebsd-i386->freebsd-scsi Responsible-Changed-By: gavin Responsible-Changed-When: Sun Mar 1 18:48:04 UTC 2009 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=132206 From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 11:07:09 2009 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3BCF106564A for ; Mon, 2 Mar 2009 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D714B8FCC9 for ; Mon, 2 Mar 2009 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n22B6xoL057440 for ; Mon, 2 Mar 2009 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n22B6xYo057436 for freebsd-scsi@FreeBSD.org; Mon, 2 Mar 2009 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Mar 2009 11:06:59 GMT Message-Id: <200903021106.n22B6xYo057436@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org 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, 02 Mar 2009 11:07:41 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/131032 scsi [panic] hald causing panic in scsi_sg o kern/130735 scsi [cam] [patch] pass M_NOWAIT to the malloc() call insid o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/126866 scsi [isp] [panic] kernel panic on card initialization o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o kern/123666 scsi [aac] attach fails with Adaptec SAS RAID 3805 controll o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/40895 scsi wierd kernel / device driver bug o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 34 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 12:44:18 2009 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35AAD106566B; Mon, 2 Mar 2009 12:44:18 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0DA888FC1C; Mon, 2 Mar 2009 12:44:18 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n22CiHtH039931; Mon, 2 Mar 2009 12:44:17 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n22CiHQq039927; Mon, 2 Mar 2009 12:44:17 GMT (envelope-from linimon) Date: Mon, 2 Mar 2009 12:44:17 GMT Message-Id: <200903021244.n22CiHQq039927@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-scsi@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/132250: [ciss] ciss driver does not support more then 15 drives 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, 02 Mar 2009 12:44:19 -0000 Old Synopsis: ciss driver does not support more then 15 drives New Synopsis: [ciss] ciss driver does not support more then 15 drives Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 2 12:43:52 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=132250 From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 18:16:03 2009 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8C5F106566C for ; Mon, 2 Mar 2009 18:16:03 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 672338FC19 for ; Mon, 2 Mar 2009 18:16:03 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id B5C222D0F57 for ; Mon, 2 Mar 2009 12:56:52 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 02 Mar 2009 12:56:52 -0500 X-Sasl-enc: jSKWUe1fCi+NdFFOsoRQ5fejZY1C3effbDrdpr8C+gFl 1236016612 Received: from [10.0.1.198] (c-66-41-132-62.hsd1.mn.comcast.net [66.41.132.62]) by mail.messagingengine.com (Postfix) with ESMTPSA id 2793D394C8 for ; Mon, 2 Mar 2009 12:56:52 -0500 (EST) Message-Id: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> From: Josh Paetzel To: freebsd-scsi@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 2 Mar 2009 11:56:50 -0600 X-Mailer: Apple Mail (2.930.3) Cc: Subject: twa driver and 3ware 9690SA issues 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, 02 Mar 2009 18:16:04 -0000 This is somewhat of a repost from questions@, and I'm currently engaged with 3ware about this issue. I have several 3ware 9690SA SAS RAID controllers. This item is very similar to their 9650SE controller. It uses the same firmware and driver, the difference being it can handle SAS drives. Up until this point all of the arrays we've used with these drives have been RAID 1 arrays with 7200 RPM SATA drives, but recently we've started using 15,000 MBA series Fujitsu SAS drives in places. The arrays have always been detected as: da0: Fixed Direct Access SCSI-5 device da0: 100.000MB/s transfers Which wasn't that much of an issue, as SATA drives aren't capable of sustained sequential 100 MB/sec transfers anyways, but the SAS drives we are getting are supposedly capable of 180 Megs/sec and I'm not seeing it. I'm unsure of how to eliminate caching from the equation, simple tests like dd if=/dev/zero of=testfile bs=8m count=1000 seem to support what dmesg reports by returning 96 Meg/sec transfer rates 3ware has had me verify the savestor performance profile is set to performance, write-caching is enabled, and that I'm using the latest driver and firmware. root@erlang / ->tw_cli /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-1 OK - - - 135.031 ON ON VPort Status Unit Size Type Phy Encl-Slot Model ------------------------------------------------------------------------------ p0 OK u0 136.98 GB SAS 0 - FUJITSU MBA3147RC p1 OK u0 136.98 GB SAS 1 - FUJITSU MBA3147RC Name OnlineState BBUReady Status Volt Temp Hours LastCapTest --------------------------------------------------------------------------- bbu On Yes OK OK OK 0 xx-xxx- xxxx At this point I'd be happy to somehow verify the 100 MB/sec reported by dmesg as either the real link speed, or as a bogus number. This issue may have trickle down to 9650SE and 9550 series controllers, those also report 100 MB/sec links for me with SATA drives, and while that's well over the sequential capability of current SATA drives, it could be affecting cache transfer rates...not to mention RAID array configurations. This test can't be considered at all conclusive, as I ran it on a production server: root@markov / ->tw_cli /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-10 OK - - 64K 596.025 ON OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------- p0 OK u0 298.09 GB 625142448 WD-WCARW4254676 p1 OK u0 298.09 GB 625142448 WD-WCARW3480367 p2 OK u0 298.09 GB 625142448 WD-WCARW4254675 p3 OK u0 298.09 GB 625142448 WD-WCARW3479101 root@markov / ->grep da0 /var/run/dmesg.boot da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 100.000MB/s transfers da0: 610330MB (1249955840 512 byte sectors: 255H 63S/T 77806C) Trying to mount root from ufs:/dev/da0s1a root@markov /home/jpaetzel ->dd if=/dev/zero of=test bs=8m count=100 100+0 records in 100+0 records out 838860800 bytes transferred in 6.923690 secs (121158052 bytes/sec) Kind of what I expect, and faster than 100 Megs/sec Thanks, Josh Paetzel From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 19:44:15 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C43E1065863 for ; Mon, 2 Mar 2009 19:44:15 +0000 (UTC) (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 D32FE8FC0A for ; Mon, 2 Mar 2009 19:44:14 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n22JiAUq078813; Mon, 2 Mar 2009 12:44:11 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <49AC370A.1040700@samsco.org> Date: Mon, 02 Mar 2009 12:44:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Josh Paetzel References: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> In-Reply-To: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: twa driver and 3ware 9690SA issues 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, 02 Mar 2009 19:44:17 -0000 Josh Paetzel wrote: > This is somewhat of a repost from questions@, and I'm currently engaged > with 3ware about this issue. > > I have several 3ware 9690SA SAS RAID controllers. This item is very > similar to their 9650SE controller. It uses the same firmware and > driver, the difference being it can handle SAS drives. Up until this > point all of the arrays we've used with these drives have been RAID 1 > arrays with 7200 RPM SATA drives, but recently we've started using > 15,000 MBA series Fujitsu SAS drives in places. > > The arrays have always been detected as: > > da0: Fixed Direct Access SCSI-5 device > da0: 100.000MB/s transfers This 100.000MB/s number is fictitious. The driver is just filling in a dummy value. Filling in the real number would require the driver being able to query the card for the negotiated bus speed. I have no idea if that's possible for TWA given the programming information that is public for the card. > > Which wasn't that much of an issue, as SATA drives aren't capable of > sustained sequential 100 MB/sec transfers anyways, but the SAS drives we > are getting are supposedly capable of 180 Megs/sec and I'm not seeing > it. I'm unsure of how to eliminate caching from the equation, simple > tests like dd if=/dev/zero of=testfile bs=8m count=1000 seem to support > what dmesg reports by returning 96 Meg/sec transfer rates > FreeBSD limits individual I/O segments through the CAM subsystem to 64K. It can safely be raised to 128K via some patches that I have, and you will see a corresponding improvement in performance. I don't believe that it can be safely raised above that for the TWA controllers. Scott From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 19:52:19 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B9E9106570E for ; Mon, 2 Mar 2009 19:52:19 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id D58D78FC15 for ; Mon, 2 Mar 2009 19:52:18 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 1D7722D1074; Mon, 2 Mar 2009 14:52:18 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 02 Mar 2009 14:52:18 -0500 X-Sasl-enc: J/lLlD/rGL90rzxdXNyHOLhY1v+79uCFAkpg+NJ/gotn 1236023537 Received: from [10.0.1.198] (c-66-41-132-62.hsd1.mn.comcast.net [66.41.132.62]) by mail.messagingengine.com (Postfix) with ESMTPSA id 98BA93DB89; Mon, 2 Mar 2009 14:52:17 -0500 (EST) Message-Id: <49E31E02-E9B0-48EB-8B7A-0517C6501FC2@tcbug.org> From: Josh Paetzel To: Scott Long In-Reply-To: <49AC370A.1040700@samsco.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 2 Mar 2009 13:52:16 -0600 References: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> <49AC370A.1040700@samsco.org> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-scsi@freebsd.org Subject: Re: twa driver and 3ware 9690SA issues 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, 02 Mar 2009 19:52:19 -0000 On Mar 2, 2009, at 1:44 PM, Scott Long wrote: > Josh Paetzel wrote: >> This is somewhat of a repost from questions@, and I'm currently >> engaged with 3ware about this issue. >> I have several 3ware 9690SA SAS RAID controllers. This item is >> very similar to their 9650SE controller. It uses the same firmware >> and driver, the difference being it can handle SAS drives. Up >> until this point all of the arrays we've used with these drives >> have been RAID 1 arrays with 7200 RPM SATA drives, but recently >> we've started using 15,000 MBA series Fujitsu SAS drives in places. >> The arrays have always been detected as: >> da0: Fixed Direct Access SCSI-5 device >> da0: 100.000MB/s transfers > > This 100.000MB/s number is fictitious. The driver is just filling > in a > dummy value. Filling in the real number would require the driver > being > able to query the card for the negotiated bus speed. I have no idea > if that's possible for TWA given the programming information that is > public for the card. > >> Which wasn't that much of an issue, as SATA drives aren't capable >> of sustained sequential 100 MB/sec transfers anyways, but the SAS >> drives we are getting are supposedly capable of 180 Megs/sec and >> I'm not seeing it. I'm unsure of how to eliminate caching from the >> equation, simple tests like dd if=/dev/zero of=testfile bs=8m >> count=1000 seem to support what dmesg reports by returning 96 Meg/ >> sec transfer rates > > FreeBSD limits individual I/O segments through the CAM subsystem to > 64K. It can safely be raised to 128K via some patches that I have, > and > you will see a corresponding improvement in performance. I don't > believe that it can be safely raised above that for the TWA > controllers. > > Scott I'd like to try the patches. Where can I get them from? Thanks, Josh Paetzel From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 2 22:51:04 2009 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AA4E106566B for ; Mon, 2 Mar 2009 22:51:04 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD008FC13 for ; Mon, 2 Mar 2009 22:51:03 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 01DED17E6B; Tue, 3 Mar 2009 09:33:36 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.100] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id DF36C17E50; Tue, 3 Mar 2009 09:33:32 +1100 (EST) Message-ID: <49AC5EB3.4020601@modulus.org> Date: Tue, 03 Mar 2009 09:33:23 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Josh Paetzel , freebsd-scsi@FreeBSD.org References: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> In-Reply-To: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: twa driver and 3ware 9690SA issues 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, 02 Mar 2009 22:51:04 -0000 Josh Paetzel wrote: > Which wasn't that much of an issue, as SATA drives aren't capable of > sustained sequential 100 MB/sec transfers anyways As Scott said, this number is not reflective of actual negotiated rate, and is nothing to worry about. > u0 RAID-10 OK - - 64K 596.025 ON OFF > 838860800 bytes transferred in 6.923690 secs (121158052 bytes/sec) > Kind of what I expect, and faster than 100 Megs/sec Well, that's a RAID10 and capable of doing much faster than 120MB/s. Sorry, but you cannot expect anywhere near close to the theoretical unformatted maximum media transfer rate of the disks you're testing, especially under FreeBSD and UFS. Testing the raw disks doesn't necessarily help either because then there's no operating system read-ahead or write-caching, which is necessary to lower the latency between access requests. I don't believe you're getting any SCSI or 3ware problems - just FreeBSD kernel and filesystem issues. UFS is performance is a bit bizarre: for example I see faster sequential write speeds than read speeds! ZFS improves the situation alot and I get much closer to the theoritical max with my drives. To give you an idea of how much more efficient ZFS is: I had a 16 disk 3ware SATA RAID6, with UFS, and battery-backed cache. I converted to a 14 disk ZFS software RAIDZ2 with a smaller 3ware mirrored boot disk. Quick benchmarked using dd as follows: Creating a 6GB file: UFS+3ware=308mb/s ZFS=357mb/s Reading a 6GB file: UFS+3ware=113mb/s ZFS=424mb/s - Andrew From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 3 03:06:02 2009 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E8A51065678 for ; Tue, 3 Mar 2009 03:06:02 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id E730D8FC17 for ; Tue, 3 Mar 2009 03:06:01 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 163F12D0EC0; Mon, 2 Mar 2009 22:06:01 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 02 Mar 2009 22:06:01 -0500 X-Sasl-enc: yp14kPFIqAcw2F48U/ArWNnKz2vm4zOO4RfK5SNj+VBH 1236049560 Received: from [10.0.1.198] (c-66-41-132-62.hsd1.mn.comcast.net [66.41.132.62]) by mail.messagingengine.com (Postfix) with ESMTPSA id A075047B93; Mon, 2 Mar 2009 22:06:00 -0500 (EST) Message-Id: <89312829-73A5-463B-8F9C-8CC30FB262B1@tcbug.org> From: Josh Paetzel To: Andrew Snow In-Reply-To: <49AC5EB3.4020601@modulus.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 2 Mar 2009 21:05:58 -0600 References: <09CE3D22-431A-433F-9CAF-6896FF77DDB1@tcbug.org> <49AC5EB3.4020601@modulus.org> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-scsi@FreeBSD.org Subject: Re: twa driver and 3ware 9690SA issues 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, 03 Mar 2009 03:06:02 -0000 On Mar 2, 2009, at 4:33 PM, Andrew Snow wrote: > Josh Paetzel wrote: >> Which wasn't that much of an issue, as SATA drives aren't capable >> of sustained sequential 100 MB/sec transfers anyways > > As Scott said, this number is not reflective of actual negotiated > rate, and is nothing to worry about. Great, thanks. > >> u0 RAID-10 OK - - 64K 596.025 >> ON OFF >> 838860800 bytes transferred in 6.923690 secs (121158052 bytes/sec) >> Kind of what I expect, and faster than 100 Megs/sec > > Well, that's a RAID10 and capable of doing much faster than 120MB/s. > Hrmm, I was under the impression that a single read or write would only see the sequential transfer rate of one side of the stripe set, and that would be fairly close to 120 Megs/sec. > Sorry, but you cannot expect anywhere near close to the theoretical > unformatted maximum media transfer rate of the disks you're testing, > especially under FreeBSD and UFS. > No need to apologize. > Testing the raw disks doesn't necessarily help either because then > there's no operating system read-ahead or write-caching, which is > necessary to lower the latency between access requests. > > I don't believe you're getting any SCSI or 3ware problems - just > FreeBSD kernel and filesystem issues. > > UFS is performance is a bit bizarre: for example I see faster > sequential write speeds than read speeds! ZFS improves the situation > alot and I get much closer to the theoritical max with my drives. > > To give you an idea of how much more efficient ZFS is: I had a 16 > disk 3ware SATA RAID6, with UFS, and battery-backed cache. I > converted to a 14 disk ZFS software RAIDZ2 with a smaller 3ware > mirrored boot disk. > > Quick benchmarked using dd as follows: > > Creating a 6GB file: UFS+3ware=308mb/s ZFS=357mb/s > Reading a 6GB file: UFS+3ware=113mb/s ZFS=424mb/s > > > > - Andrew ZFS probably isn't an option for me. A lot of these systems max out at 8 gigs of RAM, and postgresql eats a huge chunk of that, also the controllers on the motherboard don't always report back drive failures to the OS, as well as have occasional failures detecting new drives when we need to hot swap, as well as having my biggest concern, no battery backed cache. :( My main question has been answered, the link speed that the driver reports is imaginary. Thanks, Josh Paetzel From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 4 18:11:13 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C973106564A for ; Wed, 4 Mar 2009 18:11:13 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (unknown [IPv6:2001:380:e06:127::53]) by mx1.freebsd.org (Postfix) with ESMTP id AFB898FC1C for ; Wed, 4 Mar 2009 18:11:12 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 71C7478C4B for ; Thu, 5 Mar 2009 03:11:11 +0900 (JST) Received: from artemis (unknown [192.168.2.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTP id 34EC178C4A for ; Thu, 5 Mar 2009 03:11:11 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: Date: Thu, 5 Mar 2009 03:11:08 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Virus-Scanned: ClamAV using ClamSMTP Subject: iSCSI initiator StatSN 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, 04 Mar 2009 18:11:13 -0000 Hello, I'm now writing an iSCSI target designed for multipath failover cluster node. I noticed that FreeBSD initiator (2.1.0) was not able to be connected. So I have two questions. My target send StatSN=0(taken from ExpStatSN in request) at first response. But next request still have ExpStatSN=0 in PDU. What value does expect for StatSN? An initial version of the target is send-pr as PR 132016. The latest version is uploaded on my site pointed by PR. I want to replace the distfile because of many bugs. Does anyone known how to replace the file in this PR? Thanks, -- Daisuke Aoyama