From owner-freebsd-scsi Mon Jul 19 1:12:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3]) by hub.freebsd.org (Postfix) with ESMTP id E4F8715145 for ; Mon, 19 Jul 1999 01:12:32 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix3.ix.netcom.com (8.8.4/8.8.4) id DAA05223; Mon, 19 Jul 1999 03:11:52 -0500 (CDT) Received: from sji-ca4-70.ix.netcom.com(205.186.212.198) by dfw-ix3.ix.netcom.com via smap (V1.3) id rma005219; Mon Jul 19 03:11:43 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id BAA71585; Mon, 19 Jul 1999 01:11:39 -0700 (PDT) Date: Mon, 19 Jul 1999 01:11:39 -0700 (PDT) Message-Id: <199907190811.BAA71585@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: ken@plutotech.com Cc: nisha@cs.berkeley.edu, scsi@FreeBSD.ORG In-reply-to: <199907142226.QAA41224@panzer.kdm.org> (ken@plutotech.com) Subject: Re: Question From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) References: <199907142226.QAA41224@panzer.kdm.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: "Kenneth D. Merry" Oops, I should have read the manpage more carefully. But still... * > camcontrol modepage -e -m 8 /dev/pass0 * Otherwise, camcontrol will probably reject /dev/pass0 as garbage and * default to editing mode page 8 on da0. Shouldn't it exit with an error instead of just silently ignoring it? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 5:14: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f135.hotmail.com [207.82.251.14]) by hub.freebsd.org (Postfix) with SMTP id BA35214F75 for ; Mon, 19 Jul 1999 05:14:00 -0700 (PDT) (envelope-from freenerd@hotmail.com) Received: (qmail 63024 invoked by uid 0); 19 Jul 1999 12:11:48 -0000 Message-ID: <19990719121148.63023.qmail@hotmail.com> Received: from 165.21.83.140 by www.hotmail.com with HTTP; Mon, 19 Jul 1999 05:11:47 PDT X-Originating-IP: [165.21.83.140] From: "Freedom Bert" To: scsi@freebsd.org Subject: Proliant 400 and Vikings II doing only 40MB/s Date: Mon, 19 Jul 1999 05:11:47 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I risked making a fool of myself, but I really have to ask this. I recently installed 3.2-stable on a brand new Compaq Proliant 400. It came with a built-in onboard SCSI, an Integrated Single Channel Wide-Ultra2 SCSI controller ( really a Symbios 53c895 ) I have a Vikings II 9.1s connected to this controller. All the default settings has been turned OFF, ie. ID=0, TP is OFF, SE is OFF. The SCSI cable is the same that came with the server, it has a terminator attached to the end. I think it is a correct cable. I know I have to make sure that I'm using LVD, but I have no idea how to configure it. That's no configuration program from the SCSI controller at all. I am expecting a 80MB/s trasnfer rate which I am not gettings, and I have run out of ideas/ things to try. Perhaps some kind soul who have knwoledge of similar setup can throw me some rope here. TIA. the relevant dmesg output follows: >ncr0: rev 0x02 int a irq 11 on pci2.4.0 >da0 at ncr0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-2 device >da0: 40.000MB/s transfers ( 20.000MHz, offset 31, 16bit), Tagged Queueing >Enabled >da0: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 5:37: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id CFDAC14D53 for ; Mon, 19 Jul 1999 05:37:00 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by proteus.eclipse.net.uk (Postfix) with ESMTP id E7F9D9B04; Mon, 19 Jul 1999 13:36:55 +0100 (BST) Message-ID: <37931C2E.FD9EF230@eclipse.net.uk> Date: Mon, 19 Jul 1999 13:38:06 +0100 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en-GB MIME-Version: 1.0 To: Freedom Bert Cc: scsi@freebsd.org Subject: Re: Proliant 400 and Vikings II doing only 40MB/s References: <19990719121148.63023.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It came with a built-in onboard SCSI, an Integrated Single Channel > Wide-Ultra2 SCSI controller ( really a Symbios 53c895 ) here is some rope :) I have used this on our webcache since 3.1-stable shortly before 3.1-release, as far as I can tell, it's been no less reliable than servers using identical hardware running at 40MB/s. add the following to your kernel config, options SCSI_NCR_DFLT_SYNC=10 you should probably make clean && make depend && make all when building it. da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) BTW for anyone interested: the 895 support in FreeBSD works on more machines (specifically, HP LH4r - not tried in raid mode just as a standard controller) than Linux (redhat6, which fails at loading scripts code stage). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 9:12:31 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 81C04151D5; Mon, 19 Jul 1999 09:12:29 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA70954; Mon, 19 Jul 1999 10:12:21 -0600 (MDT) (envelope-from ken) Message-Id: <199907191612.KAA70954@panzer.kdm.org> Subject: Re: Question In-Reply-To: <199907190811.BAA71585@silvia.hip.berkeley.edu> from Satoshi - Ports Wraith - Asami at "Jul 19, 1999 01:11:39 am" To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: Mon, 19 Jul 1999 10:12:21 -0600 (MDT) Cc: nisha@cs.berkeley.edu, scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi - Ports Wraith - Asami wrote... > * From: "Kenneth D. Merry" > > Oops, I should have read the manpage more carefully. But still... > > * > camcontrol modepage -e -m 8 /dev/pass0 > > * Otherwise, camcontrol will probably reject /dev/pass0 as garbage and > * default to editing mode page 8 on da0. > > Shouldn't it exit with an error instead of just silently ignoring it? That's harder than it sounds, due to the way arguments are parsed in camcontrol. In any case, assuming standard getopt behavior, why should camcontrol even detect the argument at the end? Once getopt sees something that doesn't start with a '-' and isn't an expected argument, it stops parsing arguments. I doubt most programs continue going down the command line to check for extraneous garbage arguments. The right solution is probably to elimniate da0 as the default device, and require the user to specify a device to act on. I've been planning on doing that for a while, but only in -current. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 10:43:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id DD25815244 for ; Mon, 19 Jul 1999 10:43:49 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 49077 invoked from network); 19 Jul 1999 15:56:30 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 19 Jul 1999 15:56:30 -0000 Message-ID: <37934AC2.76626974@pipeline.ch> Date: Mon, 19 Jul 1999 17:56:50 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: se@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Re: ncr0: queue is empty Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stefan Esser wrote: > > Do you need more information? What can I do? > > More info sent in separate mail (regarding test of whether the problem > was introduced with rev. 1.146 of ncr.c, although you are the only one > to report a problem after that change went in two months ago ...) > > Your problem report keeps me from merging 1.146 from -current into > -stable. This means, that U2W support will be missing from -stable for > another week. Hi Stefan Going back to ncr.c rev. 1.145 did not solve the problem. I still got one "ncr0: queue empty" so far. I'm fairly certain that it is not related to any bugs in the quantum firmware because it was working fine for more than 7 month with -current (I remade world and kernel all 2-3 weeks). Are there any other things that changed in CAM which might trigger this behaviour in the ncr driver? I'm cvsupping today for the latest and greatest current and will see what happens. Cheers -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 18:48:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 8C09015112 for ; Mon, 19 Jul 1999 18:48:43 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id VAA07328; Mon, 19 Jul 1999 21:48:03 -0400 (EDT) (envelope-from mi) Message-Id: <199907200148.VAA07328@misha.cisco.com> Subject: Re: SEAGATE ST34371W on an NCR -- slow :( In-Reply-To: <19990714163904.17891@mojave.lemis.com> from Greg Lehey at "Jul 14, 1999 04:39:04 pm" To: Greg Lehey Date: Mon, 19 Jul 1999 21:48:03 -0400 (EDT) Cc: scsi@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey once wrote: > > I'm getting a dissapointingly low performance from the only disk on the > > ncr0: > > > > ncr0: rev 0x37 int a irq 21 on pci0.13.0 > > ncr1: rev 0x37 int b irq 22 on pci0.13.1 > > [...] > > da0 at ncr0 bus 0 target 3 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing E. > > da0: 52MB (8496884 512 byte sectors: 255H 63S/T 528C) > > > > This is a dual PII-300MHz system with 64Mb of RAM running FreeBSD > > 3.2-STABLE from Wed Jul 7. > > > > The iozone's numbers are: > > > > File size set to 80000 KB > > Time Resolution = 0.000015 seconds. > > Processor cache size set to 1024 Kbytes. > > Processor cache line size set to 32 bytes. > > File stride size set to 17 * record size. > > > > random random > > KB reclen write rewrite read reread read write > > 80000 4 3885 1460 4842 4474 415 208 > > > > bkwd record stride > > read rewrite read fwrite frewrite fread freread > > 988 135635 543 5235 1533 4674 4803 > > > > Big things, like Netscape and KDE take very long to start up, probably > > even longer then they used to take on my older P90 system with the same > > amount of RAM. > > > > What should I be tuning? Thanks! > > I'd be interested to see what results rawio shows. It bypasses the > buffer cache and measures raw disk performance. Take a look at > ftp://ftp.lemis.com/pub/rawio.tar.gz. root@guest:~ (148) rawio -I "Dual-One-SETI@Home" /dev/rda0s1e Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec Dual-One-SETI@Home Child 0 Bad read at 1511671296: (null) (671939037) Child 1 Bad read at 382283264: (null) (671939037) Child 2 Bad read at 1870251520: (null) (671939037) Child 3 Bad read at 1451056128: (null) (671939037) Child 5 Bad read at 1095859200: (null) (671939037) Child 4 Bad read at 2002068480: (null) (671939037) Child 6 Bad read at 559927808: (null) (671939037) Child 7 Bad read at 1127489024: (null) (671939037) 0.0 0 4394.9 268 I wonder what this "Bad read" s are about.... The device is typicly used as my /tmp. THe second run gives: root@guest:~ (149) rawio /dev/rda0s1e Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec anon Child 0 Bad read at 1890011136: (null) (671939037) Child 1 Bad read at 1000460800: (null) (671939037) Child 2 Bad read at 475668480: (null) (671939037) Child 3 Bad read at 230313472: (null) (671939037) Child 4 Bad read at 1622021632: (null) (671939037) Child 5 Bad read at 460020224: (null) (671939037) Child 6 Bad read at 1155239424: (null) (671939037) Child 7 Bad read at 748593664: (null) (671939037) 0.0 0 3976.9 243 root@guest:~ (150) rawio -I all -a /dev/rda0s1e Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec all Child 0 Bad read at 1311602688: (null) (671939037) Child 1 Bad read at 518595584: (null) (671939037) Child 2 Bad read at 1612716032: (null) (671939037) Child 3 Bad read at 1718660608: (null) (671939037) Child 4 Bad read at 934173696: (null) (671939037) Child 5 Bad read at 365423104: (null) (671939037) Child 6 Bad read at 1737638400: (null) (671939037) Child 7 Bad read at 622154752: (null) (671939037) 0.0 0 4153.1 253 Child 0 Bad write at 712240128: (null) (671939037) Child 1 Bad write at 2029816832: (null) (671939037) Child 2 Bad write at 1479277568: (null) (671939037) Child 3 Bad write at 1101784064: (null) (671939037) Child 4 Bad write at 741783040: (null) (671939037) Child 5 Bad write at 1680343552: (null) (671939037) Child 6 Bad write at 1918504448: (null) (671939037) Child 7 Bad write at 700973568: (null) (671939037) 0.0 0 1830.9 112 And finally, with the -v 2 setting: root@guest:~ (151) rawio -v 2 -I all -a /dev/rda0s1e Test name: all Transfer count: 16384 Record count: 16384 Process count: 8 Device size: 4350404608 Test ID Time KB/sec /sec %User %Sys %Total Reads Writes Child 1 Bad read at 754815488: (null) (671939037) Child 2 Bad read at 1117575168: (null) (671939037) Child 3 Bad read at 2136927744: (null) (671939037) Child 4 Bad read at 1750441472: (null) (671939037) Child 0 Bad read at 838010368: (null) (671939037) Child 5 Bad read at 1213815808: (null) (671939037) Child 7 Bad read at 792023552: (null) (671939037) Child 6 Bad read at 1504394240: (null) (671939037) RR all 0.049070 845.2 41 0.0 40.5 40.5 20 SR all 64.628578 4153.5 254 0.1 2.6 2.6 16384 0 Child 0 Bad write at 656580096: (null) (671939037) Child 3 Bad write at 1575190528: (null) (671939037) Child 2 Bad write at 1815015936: (null) (671939037) Child 4 Bad write at 1145159680: (null) (671939037) Child 5 Bad write at 1926565888: (null) (671939037) Child 1 Bad write at 696373760: (null) (671939037) Child 7 Bad write at 1483964928: (null) (671939037) Child 6 Bad write at 158612480: (null) (671939037) RW all 0.020574 1916.2 97 0.0 83.1 83.1 02 SW all 142.680023 1881.4 115 0.0 1.1 1.2 016384 Without the Seti@home, which was running on one of the CPUs at idprio 10 during the previous tests: root@guest:~ (155) rawio -v 2 -I NO-SETI -a /dev/rda0s1e Test name: NO-SETI Transfer count: 16384 Record count: 16384 Process count: 8 Device size: 4350404608 Test ID Time KB/sec /sec %User %Sys %Total Reads Writes Child 0 Bad read at 1404747264: (null) (671939037) Child 1 Bad read at 1404747264: (null) (671939037) Child 2 Bad read at 1538743808: (null) (671939037) Child 3 Bad read at 1702750208: (null) (671939037) Child 5 Bad read at 1468262912: (null) (671939037) Child 6 Bad read at 670607360: (null) (671939037) Child 7 Bad read at 1359508992: (null) (671939037) Child 4 Bad read at 957671424: (null) (671939037) RR NO-SETI 0.042906 716.0 47 0.0 61.7 61.7 20 SR NO-SETI 74.679314 3594.5 219 0.0 2.3 2.3 16384 0 Child 1 Bad write at 1859974144: (null) (671939037) Child 0 Bad write at 2059030528: (null) (671939037) Child 3 Bad write at 1325156352: (null) (671939037) Child 2 Bad write at 1457619456: (null) (671939037) Child 4 Bad write at 839265280: (null) (671939037) Child 5 Bad write at 1203342336: (null) (671939037) Child 6 Bad write at 2026992128: (null) (671939037) Child 7 Bad write at 162286592: (null) (671939037) RW NO-SETI 0.016841 1550.5 59 0.0 124.1 124.1 01 SW NO-SETI 143.285309 1873.4 114 0.0 1.2 1.2 016384 Thanks for ideas... Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 21:55:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from baklava.alt.net (baklava.alt.net [207.14.113.9]) by hub.freebsd.org (Postfix) with ESMTP id 14C1014D1C for ; Mon, 19 Jul 1999 21:55:09 -0700 (PDT) (envelope-from ccaputo@alt.net) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.9.3/8.7.3) with SMTP id VAA29498; Mon, 19 Jul 1999 21:55:02 -0700 (PDT) Date: Mon, 19 Jul 1999 21:55:00 -0700 (PDT) From: Chris Caputo To: freebsd-scsi@freebsd.org Subject: hard lockups with 3.2-STABLE and ASUS P2B-LS onboard AIC-7890 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeing crashes consisting of hard lockups when pushing lots of disk i/o (doing a "dump" of /usr for example) on a 3.2-STABLE system using the ASUS P2B-LS on board SCSI (AIC-7890). When the crash happens, the SCSI activity light on the motherboard and the active drive stay lit. ctrl-alt-del gets no response. What is the recommended way for debugging this? Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 19 21:59:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4977B1516E for ; Mon, 19 Jul 1999 21:59:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA03826; Mon, 19 Jul 1999 21:54:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907200454.VAA03826@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Caputo Cc: freebsd-scsi@freebsd.org Subject: Re: hard lockups with 3.2-STABLE and ASUS P2B-LS onboard AIC-7890 In-reply-to: Your message of "Mon, 19 Jul 1999 21:55:00 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 21:54:09 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am seeing crashes consisting of hard lockups when pushing lots of disk > i/o (doing a "dump" of /usr for example) on a 3.2-STABLE system using the > ASUS P2B-LS on board SCSI (AIC-7890). When the crash happens, the SCSI > activity light on the motherboard and the active drive stay lit. > ctrl-alt-del gets no response. > > What is the recommended way for debugging this? Buy a PCI bus analyser, or a new motherboard. Typically the symptoms you're describing are the result of hard PCI bus lockups of one kind or another. You might try some unscientific tweaking of the PCI bus parameters (latency, as well as positioning of cards) to see if you can make it go away. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 20 5:24:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mproxy.zedo.fuedo.de (mproxy.zedo.fuedo.de [193.99.167.226]) by hub.freebsd.org (Postfix) with ESMTP id E792614CEC; Tue, 20 Jul 1999 05:23:32 -0700 (PDT) (envelope-from hartung@zkom.de) Received: from master.zkom.de (master.zkom.de [193.99.166.6]) by mproxy.zedo.fuedo.de (8.9.3/8.9.3) with ESMTP id OAA06937; Tue, 20 Jul 1999 14:23:28 +0200 (CEST) Received: from zkom.de (jack.zkom.de [193.99.166.10]) by master.zkom.de (8.9.1a/8.8.8) with ESMTP id OAA09902; Tue, 20 Jul 1999 14:23:28 +0200 (CEST) (envelope-from hartung@zkom.de) Message-ID: <37946BAC.34DF01F3@zkom.de> Date: Tue, 20 Jul 1999 14:29:32 +0200 From: Michael Hartung Organization: ZKOM GmbH, Germany, Fax: +49 (0) 231 9700474 X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: RAID-controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anybody tell me which SCSI RAID-controller is the best ( and cheapest ) one to implement RAID-1 under FreeBSD 3.x. What about the storage management software? Thanks in advance -- Michael Hartung |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | ZKOM GmbH | | State Diagnostics Systems | | and Computer Networks | | | | WWW: www.zkom.de (WebCam) | | | | Joseph-von-Fraunhofer Str. 20 | | D-44227 Dortmund | | Germany | | E-mail: hartung@zkom.de | | Phone: +49 (0)231 / 9700 336 | | Fax: +49 (0)231 / 9700 474 | | Mobile: +49 (0)172 / 67 70 522 | | | | AG Dortmund HRB 12918 | | Managing Director: Dipl.-Ing. Michael Hartung | |_______________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 20 11:37: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from 001101.zer0.org (001101.zer0.org [206.24.105.163]) by hub.freebsd.org (Postfix) with ESMTP id A6BCF14C9E; Tue, 20 Jul 1999 11:37:03 -0700 (PDT) (envelope-from gsutter@001101.zer0.org) Received: (from gsutter@localhost) by 001101.zer0.org (8.9.2/8.9.2) id LAA76307; Tue, 20 Jul 1999 11:35:46 -0700 (PDT) (envelope-from gsutter) Date: Tue, 20 Jul 1999 11:35:46 -0700 From: Gregory Sutter To: Michael Hartung Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: RAID-controller Message-ID: <19990720113546.K45481@001101.zer0.org> References: <37946BAC.34DF01F3@zkom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37946BAC.34DF01F3@zkom.de>; from Michael Hartung on Tue, Jul 20, 1999 at 02:29:32PM +0200 Organization: Zer0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 20, 1999 at 02:29:32PM +0200, Michael Hartung wrote: > > Can anybody tell me which SCSI RAID-controller is the best ( and > cheapest ) one to implement RAID-1 under FreeBSD 3.x. What about the > storage management software? vinum(8) is the best software method, which would certainly be the cheapest. It's included in the base FreeBSD system. Any SCSI-SCSI RAID controller will work under FreeBSD. I personally have had good luck (and relatively cheap prices) with Infortrend, . It is likely that no vendor's storage management software will work under FreeBSD. Greg -- Gregory S. Sutter Cole's Law: Thinly sliced cabbage. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 2:38: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (Postfix) with ESMTP id 147431547F for ; Wed, 21 Jul 1999 02:38:04 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id EAA06653 for ; Wed, 21 Jul 1999 04:38:00 -0500 (CDT) Received: from sji-ca4-70.ix.netcom.com(205.186.212.198) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma006648; Wed Jul 21 04:37:37 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id CAA96811; Wed, 21 Jul 1999 02:37:32 -0700 (PDT) Date: Wed, 21 Jul 1999 02:37:32 -0700 (PDT) Message-Id: <199907210937.CAA96811@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: scsi@freebsd.org Subject: error logs From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a question. I just saw some errors on the package building machine. Part of it looks like this: === : Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): MEDIUM ERROR info:3cf816 asc:11,0 Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): Unrecovered read error sks:80,9 Jul 21 02:25:40 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): RECOVERED ERROR info:3cf817 asc:17,2 Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): Recovered data with positive head offset sks:80,2 : === I assume the stuff after "CDB:" is the entire SCSI command (10-byte commands?), does this mean that the kernel got a medium error from the disk, retried the exact same read command and succeeded the second time, even though the disk had to do some internal fiddling ("positive head offset")? I also see a bunch of recovered error messages with no associated medium error messages. This probably means the disk is dying, right? Thanks, Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 7:30:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from db.geocrawler.com (db.gotocity.com [165.90.140.10]) by hub.freebsd.org (Postfix) with ESMTP id 16A1314DB1 for ; Wed, 21 Jul 1999 07:30:51 -0700 (PDT) (envelope-from nobody@db.geocrawler.com) Received: (from nobody@localhost) by db.geocrawler.com (8.8.8/8.8.8) id JAA13990; Wed, 21 Jul 1999 09:28:48 -0500 Date: Wed, 21 Jul 1999 09:28:48 -0500 Message-Id: <199907211428.JAA13990@db.geocrawler.com> To: freebsd-scsi@freebsd.org Subject: Eliant 820 tape problems From: "Geocrawler.com" Reply-To: "Carey Nairn" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message was sent from Geocrawler.com by "Carey Nairn" Be sure to reply to that address. Hi all, just trying to use dump to backup a FreeBSD-3.1R system to an ExaByte Eliant 820 drive. this is what I get when I try to use dump on the command line: dump 0uBf 4585536 /dev/nrsa0 / DUMP: Date of this level 0 dump: Thu Jul 15 00:40:56 1999 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rwd0s1a (/) to /dev/nrsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 21102 tape blocks on 0.00 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: write error 10120 blocks into volume 1 DUMP: Do you want to restart?: ("yes" or "no") I also get the following console messages: (sa0:aha0:0:4:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,5 asc:10,0 (sa0:aha0:0:4:0): ID CRC or ECC error (sa0:aha0:0:4:0): WRITE(06). CDB: a 0 0 28 0 0 (sa0:aha0:0:4:0): Deferred Error: HARDWARE FAILURE info:2800 csi:0,0,0,1 asc:10,0 (sa0:aha0:0:4:0): ID CRC or ECC error (sa0:aha0:0:4:0): WRITE(06). CDB: a 0 0 28 0 0 (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 (sa0:aha0:0:4:0): ID CRC or ECC error (sa0:aha0:0:4:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 (sa0:aha0:0:4:0): ID CRC or ECC error (sa0:aha0:0:4:0): failure at writing filemarks - opting for safety (sa0:aha0:0:4:0): REWIND. CDB: 1 0 0 0 0 0 (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 (sa0:aha0:0:4:0): ID CRC or ECC error The SCSI system portion from dmesg is: aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 15 seconds for SCSI devices to settle sa0 at aha0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers changing root device to wd0s1a cd0 at aha0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [267400 x 2048 byte records] Any thought about why I can't write to the tape? cheers, Carey Nairn NB please reply to me at cpn@mailroom.dpac.tas.gov.au Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 8:36:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AB006154AC for ; Wed, 21 Jul 1999 08:35:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA82716; Wed, 21 Jul 1999 09:35:16 -0600 (MDT) (envelope-from ken) Message-Id: <199907211535.JAA82716@panzer.kdm.org> Subject: Re: error logs In-Reply-To: <199907210937.CAA96811@silvia.hip.berkeley.edu> from Satoshi Asami at "Jul 21, 1999 02:37:32 am" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 21 Jul 1999 09:35:16 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi Asami wrote... > Hi, > > I have a question. I just saw some errors on the package building > machine. Part of it looks like this: > > === > : > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): MEDIUM ERROR info:3cf816 asc:11,0 > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): Unrecovered read error sks:80,9 > Jul 21 02:25:40 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): RECOVERED ERROR info:3cf817 asc:17,2 > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): Recovered data with positive head offset sks:80,2 > : > === > > I assume the stuff after "CDB:" is the entire SCSI command (10-byte > commands?), Yes, that's the SCSI command. > does this mean that the kernel got a medium error from the > disk, retried the exact same read command and succeeded the second > time, even though the disk had to do some internal fiddling ("positive > head offset")? Well, the two errors above refer to two different blocks on the disk. The command in question was the same in both instances, but the two errors are for two different blocks. (see the info field on the second line of the error message, that tells you which block caused the problem) My guess is that the command was retried by some of the upper-level code or something, since CAM will generally only spit out one error for a command, and then only after the retry count (4 in this case) has been exhausted. So it looks like you've got one bad block, and one block that got recovered. > I also see a bunch of recovered error messages with no associated > medium error messages. This probably means the disk is dying, right? It could indeed mean the disk is dying. Make sure you have read and write reallocation turned on for the disk, and keep track of the grown defect list. (see the camcontrol man page for how to do that) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 9:37:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 83D8F154D6 for ; Wed, 21 Jul 1999 09:37:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA00715; Wed, 21 Jul 1999 09:30:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907211630.JAA00715@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: asami@cs.berkeley.edu (Satoshi Asami) Cc: scsi@freebsd.org Subject: Re: error logs In-reply-to: Your message of "Wed, 21 Jul 1999 02:37:32 PDT." <199907210937.CAA96811@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 09:30:25 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I have a question. I just saw some errors on the package building > machine. Part of it looks like this: > > === > : > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): MEDIUM ERROR info:3cf816 asc:11,0 > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): Unrecovered read error sks:80,9 This is a fatal read error. The kernel will retry it. > Jul 21 02:25:40 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): RECOVERED ERROR info:3cf817 asc:17,2 > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): Recovered data with positive head offset sks:80,2 > : This is the kernel-instigated retry, note that the read10 command is the same. The drive reports that it was able to recover the data but needed to adjust the head position in order to do so. > === > > I assume the stuff after "CDB:" is the entire SCSI command (10-byte > commands?), does this mean that the kernel got a medium error from the > disk, retried the exact same read command and succeeded the second > time, even though the disk had to do some internal fiddling ("positive > head offset")? > > I also see a bunch of recovered error messages with no associated > medium error messages. This probably means the disk is dying, right? It at least means that it's grown some defects. What I'm not seeing are any additions to the grown defects list, despite ARRE being set. 8( -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 11: 9:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id F412814C4C for ; Wed, 21 Jul 1999 11:09:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA83601; Wed, 21 Jul 1999 12:07:28 -0600 (MDT) (envelope-from ken) Message-Id: <199907211807.MAA83601@panzer.kdm.org> Subject: Re: error logs In-Reply-To: <199907211630.JAA00715@dingo.cdrom.com> from Mike Smith at "Jul 21, 1999 09:30:25 am" To: mike@smith.net.au (Mike Smith) Date: Wed, 21 Jul 1999 12:07:28 -0600 (MDT) Cc: asami@cs.berkeley.edu (Satoshi Asami), scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote... > > Hi, > > > > I have a question. I just saw some errors on the package building > > machine. Part of it looks like this: > > > > === > > : > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): MEDIUM ERROR info:3cf816 asc:11,0 > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): Unrecovered read error sks:80,9 > > This is a fatal read error. The kernel will retry it. If it gets retried, it gets retried above the CAM layer. When CAM prints out an error message, it almost always is after all retries have been completed. Read and write commands from the da driver have a retry count of 4. > > Jul 21 02:25:40 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): RECOVERED ERROR info:3cf817 asc:17,2 > > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): Recovered data with positive head offset sks:80,2 > > : > > This is the kernel-instigated retry, note that the read10 command is > the same. The drive reports that it was able to recover the data but > needed to adjust the head position in order to do so. The read command is the same, but the block referred to in this error message is different than the one above. See the info field. The read cdb above is two blocks in length. > > === > > > > I assume the stuff after "CDB:" is the entire SCSI command (10-byte > > commands?), does this mean that the kernel got a medium error from the > > disk, retried the exact same read command and succeeded the second > > time, even though the disk had to do some internal fiddling ("positive > > head offset")? > > > > I also see a bunch of recovered error messages with no associated > > medium error messages. This probably means the disk is dying, right? > > It at least means that it's grown some defects. What I'm not seeing > are any additions to the grown defects list, despite ARRE being set. 8( Read reallocation only works if the disk managed to salvage the data. If it can't salvage the data, it can't reallocate it. Write reallocation, IMO, should be successful much more often, because the kernel has the good data already. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 12: 1:42 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A624C155A1 for ; Wed, 21 Jul 1999 12:01:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id EAA01397; Wed, 21 Jul 1999 04:59:41 -0700 Date: Wed, 21 Jul 1999 12:00:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Carey Nairn Cc: freebsd-scsi@FreeBSD.org Subject: Re: Eliant 820 tape problems In-Reply-To: <199907211428.JAA13990@db.geocrawler.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 > (sa0:aha0:0:4:0): ID CRC or ECC error > (sa0:aha0:0:4:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 > (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 > (sa0:aha0:0:4:0): ID CRC or ECC error > (sa0:aha0:0:4:0): failure at writing filemarks - opting for safety > (sa0:aha0:0:4:0): REWIND. CDB: 1 0 0 0 0 0 > (sa0:aha0:0:4:0): HARDWARE FAILURE csi:0,0,0,1 asc:10,0 > (sa0:aha0:0:4:0): ID CRC or ECC error > > > > Any thought about why I can't write to the tape? > Check the manual. It's a Harcware failure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 21 17:50: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 5F6AD14F52 for ; Wed, 21 Jul 1999 17:50:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02949; Wed, 21 Jul 1999 17:43:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907220043.RAA02949@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: mike@smith.net.au (Mike Smith), asami@cs.berkeley.edu (Satoshi Asami), scsi@FreeBSD.ORG Subject: Re: error logs In-reply-to: Your message of "Wed, 21 Jul 1999 12:07:28 MDT." <199907211807.MAA83601@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 17:43:46 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote... > > > Hi, > > > > > > I have a question. I just saw some errors on the package building > > > machine. Part of it looks like this: > > > > > > === > > > : > > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): MEDIUM ERROR info:3cf816 asc:11,0 > > > Jul 21 02:25:39 bento /kernel: (da7:ahc1:0:4:0): Unrecovered read error sks:80,9 > > > > This is a fatal read error. The kernel will retry it. > > If it gets retried, it gets retried above the CAM layer. When CAM prints > out an error message, it almost always is after all retries have been > completed. Read and write commands from the da driver have a retry count > of 4. I'm aware of this. > > > Jul 21 02:25:40 bento /kernel: (da7:ahc1:0:4:0): READ(10). CDB: 28 0 0 3c f8 16 0 0 2 0 > > > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): RECOVERED ERROR info:3cf817 asc:17,2 > > > Jul 21 02:25:41 bento /kernel: (da7:ahc1:0:4:0): Recovered data with positive head offset sks:80,2 > > > : > > > > This is the kernel-instigated retry, note that the read10 command is > > the same. The drive reports that it was able to recover the data but > > needed to adjust the head position in order to do so. > > The read command is the same, but the block referred to in this error > message is different than the one above. See the info field. The read > cdb above is two blocks in length. Correct. The command failed the first time around, but not the second. Block 0x3cf816 was read successfully the second time, and 0x3cf817 was read after futzing around a bit. > > It at least means that it's grown some defects. What I'm not seeing > > are any additions to the grown defects list, despite ARRE being set. 8( > > Read reallocation only works if the disk managed to salvage the data. If > it can't salvage the data, it can't reallocate it. Write reallocation, > IMO, should be successful much more often, because the kernel has the good > data already. I would have expected to see a grown defect for 0x3cf817 somewhere in the grown defect list, however there isn't one before 0x5dd84b. I don't know where the threshold for reallocating a block is set on this disk (Quantum XP34301). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 10: 7:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from excalibur.lps.ens.fr (excalibur.lps.ens.fr [129.199.120.3]) by hub.freebsd.org (Postfix) with ESMTP id 912581535F for ; Thu, 22 Jul 1999 10:07:21 -0700 (PDT) (envelope-from Thierry.Besancon@lps.ens.fr) Received: from (besancon@localhost) by excalibur.lps.ens.fr (8.9.3/jtpda-5.3.1) id TAA27736 ; Thu, 22 Jul 1999 19:06:32 +0200 (MET DST) To: scsi@freebsd.org Subject: tagged openings Cc: besancon@lps.ens.fr From: Thierry.Besancon@lps.ens.fr Date: 22 Jul 1999 19:06:31 +0200 Message-ID: Lines: 122 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello I'm running FreeBSD 3.1 and whenever my workstation reboots I get the message : (da0:ncr0:0:0:0): tagged openings now 15 What does it mean ? I must say that I encounter scsi problems with this host but I can't find where they're coming from. Generally the machine freezes with messages saying ncr1 is on timeout. For example : ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). ncr1: script cmd = 89030000 ncr1: regdump: da 10 80 13 47 08 05 1f 03 09 85 ae 80 00 06 00. ncr1: have to clear fifos. ncr1: restart (fatal error). (sa0:ncr1:0:5:0): COMMAND FAILED (9 ff) @0xf0af9200. ncr1: timeout nccb=0xf0c79600 (skip) ncr1: timeout nccb=0xf0c79800 (skip) ncr1: timeout nccb=0xf0c79a00 (skip) Another one : ncr1:4:ERROR (81:0) (f-aa-0) (0/3) @ (script 3f0: 48000000) ncr1: script cmd = 7210000 ncr1: regdump: da 10 00 03 47 00 04 1f ff 0f 06 aa 80 00 0a 00 ncr1: target 4 doesn't release the bus ncr1:4: ERROR (0:41) (f-aa-00) (0/3) @ (script 3f0: 48000000) ncr1: script smd = 72100000 ncr1: regdump: da 10 00 03 47 00 04 1f ff 0f 06 aa 80 00 0a 00 ncr1: have to clear fifos ncr1: restrt (fatal error) (probe13:ncr1:0:6:0): COMMAND FAILED (9ff) @ 0xf0af9000 (probe13:ncr1:0:5:0): COMMAND FAILED (9ff) @ 0xf0af9000 (probe13:ncr1:0:4:0): COMMAND FAILED (9ff) @ 0xf0af9000 (probe13:ncr1:0:3:0): COMMAND FAILED (9ff) @ 0xf0af9000 (probe13:ncr1:0:2:0): COMMAND FAILED (9ff) @ 0xf0af9000 ncr1: timeout nccb=0xf0af9000 (skip) ncr1: timeout nccb=0xf0af9020 (skip) ncr1: timeout nccb=0xf0af9040 (skip) ncr1: timeout nccb=0xf0af9060 (skip) ncr1: timeout nccb=0xf0af9080 (skip) The precise configuration is 2 Tekram 390F cards + 2 towers of disks (4 disks each, IBM 9.1 Go), one DLT and one QUANTUM for the system : ncr0: rev 0x26 int a irq 9 on pci0.9.0 ncr1: rev 0x26 int a irq 12 on pci0.10.0 ... Waiting 3 seconds for SCSI devices to settle sa0 at ncr1 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.0MB/s transfers (10.0MHz, offset 15) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 1222MB (2503872 512 byte sectors: 255H 63S/T 155C) changing root device to da0s1a da9 at ncr1 bus 0 target 1 lun 0 da9: Fixed Direct Access SCSI-2 device da9: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da9: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da12 at ncr1 bus 0 target 4 lun 0 da12: Fixed Direct Access SCSI-2 device da12: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da12: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da11 at ncr1 bus 0 target 3 lun 0 da11: Fixed Direct Access SCSI-2 device da11: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da11: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da10 at ncr1 bus 0 target 2 lun 0 da10: Fixed Direct Access SCSI-2 device da10: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da10: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da3 at ncr0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da4 at ncr0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) The DLT is daisy chained with one UW tower and I don't use the narrow connector on the tekram 390F. If I do so, the workstation just freezes during the boot with an error like : ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). ncr1: script cmd = 89030000 ncr1: regdump: da 10 80 13 47 08 05 1f 03 09 85 ae 80 00 06 00. ncr1: have to clear fifos. ncr1: restart (fatal error). (sa0:ncr1:0:5:0): COMMAND FAILED (9 ff) @0xf0af9200. ncr1: timeout nccb=0xf0c79600 (skip) ncr1: timeout nccb=0xf0c79800 (skip) ncr1: timeout nccb=0xf0c79a00 (skip) I must say too that I had the same problems with the same PC in another configuration : the DLT was the same, the system disk was the same, all other disks were different and not UW, the scsi cards were NCR 810. The scsi bus goinf timeout is always the one with the DLT. Might it be faulty ? Thierry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 15:18:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 10E0815653 for ; Thu, 22 Jul 1999 15:18:13 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA29676; Thu, 22 Jul 1999 18:17:41 -0400 (EDT) Message-ID: <19990722181740.A29395@netmonger.net> Date: Thu, 22 Jul 1999 18:17:40 -0400 From: Christopher Masto To: scsi@freebsd.org Subject: OnStream status? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any news yet with the OnStream/ADR tape drives? The IDE model has been sitting in my machine for months, on the assumption that eventually I'd be able to at least get some programming info on it. At one point, supposedly they had released documentation. I would like a copy. It is not on OnStream's web site and they are still ignoring my e-mail. Does anyone know what the current status is? I have the drive, I have (very little) time, and I have the inclination to get it working. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 15:40:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A18814F0C for ; Thu, 22 Jul 1999 15:40:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA06248; Thu, 22 Jul 1999 15:39:50 -0700 Date: Thu, 22 Jul 1999 15:39:43 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christopher Masto Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? In-Reply-To: <19990722181740.A29395@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org in process On Thu, 22 Jul 1999, Christopher Masto wrote: > Any news yet with the OnStream/ADR tape drives? The IDE model has > been sitting in my machine for months, on the assumption that > eventually I'd be able to at least get some programming info on it. > > At one point, supposedly they had released documentation. I would > like a copy. It is not on OnStream's web site and they are still > ignoring my e-mail. Does anyone know what the current status is? > > I have the drive, I have (very little) time, and I have the > inclination to get it working. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 15:44:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id C07C214F0C for ; Thu, 22 Jul 1999 15:44:47 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA00990; Thu, 22 Jul 1999 18:42:30 -0400 (EDT) Message-ID: <19990722184229.A928@netmonger.net> Date: Thu, 22 Jul 1999 18:42:29 -0400 From: Christopher Masto To: mjacob@feral.com Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? References: <19990722181740.A29395@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Thu, Jul 22, 1999 at 03:39:43PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 22, 1999 at 03:39:43PM -0700, Matthew Jacob wrote: > > in process Is it a private party? I'd like to get involved, if possible. Particularly if the initial work is SCSI, as their IDE drive suffers from the same personality quirks. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 16: 0:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F1A0414DC6 for ; Thu, 22 Jul 1999 16:00:54 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA06340; Thu, 22 Jul 1999 16:00:51 -0700 Date: Thu, 22 Jul 1999 16:00:44 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Christopher Masto Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? In-Reply-To: <19990722184229.A928@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > in process > > Is it a private party? I'd like to get involved, if possible. > Particularly if the initial work is SCSI, as their IDE drive suffers > from the same personality quirks. Onstream has asked me to not release the documents, yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 16:24: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9866A14FEF for ; Thu, 22 Jul 1999 16:24:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA06406; Thu, 22 Jul 1999 16:19:26 -0700 Date: Thu, 22 Jul 1999 16:19:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Darryl Okahata Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? In-Reply-To: <199907222313.QAA09376@mina.sr.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > in process > > Is this for the IDE version? I thought that you were only going to > do SCSI support (it would be great if IDE drives were supported, though). No, this is scsi only. sos is doing ide (maybe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 16:48:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id BF29A14CE1 for ; Thu, 22 Jul 1999 16:48:40 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id QAA02535; Thu, 22 Jul 1999 16:13:07 -0700 (PDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id QAA01433; Thu, 22 Jul 1999 16:12:08 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id QAA09376; Thu, 22 Jul 1999 16:13:05 -0700 (PDT) Message-Id: <199907222313.QAA09376@mina.sr.hp.com> To: mjacob@feral.com Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 22 Jul 1999 15:39:43 PDT." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 22 Jul 1999 16:13:04 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org mjacob@feral.com wrote: > in process Is this for the IDE version? I thought that you were only going to do SCSI support (it would be great if IDE drives were supported, though). -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 17:17:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id BD93B14C27 for ; Thu, 22 Jul 1999 17:17:07 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel1.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id TAA15003; Thu, 22 Jul 1999 19:09:30 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id QAA01263; Thu, 22 Jul 1999 16:09:01 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id QAA08849; Thu, 22 Jul 1999 16:09:57 -0700 (PDT) Message-Id: <199907222309.QAA08849@mina.sr.hp.com> To: Christopher Masto Cc: scsi@FreeBSD.ORG Subject: Re: OnStream status? Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 22 Jul 1999 18:42:29 EDT." <19990722184229.A928@netmonger.net> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 22 Jul 1999 16:09:56 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher Masto wrote: > Is it a private party? I'd like to get involved, if possible. > Particularly if the initial work is SCSI, as their IDE drive suffers > from the same personality quirks. It's seriously funky. If anyone's curious, here's a copy of a message that I recently sent to Matthew (who's doing all of the FreeBSD work). -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. =============================================================================== I've been playing with it, and have the following comments: * The Echo software (the Windows-based software that comes with the OnStream drive) doesn't write tapes that's even vaguely close to the ADR development specification. The Echo software appears to be using it's own format. For example, the AUX data appears to be completely unused, and the configuration frames are different and are stored at a slightly different address (for the second, duplicate set of 5 blocks). * I see OnStream has announced a new "70GB" drive, and this drive will supposedly be Unix-compatible. However, I don't see how this drive can read current tapes unless it has a backward-compatibility mode. * If you know where the bad sectors are (presumably determined when writing -- I've only gotten as far as reading from the drive), skipping over the bad sectors seems to result in better performance. Given this, I'm wondering if it really makes sense to follow the ADR development specification. In particular, the AUX data is, well, tedious, and I'm wondering if it's really necessary. One can probably write a driver for it without following the ADR specs. I believe the Echo software does this. As far as compatibility goes, the new OnStream drive can either read old tapes, or it can't. If it can't, then we don't have to worry about the AUX data. If it can, then there probably has to be some kind of compatibility mode; if so, then a driver that one writes, can use the AUX data as it pleases. [ Of course, it is possible that the new drive will only read old tapes that follow the ADR dev specs. I don't think this will happen, though, as I think that this means that just about every existing tape will be unreadable in the new drive, because the current software doesn't follow the ADR specs. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 22: 7:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 237D314E3C for ; Thu, 22 Jul 1999 22:07:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA52341 for ; Thu, 22 Jul 1999 23:07:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA16334 for ; Thu, 22 Jul 1999 23:08:00 -0600 (MDT) Message-Id: <199907230508.XAA16334@harmony.village.org> Subject: Re: OnStream status? To: scsi@FreeBSD.ORG In-reply-to: Your message of "Thu, 22 Jul 1999 16:19:19 PDT." References: Date: Thu, 22 Jul 1999 23:08:00 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Matthew Jacob writes: : No, this is scsi only. sos is doing ide (maybe) Having read the document, it is best described as weird... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 22 23: 6:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id 103FD156A4 for ; Thu, 22 Jul 1999 23:06:27 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: (qmail 52493 invoked from network); 23 Jul 1999 06:05:46 -0000 Received: from yusufg.portal2.com (qmailr@203.85.226.249) by ns1.portal2.com with SMTP; 23 Jul 1999 06:05:46 -0000 Received: (qmail 30709 invoked by uid 500); 23 Jul 1999 06:06:03 -0000 Date: 23 Jul 1999 06:06:03 -0000 Message-ID: <19990723060603.30708.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-scsi@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Postmark results with DPT RAID-5 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid Ultra PM3334UW (Is there any standard mechanism or a methodology available for this). Any way, I am using the benchmark tool "Postmark" written by Network Appliance which is available via the URL http://www.netapp.com/technology/level3/3022.html. Here's the config of my NFS server running 3.2-stable from a few days ago PII 333 256mb ram Scsi 9 gig HDD Adaptec 2940UW scsi card. Intel Etherexpress 10/100 Mbps NIC DPT SmartRaid Ultra PM3334UW --> 6 x 18.6 Seagate Cheatah running RAID 5 The NFS client machine also running 3.2-stable from a few days PII 333 256mb ram Scsi 9 gig HDD Adaptec 2940UW scsi card. Intel Etherexpress 10/100 NIC nfs mount options: soft,rw Machines are connected via a 100 Mbps switch This is the postmark results for NFS (1000 initial files and 50,000 transactions). The 90GB filesystem mounted NFS has softupdated enabled on it Time: 520 seconds total 513 seconds of transactions (97 per second) Files: 25739 created (49 per second) Creation alone: 1000 files (166 per second) Mixed with transactions: 24739 files (48 per second) 25145 read (49 per second) 24602 appended (47 per second) 25739 deleted (49 per second) Deletion alone: 478 files (478 per second) Mixed with transactions: 25261 files (49 per second) Data: 160.78 megabytes read (309.20 kilobytes per second) 164.40 megabytes written (316.15 kilobytes per second) I also ran the benchmark on a soft-update local filesystem on the NFS client and these are the results Time: 187 seconds total 187 seconds of transactions (267 per second) Files: 25739 created (137 per second) Creation alone: 1000 files (1000 per second) Mixed with transactions: 24739 files (132 per second) 25145 read (134 per second) 24602 appended (131 per second) 25739 deleted (137 per second) Deletion alone: 478 files (478 per second) Mixed with transactions: 25261 files (135 per second) Data: 160.78 megabytes read (859.79 kilobytes per second) 164.40 megabytes written (879.12 kilobytes per second) If somebody else can also share their results using the "postmark" tool. I would appreciate it. Just want to get a feel if these numbers are good. I am planning to evaluate the Mylex DAC960SX SCSI-SCSI RAID also and shall post the numbers once I get the card Also, is there a way via camcontrol to simulate a disk failure so I can test RAID reconstruction Cheers, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 2:49:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3]) by hub.freebsd.org (Postfix) with ESMTP id 968D3156FB for ; Fri, 23 Jul 1999 02:49:31 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix3.ix.netcom.com (8.8.4/8.8.4) id EAA16533; Fri, 23 Jul 1999 04:48:30 -0500 (CDT) Received: from sji-ca4-70.ix.netcom.com(205.186.212.198) by dfw-ix3.ix.netcom.com via smap (V1.3) id rma016529; Fri Jul 23 04:48:07 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id CAA10870; Fri, 23 Jul 1999 02:48:01 -0700 (PDT) Date: Fri, 23 Jul 1999 02:48:01 -0700 (PDT) Message-Id: <199907230948.CAA10870@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: mike@smith.net.au Cc: ken@plutotech.com, mike@smith.net.au, scsi@FreeBSD.ORG In-reply-to: <199907220043.RAA02949@dingo.cdrom.com> (message from Mike Smith on Wed, 21 Jul 1999 17:43:46 -0700) Subject: Re: error logs From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) References: <199907220043.RAA02949@dingo.cdrom.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Mike Smith Ken says (" * > ") * > If it gets retried, it gets retried above the CAM layer. When CAM prints * > out an error message, it almost always is after all retries have been * > completed. Read and write commands from the da driver have a retry count * > of 4. So, if I see three lines of the standard read error but not anything else, can I assume that the kernel retried it and the disk successfully read the sector(s) the second time around without any hitch? * > The read command is the same, but the block referred to in this error * > message is different than the one above. See the info field. The read * > cdb above is two blocks in length. * * Correct. The command failed the first time around, but not the second. * Block 0x3cf816 was read successfully the second time, and 0x3cf817 was * read after futzing around a bit. Thanks, didn't know that. * I would have expected to see a grown defect for 0x3cf817 somewhere in * the grown defect list, however there isn't one before 0x5dd84b. I * don't know where the threshold for reallocating a block is set on this * disk (Quantum XP34301). As for this particular disk, I see the following message at about the time you sent this out: Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): READ DEFECT DATA(10). CDB: 37 0 0 0 0 0 0 fd e8 0 Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): RECOVERED ERROR asc:1c,0 Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): Defect list not found sks:80,0 Are you sure that the list itself isn't unreadable? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 4:17:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by hub.freebsd.org (Postfix) with ESMTP id B2B9B14ED4 for ; Fri, 23 Jul 1999 04:17:20 -0700 (PDT) (envelope-from wjw@iae.nl) Received: by surf.iae.nl (Postfix, from userid 74) id 5AD2F9725; Fri, 23 Jul 1999 13:16:49 +0200 (MET DST) To: yusufg@outblaze.com Subject: Re: Postmark results with DPT RAID-5 X-Newsgroups: list.freebsd.scsi In-Reply-To: <19990723060603.30708.qmail@yusufg.portal2.com> Organization: Internet Access Eindhoven Cc: scsi@freebsd.org Message-Id: <19990723111649.5AD2F9725@surf.iae.nl> Date: Fri, 23 Jul 1999 13:16:49 +0200 (MET DST) From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990723060603.30708.qmail@yusufg.portal2.com> you write: >Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid >Ultra PM3334UW (Is there any standard mechanism or a methodology >Also, is there a way via camcontrol to simulate a disk failure so I >can test RAID reconstruction I tried to eject the RAID-5 disk I have. :-) That started to kill drives. But it will invalidate all drivs. :-( We usually test this by turning of the power on one of the drives. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 6: 5:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0D1811571D for ; Fri, 23 Jul 1999 06:05:07 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA01486; Fri, 23 Jul 1999 14:55:03 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id OAA00647; Fri, 23 Jul 1999 14:35:07 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907231235.OAA00647@yedi.iaf.nl> Subject: Re: Postmark results with DPT RAID-5 In-Reply-To: <19990723111649.5AD2F9725@surf.iae.nl> from Willem Jan Withagen at "Jul 23, 1999 1:16:49 pm" To: wjw@iae.nl (Willem Jan Withagen) Date: Fri, 23 Jul 1999 14:35:07 +0200 (CEST) Cc: yusufg@outblaze.com, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Willem Jan Withagen wrote ... > In article <19990723060603.30708.qmail@yusufg.portal2.com> you write: > >Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid > >Ultra PM3334UW (Is there any standard mechanism or a methodology > > >Also, is there a way via camcontrol to simulate a disk failure so I > >can test RAID reconstruction > > I tried to eject the RAID-5 disk I have. :-) > That started to kill drives. But it will invalidate all drivs. :-( Lousy. Popping drives is what we tend to do on our Storageworks disks/arrays. > We usually test this by turning of the power on one of the drives. Should also work. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 7:14:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226]) by hub.freebsd.org (Postfix) with ESMTP id C136914D3B; Fri, 23 Jul 1999 07:14:41 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id KAA02981; Fri, 23 Jul 1999 10:14:27 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14232.30911.431405.352467@trooper.velocet.ca> Date: Fri, 23 Jul 1999 10:14:23 -0400 (EDT) To: Yusuf Goolamabbas Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Postmark results with DPT RAID-5 In-Reply-To: <19990723060603.30708.qmail@yusufg.portal2.com> References: <19990723060603.30708.qmail@yusufg.portal2.com> X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Yusuf" == Yusuf Goolamabbas writes: Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a Yusuf> methodology available for this). Any way, I am using the Yusuf> benchmark tool "Postmark" written by Network Appliance which is Yusuf> available via the URL Yusuf> http://www.netapp.com/technology/level3/3022.html. I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI drives. I found that for creating and deleting files, it couldn't be beat (Ports would untar 4 times faster, for instance). However, I found that a single 9G on a 2940UW would easily beat the raw throughput. I was dissapointed with this. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 8: 1: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 69F1E14D66; Fri, 23 Jul 1999 08:00:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id IAA94485; Fri, 23 Jul 1999 08:59:29 -0600 (MDT) (envelope-from ken) Message-Id: <199907231459.IAA94485@panzer.kdm.org> Subject: Re: error logs In-Reply-To: <199907230948.CAA10870@silvia.hip.berkeley.edu> from Satoshi - Ports Wraith - Asami at "Jul 23, 1999 02:48:01 am" To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: Fri, 23 Jul 1999 08:59:29 -0600 (MDT) Cc: mike@smith.net.au, scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi - Ports Wraith - Asami wrote... > * From: Mike Smith > > Ken says (" * > ") > * > If it gets retried, it gets retried above the CAM layer. When CAM prints > * > out an error message, it almost always is after all retries have been > * > completed. Read and write commands from the da driver have a retry count > * > of 4. > > So, if I see three lines of the standard read error but not anything > else, can I assume that the kernel retried it and the disk > successfully read the sector(s) the second time around without any > hitch? Maybe, maybe not. :) It depends on how the upper level code handles it. It may be that if the read failed, the upper level code passes back the error to the userland application that generated the request, and what happens then is up to the application. I really don't know what happens above CAM, someone else may have a clue, though. One thing to keep in mind is that once you get an error printout from the da driver, it has already retried the command 4 times. While it is possible that the command will succeed if retried again, I think it's unlikely. > * I would have expected to see a grown defect for 0x3cf817 somewhere in > * the grown defect list, however there isn't one before 0x5dd84b. I > * don't know where the threshold for reallocating a block is set on this > * disk (Quantum XP34301). > > As for this particular disk, I see the following message at about the > time you sent this out: > > Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): READ DEFECT DATA(10). CDB: 37 0 0 0 0 0 0 fd e8 0 > Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): RECOVERED ERROR asc:1c,0 > Jul 21 17:41:58 bento /kernel: (pass7:ahc1:0:4:0): Defect list not found sks:80,0 > > Are you sure that the list itself isn't unreadable? That error message sometimes gets printed out when the disk doesn't like the defect list format you asked for. Quantums usually support block format, but most every disk I've seen at least supports physical sector format. Most IBM and Seagate disks do not support block format. In some cases, if a drive doesn't support a given defect list format, it will send back the defect list in some other format. camcontrol attempts to deal with that scenario, if it can detect it. However it only ends up working in some cases, either because the drives use different error codes to indicate that they're returning a different defect list format, or because the drive won't return a defect list at all if you don't ask for one in a format it supports. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 8:13: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.ripco.com (relay.ripco.com [209.100.227.3]) by hub.freebsd.org (Postfix) with SMTP id 4537B14D54 for ; Fri, 23 Jul 1999 08:12:57 -0700 (PDT) (envelope-from aphor@ripco.com) Received: (qmail 25543 invoked from network); 23 Jul 1999 15:11:43 -0000 Received: from golden.ripco.com (aphor@209.100.227.10) by relay.ripco.com with SMTP; 23 Jul 1999 15:11:43 -0000 Date: Fri, 23 Jul 1999 10:11:42 -0500 (CDT) From: Jeremy McMillan To: mcmillan@cboe.com Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Postmark results with DPT RAID-5 In-Reply-To: <14232.30911.431405.352467@trooper.velocet.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 23 Jul 1999, David Gilbert wrote: > >>>>> "Yusuf" == Yusuf Goolamabbas writes: > > Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT > Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a > Yusuf> methodology available for this). Any way, I am using the > Yusuf> benchmark tool "Postmark" written by Network Appliance which is > Yusuf> available via the URL > Yusuf> http://www.netapp.com/technology/level3/3022.html. > > I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI > drives. I found that for creating and deleting files, it couldn't be > beat (Ports would untar 4 times faster, for instance). However, I > found that a single 9G on a 2940UW would easily beat the raw > throughput. I was dissapointed with this. Why is this so? How's your DPT cache configured? --- Jeremy McMillan | Finger for PGP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 10:48: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9EF5314C91; Fri, 23 Jul 1999 10:47:58 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id KAA88500; Fri, 23 Jul 1999 10:47:27 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199907231747.KAA88500@gndrsh.aac.dev.com> Subject: Re: Postmark results with DPT RAID-5 In-Reply-To: <14232.30911.431405.352467@trooper.velocet.ca> from David Gilbert at "Jul 23, 1999 10:14:23 am" To: dgilbert@velocet.ca (David Gilbert) Date: Fri, 23 Jul 1999 10:47:27 -0700 (PDT) Cc: yusufg@outblaze.com (Yusuf Goolamabbas), freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >>>>> "Yusuf" == Yusuf Goolamabbas writes: > > Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT > Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a > Yusuf> methodology available for this). Any way, I am using the > Yusuf> benchmark tool "Postmark" written by Network Appliance which is > Yusuf> available via the URL > Yusuf> http://www.netapp.com/technology/level3/3022.html. > > I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI > drives. I found that for creating and deleting files, it couldn't be > beat (Ports would untar 4 times faster, for instance). However, I > found that a single 9G on a 2940UW would easily beat the raw > throughput. I was dissapointed with this. This disparity is usually caused by the configuration of the stripe size or chunk factor set up for the raid array. Most default raid controller parameters are optimized for tps (transactions per second) not for aggregate data transfer rates. And an ever larger problem in optimizing raid arrays for raw throughput is the need to spindle sync the drives, with correct RPL Offsets, such that the SCSI commands and data can blast out the channel at full speed without incurring rotational delay per drive/chunk of transfer. This process requires a SCSI bus analyzer, logic analyzer and a lot of patients! -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 16:11:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226]) by hub.freebsd.org (Postfix) with ESMTP id A33AA1574B; Fri, 23 Jul 1999 16:10:27 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id SAA23757; Fri, 23 Jul 1999 18:56:43 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14232.62251.3136.872573@trooper.velocet.ca> Date: Fri, 23 Jul 1999 18:56:43 -0400 (EDT) To: Jeremy McMillan Cc: mcmillan@cboe.com, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Postmark results with DPT RAID-5 In-Reply-To: References: <14232.30911.431405.352467@trooper.velocet.ca> X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Jeremy" == Jeremy McMillan writes: Jeremy> On Fri, 23 Jul 1999, David Gilbert wrote: >> >>>>> "Yusuf" == Yusuf Goolamabbas writes: >> Yusuf> Hi, I am trying to stress test a DPT RAID controller DPT Yusuf> SmartRaid Ultra PM3334UW (Is there any standard mechanism or a Yusuf> methodology available for this). Any way, I am using the Yusuf> benchmark tool "Postmark" written by Network Appliance which is Yusuf> available via the URL Yusuf> http://www.netapp.com/technology/level3/3022.html. >> I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI >> drives. I found that for creating and deleting files, it couldn't >> be beat (Ports would untar 4 times faster, for instance). However, >> I found that a single 9G on a 2940UW would easily beat the raw >> throughput. I was dissapointed with this. Jeremy> Why is this so? How's your DPT cache configured? I talked with the driver author and somewhat determined that my level of performance was expected. When you think about it, the 3334 is a 68040 --- which can run as fast as 50Mhz. Now, I'm sure that they have other special hardware there, but the thruput bottleneck on the 3334 is likely the 68040. ... This would also probably be why later cards are based on RISC processors. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 17:31: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 8473314F01; Fri, 23 Jul 1999 17:30:50 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA06652; Sat, 24 Jul 1999 09:59:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA42234; Sat, 24 Jul 1999 09:59:30 +0930 (CST) Date: Sat, 24 Jul 1999 09:59:30 +0930 From: Greg Lehey To: Yusuf Goolamabbas Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Postmark results with DPT RAID-5 Message-ID: <19990724095930.H84734@freebie.lemis.com> References: <19990723060603.30708.qmail@yusufg.portal2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990723060603.30708.qmail@yusufg.portal2.com>; from Yusuf Goolamabbas on Fri, Jul 23, 1999 at 06:06:03AM -0000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 23 July 1999 at 6:06:03 -0000, Yusuf Goolamabbas wrote: > Hi, I am trying to stress test a DPT RAID controller DPT SmartRaid > Ultra PM3334UW (Is there any standard mechanism or a methodology > available for this). Any way, I am using the benchmark tool "Postmark" > written by Network Appliance which is available via the URL > http://www.netapp.com/technology/level3/3022.html. I've had a look at this benchmark. I don't understand why they want to do things this way. Many factors influence overall system throughput; if you want to measure only one part of it, measuring "real-life" performance is confusing. If you want to measure just the storage device throughput, look at rawio (ftp://ftp.lemis.com/pub/rawio.tar.gz). If you do use it, I'd be very interested in your results. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 23 18:37:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 27AC714DCA; Fri, 23 Jul 1999 18:37:20 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 117qjK-0000zH-00; Fri, 23 Jul 1999 18:36:02 -0700 Date: Fri, 23 Jul 1999 18:35:58 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: David Gilbert Cc: Jeremy McMillan , mcmillan@cboe.com, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Postmark results with DPT RAID-5 In-Reply-To: <14232.62251.3136.872573@trooper.velocet.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 23 Jul 1999, David Gilbert wrote: > >> I configured a DPT-3334UW on a K6-II/400 machine with 4 9G SCSI > >> drives. I found that for creating and deleting files, it couldn't > >> be beat (Ports would untar 4 times faster, for instance). However, > >> I found that a single 9G on a 2940UW would easily beat the raw > >> throughput. I was dissapointed with this. > > Jeremy> Why is this so? How's your DPT cache configured? > > I talked with the driver author and somewhat determined that my level > of performance was expected. When you think about it, the 3334 is a > 68040 --- which can run as fast as 50Mhz. Now, I'm sure that they > have other special hardware there, but the thruput bottleneck on the > 3334 is likely the 68040. Not too likely. The 68040 is a rather nice CPU. Especially since all RAID calculations are offloaded onto ASICs chips. The 68040 is basically just a SCSI command processor. > ... This would also probably be why later cards are based on RISC > processors. Not too likely. The RISC CPUs are just cheaper than using the next generation 680x0 series. DPT has pumped up their ASICs though. More likely you were using RAID5. RAID5 writing speed isn't so fast. > Dave. > > -- > ============================================================================ > |David Gilbert, Velocet Communications. | Two things can only be | > |Mail: dgilbert@velocet.net | equal if and only if they | > |http://www.velocet.net/~dgilbert | are precisely opposite. | > =========================================================GLO================ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 24 12: 9:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from jeeves.poopie.net (jeeves.poopie.net [151.198.231.29]) by hub.freebsd.org (Postfix) with ESMTP id 2537B14E59 for ; Sat, 24 Jul 1999 12:09:46 -0700 (PDT) (envelope-from pete@jeeves.poopie.net) Received: from localhost (pete@localhost) by jeeves.poopie.net (8.9.2/8.9.3) with ESMTP id PAA11745 for ; Sat, 24 Jul 1999 15:13:14 GMT Date: Sat, 24 Jul 1999 15:13:14 +0000 (GMT) From: Pedro Leitao To: freebsd-scsi@freebsd.org Subject: MAKEDEV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just added a new scsi backup tape drive on my server. I compiled the kernel, and the scsi card and tape drive now show up on startup as ahc0(card) and sa0(drive). I want to use that drive, but the device sa0 doesn't show in /dev. I am trying to make it with ./MAKEDEV sa0, but that just doesn't work. When I run ./MAKEDEV sa0 , it looks like it runs, but the sa0 device doesn't show in /dev/ How do I make the backup tape drive device so that I can use it? thanx in advance for any help.. _P_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 24 12:16:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6FE581522D for ; Sat, 24 Jul 1999 12:16:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA13147; Sat, 24 Jul 1999 12:13:54 -0700 Date: Sat, 24 Jul 1999 12:13:47 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Pedro Leitao Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: MAKEDEV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Try looking for 'rsa0'. On Sat, 24 Jul 1999, Pedro Leitao wrote: > > > I just added a new scsi backup tape drive on my server. > I compiled the kernel, and the scsi card and tape drive now show > up on startup as ahc0(card) and sa0(drive). > > I want to use that drive, but the device sa0 doesn't show in /dev. > I am trying to make it with ./MAKEDEV sa0, but that just doesn't work. > When I run ./MAKEDEV sa0 , it looks like it runs, but the sa0 device > doesn't show in /dev/ > > How do I make the backup tape drive device so that I can use it? > > thanx in advance for any help.. > _P_ > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message