From owner-freebsd-scsi Sun Jul 20 21:02:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA20136 for freebsd-scsi-outgoing; Sun, 20 Jul 1997 21:02:34 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20128 for ; Sun, 20 Jul 1997 21:02:25 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.6) id OAA24915 for freebsd-scsi@freebsd.org; Mon, 21 Jul 1997 14:02:16 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id NAA23642; Mon, 21 Jul 1997 13:57:54 +1000 (EST) Message-Id: <199707210357.NAA23642@ogre.dtir.qld.gov.au> To: freebsd-scsi@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: Disk activity light on Asus SC875 doesn't work References: In-Reply-To: from Dave Huang at "Sat, 19 Jul 1997 04:13:35 +0000" Date: Mon, 21 Jul 1997 13:57:54 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Saturday, 19th July 1997, Dave Huang wrote: >Hi there... I just got an Asus SC875 card (53c875 chip), and it seems to >be running great so far... except for one weird thing: the activity LED >doesn't work when in NetBSD. However, in MSDOS, Win95, and WinNT, it works >just fine. It's the same with the Diamond FirePort 40 (based on the 875J), so you aren't imagining it. It wasn't a useful indicator no matter which way I plugged in my LED. It's a real bummer because my new disk is too quiet. :-) Stephen. From owner-freebsd-scsi Sun Jul 20 23:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA26097 for freebsd-scsi-outgoing; Sun, 20 Jul 1997 23:45:16 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA26092 for ; Sun, 20 Jul 1997 23:45:13 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wqC6l-00011S-00; Sun, 20 Jul 1997 23:38:11 -0700 Date: Sun, 20 Jul 1997 23:38:10 -0700 (PDT) From: Tom Samplonius To: freebsd-scsi@freebsd.org Subject: DPT driver integration? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When is the DPT driver likely to be integrated into current, and later into 2.2.2? I wish I could try it, but my 3334UW doesn't seem to be able to save its array configuration (every time I run dptmgr, it says I have to do an initial setup, even though I've done it a dozen times). DPT claims it is probably a cabling problem, which sounds phony to me, as isn't the array configuration stored in NVRAM on the card? Tom From owner-freebsd-scsi Mon Jul 21 07:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17103 for freebsd-scsi-outgoing; Mon, 21 Jul 1997 07:55:07 -0700 (PDT) Received: from bacchus.eng.umd.edu (bacchus.eng.umd.edu [129.2.94.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17097 for ; Mon, 21 Jul 1997 07:55:05 -0700 (PDT) Received: from [10.0.0.4] (annex9-52.dial.umd.edu [128.8.23.52]) by bacchus.eng.umd.edu (8.8.5/8.8.5) with ESMTP id KAA27079; Mon, 21 Jul 1997 10:52:15 -0400 (EDT) X-Sender: crb@bacchus.eng.umd.edu Message-Id: In-Reply-To: <199707210357.NAA23642@ogre.dtir.qld.gov.au> References: from Dave Huang at "Sat, 19 Jul 1997 04:13:35 +0000" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 21 Jul 1997 10:50:26 -0400 To: Stephen McKay From: "Christopher R. Bowman" Subject: Re: Disk activity light on Asus SC875 doesn't work Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Saturday, 19th July 1997, Dave Huang wrote: > >>Hi there... I just got an Asus SC875 card (53c875 chip), and it seems to >>be running great so far... except for one weird thing: the activity LED >>doesn't work when in NetBSD. However, in MSDOS, Win95, and WinNT, it works >>just fine. > >It's the same with the Diamond FirePort 40 (based on the 875J), so you >aren't imagining it. It wasn't a useful indicator no matter which way I >plugged in my LED. It's a real bummer because my new disk is too quiet. :-) > >Stephen. Simply as a data point, the led on my Tekram 390F (53c875) card works. --------- Christopher R. Bowman crb@eng.umd.edu My home page From owner-freebsd-scsi Mon Jul 21 13:28:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09298 for freebsd-scsi-outgoing; Mon, 21 Jul 1997 13:28:22 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA09277 for ; Mon, 21 Jul 1997 13:28:15 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-44.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA29320 (5.67b/IDA-1.5 for ); Mon, 21 Jul 1997 22:28:10 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id WAA10755; Mon, 21 Jul 1997 22:27:50 +0200 (CEST) X-Face: " Date: Mon, 21 Jul 1997 22:27:49 +0200 From: Stefan Esser To: Stephen McKay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Disk activity light on Asus SC875 doesn't work References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Christopher R. Bowman on Mon, Jul 21, 1997 at 10:50:26AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 21, "Christopher R. Bowman" wrote: > >On Saturday, 19th July 1997, Dave Huang wrote: > > > >>Hi there... I just got an Asus SC875 card (53c875 chip), and it seems to > >>be running great so far... except for one weird thing: the activity LED > >>doesn't work when in NetBSD. However, in MSDOS, Win95, and WinNT, it works > >>just fine. > > > >It's the same with the Diamond FirePort 40 (based on the 875J), so you > >aren't imagining it. It wasn't a useful indicator no matter which way I > >plugged in my LED. It's a real bummer because my new disk is too quiet. :-) > > > >Stephen. > > Simply as a data point, the led on my Tekram 390F (53c875) card works. Well, and to add a few more data points, it also works if you use a Symbios SCSI card, or even my SP3G mother board with on-board SCSI ... While it is easy to have a status LED connected to some SCSI bus signal (BSY), which makes it work with no driver support, other boards use a general purpose I/O pin, and the driver has to set/reset the according register bit. The bad thing about this is, that some other card might do surprising things (like erase the cards NVRAM :), if you toggle that bit with a suitable rate ... I have prefered to not implement software support for the status LED, but Gerard Roudier did it for the BSD driver when he ported it to Linux. Well, and I guess now I've got even less reason to reject the patch he sent, which will add this feature (and some more!) to the version in FreeBSD. So, if you wait for a few more days, you may find that your status LED will suddenly start to blink :) Regards, STefan From owner-freebsd-scsi Tue Jul 22 05:03:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24179 for freebsd-scsi-outgoing; Tue, 22 Jul 1997 05:03:35 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24160; Tue, 22 Jul 1997 05:03:26 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA06466; Tue, 22 Jul 1997 07:18:01 -0400 (EDT) From: Peter Dufault Message-Id: <199707221118.HAA06466@hda.hda.com> Subject: Re: help: wiring down scsi devices doesn't work In-Reply-To: from Jay Kuri at "Jul 19, 97 00:06:15 am" To: jaykuri@oneway.com (Jay Kuri) Date: Tue, 22 Jul 1997 07:18:00 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have been trying, to no avail, to wire down a particular target > device to pt0. Although config gives me no errors, and the kernel > rebuilds fine, it does not wire down the device... and instead reports it > (a scsi scanner) as uk0. It didn't recognize it as a processor type. The device still needs to claim to be a processor type for the kernel to connect it as that. For example, you can't forceably say that a WORM is a CDROM with something like: device cd0 at scbus0 target 5 unit 0 and have it work for whatever shows up in target 5, though it may be a good idea given a required "flag 0x01" etc. Post your verbose boot messages. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-scsi Tue Jul 22 18:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13428 for freebsd-scsi-outgoing; Tue, 22 Jul 1997 18:21:33 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13423 for ; Tue, 22 Jul 1997 18:21:30 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id SAA11332 for ; Tue, 22 Jul 1997 18:21:22 -0700 (PDT) Date: Tue, 22 Jul 1997 18:21:22 -0700 (PDT) From: Jaye Mathisen To: scsi@freebsd.org Subject: Which version is the DPT driver installed in? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Which version of FreeBSD has the DPT driver incorporated? I see some patches against 2.2, but unsure how well they'll apply against -current, or 2.2.2-RELEASE. Have DPT, will travel. From owner-freebsd-scsi Wed Jul 23 00:29:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01173 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 00:29:34 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA01162 for ; Wed, 23 Jul 1997 00:29:31 -0700 (PDT) Received: (qmail 1071 invoked by uid 1000); 23 Jul 1997 07:29:43 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 23 Jul 1997 00:29:43 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, A new version of the DPT driver for FreeBSD was posted to sendero-ppp.i-connect.net/crsh. Apologies to those who could not get through. This situation will be cleared in a short time. From owner-freebsd-scsi Wed Jul 23 00:29:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01187 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 00:29:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA01163 for ; Wed, 23 Jul 1997 00:29:31 -0700 (PDT) Received: (qmail 1076 invoked by uid 1000); 23 Jul 1997 07:29:44 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 23 Jul 1997 00:29:43 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-scsi@freebsd.org Subject: New DPT Driver Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, First! Sorry for the lousy connectivity to sendero-ppp. I will GREATLY improve things in the next few days. I have put version 1.1.10 in the crash directory. Highlights: * Hopefully the last release before checkin into the FreeBSD tree. * The driver should be in the RELENG_2_2 tree. * In the near future, I will continue to publish the driver BEFORE it goes into the depository. * Certain NASTY bugs eliminated. Most dealing with slight timing errors and race conditions too subtle to detect, except through testing. * Some options were eliminated and some were added. Notably the DPT_COMMAND_SPLHIGH; It puts the driver, ever so BRIEFLY into splhigh to insure safe locking of the hardware registers. This is a short term solution but appears very effective. * By the time you read this, there will be a patch against 3.0-current. There will not be many of these patches, only enough to meet demand. The -current driver will support the new SCSI layer planned. As such we would like to limit development on that branch. Bugs will be fixed! Other DPT news: I received a motherboard from a FreeBSD user that is supposed to be really nasty. I finally put it in a box, disks, controller, etc. Will start testing tomorrow. DPT engineering, at the highest level, is taking our reports on troubles on certain platforms very seriously; A test program is on its way, including a FreeBSD release to be installed and tested. I masterdd a CD set for them and it is on the way. Between DPT, certain system vendor and us here, there are some 6 people working on this problem. I received inquiries about the syscon spitting messages like this: ... Leaving %d (%s) alone ... this is the result of two things being defined: 1. In i386/conf/WHATEVER you have ``options DPT_HANDLE_TIMEOUTS'' 2. In dev/dpt/dpt/h you have ``#define DPT_DEBUG_TIMEOUTS'' This combination tells the driver to occasionally check that there are no ``forgotten'' requests in the submitted queue (requests given to the DPT hardware and not heard from yet). the above message simply says that it found something in the queue and it is too young to die. If you start seeing complaints about ``stale'' transactions, or even more so, if you see something like ``... Bad (%d) CCB ...'', please, please report it to me along with the motherboard, slot number in the board, IRQ used, name, rank, SSN, etc. this is a clear indication of corrupt DMA transfers. The next release will be 1.2.0 and will include the IOCTL support for dptmgr. RAID Corner: * Use RAID-(!0) only if data loss is very upsetting. * Use RAID-5 only if storage space is at premium. * Remember that RAID array MTBF is (worst drive MTBF) / (number of drives) A redundant array simply provides a way to recover from this formula. Many people use DPT cotrollers for News Servers, and use RAID-5 configuration. When i grew up, losing the news data was upsetting but not a disaster. Performance in this convoluted database is important. If you agree with this statement, use RAID-0. If this is wrong, use RAID-5. If you need the best performance, in a redundant array, use RAID-1. An interesting combination is to create several RAID-1 arrays, and then have CCD across them in a RAID-0 (striping) arrnagement. REQUEST: Please try and build several different RAID configurations and try to see which is the best solution for news servers. I have enough questions on this matter i think I will start selling tickets :-) For this consider: RAID type (0,1,5) Stripe size Stripe sequence (across busses, etc.) Amount of memory on the DPT Percentage of read-ahead Percentage of cache devoted to read vs. write Nature of cache (write-through, write-back, etc.) Cache arrangement on individual drives. Competition (friendly, no rewards other than (even more) inflated ego :-): Largest RAID array Fastest Array Highest load Nastiest bug If this continues, i will have to cave in and actually setup a web page for all this. Help Needed: I need to build a new, independant version of a dptmgr. I want it to have nothing to do with the DPt provided one, except for compatible API. ANYONE is better than I am in drawing icons, pixmaps, etc. I would like it to be either xforms based or some other nifty tool. I will provide all the necessary kernel interfaces and low level stuff, but the glory of the UI can and should go tom someone else. Thanx for listening! Simon From owner-freebsd-scsi Wed Jul 23 05:54:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14810 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 05:54:34 -0700 (PDT) Received: from nefertiti.lightningweb.com (nefertiti.lightningweb.com [198.68.191.157]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14805; Wed, 23 Jul 1997 05:54:32 -0700 (PDT) Received: from localhost (greg@localhost) by nefertiti.lightningweb.com (8.8.5/8.8.5) with SMTP id FAA25193; Wed, 23 Jul 1997 05:53:19 GMT Date: Wed, 23 Jul 1997 05:53:19 +0000 () From: "Greg K. Cagle" To: freebsd-fs@freebsd.org cc: freebsd-scsi@freebsd.org Subject: adding RAID to the OS without re-partitioning Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I plan on adding a RAID disk array to my existing server. Ther server has three HDD's in it now, with "/" as one, "/usr/" as another, and a spare that's partitioned as "/scratch/". The disk array will be an independent unit, and will hook up to the external port on my Adaptec 2940UW. The company (Baydel) says that the array will appear as one large volume to FreeBSD. My question: How do I include the new array as part of the filesystem, without re-installing? I know I can make those choices when I first install the OS, but can I add a partition now, without messing up anything? I want to end up with the large RAID as my "/usr/" partition. Thanks for suggestions, Greg ps I have 2.1.5 on a Pentium Pro 200 with 128MB ram. ***************************************** Greg K. Cagle - The Chief - Lightningweb http://www.lightningweb.com From owner-freebsd-scsi Wed Jul 23 08:02:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22462 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 08:02:58 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22453; Wed, 23 Jul 1997 08:02:54 -0700 (PDT) Received: from 166.72.151.198 (slip166-72-151-198.nd.us.ibm.net [166.72.151.198]) by out2.ibm.net (8.8.5/8.6.9) with ESMTP id PAA52760; Wed, 23 Jul 1997 15:02:49 GMT Message-ID: <33D61D15.AA791100@ibm.net> Date: Wed, 23 Jul 1997 10:02:47 -0500 From: Jay Erickson Reply-To: Jay.Erickson@ibm.net Organization: Life X-Mailer: Mozilla 4.01 (Macintosh; I; 68K) MIME-Version: 1.0 To: "questions@FreeBSD.ORG" , hardware@FreeBSD.ORG, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG CC: Mark Dawson , brian@ibm.net, Tao@gate.sinica.ed Subject: Compaq's Built in SCSI X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I searched the archives and didn't find a definitive answer. I want to install FreeBSD on a couple of Compaq Proliant 1000's with the built in SCSI controller or Compaq's Smart SCSI controller. The Installer kernel doesn't seem to recognize either. Please help give me some driver help or at least point me in the right direction. TIA Jay.Erickson@IBM.net erickson@Nserver.grandforks.af.mil <-- My reliable FreeBSD box From owner-freebsd-scsi Wed Jul 23 08:50:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA25866 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 08:50:40 -0700 (PDT) Received: from hotpoint.dcs.qmw.ac.uk (hotpoint.dcs.qmw.ac.uk [138.37.88.162]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA25813; Wed, 23 Jul 1997 08:50:25 -0700 (PDT) Received: from md@ruby.dcs.qmw.ac.uk [138.37.88.139]; by hotpoint.dcs.qmw.ac.uk (8.8.6/8.8.5/S-4.0) with ESMTP; id QAA01629; Wed, 23 Jul 1997 16:50:01 +0100 (BST) Received: from md@localhost; by ruby.dcs.qmw.ac.uk (8.8.4/8.8.4/C-3.2); id QAA02371; Wed, 23 Jul 1997 16:50:00 +0100 (BST) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.ruby.cs.qmw.ac.uk.sun4.41 via MS.5.6.ruby.cs.qmw.ac.uk.sun4_41; Wed, 23 Jul 1997 16:49:59 +0100 (BST) Message-ID: Date: Wed, 23 Jul 1997 16:49:59 +0100 (BST) From: Mark Dawson To: "questions@FreeBSD.ORG" , hardware@FreeBSD.ORG, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG, Jay.Erickson@ibm.net Subject: Re: Compaq's Built in SCSI CC: brian@ibm.net, Tao@gate.sinica.ed In-Reply-To: <33D61D15.AA791100@ibm.net> References: <33D61D15.AA791100@ibm.net> Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I want to install FreeBSD on a couple of Compaq Proliant 1000's with the > built in SCSI controller or Compaq's Smart SCSI controller. The > Installer kernel doesn't seem to recognize either. See for a boot floppy image and a kernel for FreeBSD-2.2.2 that should recognise the Smart and Smart-2 controllers on your Compaq box. Please see the README at the above location for further details and let me know how you get on as its not been tested on a ProLiant 1000 before. Regards, Mark From owner-freebsd-scsi Wed Jul 23 13:17:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11514 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 13:17:27 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11508 for ; Wed, 23 Jul 1997 13:17:23 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id QAA03375; Wed, 23 Jul 1997 16:17:17 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id QAA06773; Wed, 23 Jul 1997 16:17:16 -0400 (EDT) To: Simon Shapiro cc: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: New DPT Driver In-reply-to: Your message of "Wed, 23 Jul 1997 00:29:43 PDT." Date: Wed, 23 Jul 1997 16:17:16 -0400 Message-ID: <6771.869689036@orion.webspan.net> Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote in message ID : > RAID Corner: > > * Use RAID-(!0) only if data loss is very upsetting. > * Use RAID-5 only if storage space is at premium. > * Remember that RAID array MTBF is (worst drive MTBF) / (number of drives) > A redundant array simply provides a way to recover from this formula. > > Many people use DPT cotrollers for News Servers, and use RAID-5 > configuration. When i grew up, losing the news data was upsetting but not > a disaster. Performance in this convoluted database is important. > If you agree with this statement, use RAID-0. If this is wrong, use RAID-5. > If you need the best performance, in a redundant array, use RAID-1. > An interesting combination is to create several RAID-1 arrays, and then > have CCD across them in a RAID-0 (striping) arrnagement. > > REQUEST: > > Please try and build several different RAID configurations and try to see > which is the best solution for news servers. I have enough questions on > this matter i think I will start selling tickets :-) The most common scenario I've heard of for large news installations, where drive numbers are not a problem and you can get as many drives as you ask for, they use RAID0+1, i.e. take 2 identical stripes and mirror then. Of course, the RAID format you choose is only one part of a very large equation ... some people swear by 1gig drives, and lots of them, to get the needed performance. Others swear by 4gig drives. Then you get into the whole narrow/wide/ultrawide argument, and how many drives are optimal to put on a single scsi chain, how many chains you need, etc. Then there is the sticky issue of what stripe size to use. You, in the past, have recomended small stripe sizes for use in the DPT controller. I am not sure if that is because of hardware/software limitations or an over-generalisation. The growing consensus is that larger stripe sizes are better for news (sizes on the order of 32MB, yes, thats 32 megabytes) are non unusal. Can DPT support that? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-scsi Wed Jul 23 23:21:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11724 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 23:21:42 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11710 for ; Wed, 23 Jul 1997 23:21:34 -0700 (PDT) Received: (qmail 22000 invoked by uid 1000); 24 Jul 1997 06:21:47 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 23 Jul 1997 23:21:47 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: Which version is the DPT driver installed in? Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 23-Jul-97 you wrote: > > > Which version of FreeBSD has the DPT driver incorporated? I see some > patches against 2.2, but unsure how well they'll apply against -current, > or 2.2.2-RELEASE. > > Have DPT, will travel. There are two patches; * One against 2.2; this is done against RELENG_2_2 as of the day of patch publising, or the night before. Should patch against most any 2.2. * One against -current; Same policy as above. The 2.2 patch should be unnecessary soon; It will become part of the FreeBSD 2.2 source tree. The -current patch will divert soon; Will be adopted to the new SCSI architecture being build by none else than Justin Gibbs. Simon From owner-freebsd-scsi Wed Jul 23 23:21:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11744 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11712 for ; Wed, 23 Jul 1997 23:21:35 -0700 (PDT) Received: (qmail 22004 invoked by uid 1000); 24 Jul 1997 06:21:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <6771.869689036@orion.webspan.net> Date: Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Gary Palmer" Subject: Re: New DPT Driver Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Gary Palmer"; On 23-Jul-97 you wrote: ... > > REQUEST: > > > > Please try and build several different RAID configurations and try to > see > > which is the best solution for news servers. I have enough questions > on > > this matter i think I will start selling tickets :-) > > The most common scenario I've heard of for large news installations, > where drive numbers are not a problem and you can get as many drives > as you ask for, they use RAID0+1, i.e. take 2 identical stripes and > mirror then. Sounds interesting. gives me somewhat of a motivation to adopt DPT's in-kernel RAID-0 option, to allow you to stripe across controllers. You can stripe acrooss busses today. > Of course, the RAID format you choose is only one part of a very large > equation ... some people swear by 1gig drives, and lots of them, to > get the needed performance. Others swear by 4gig drives. Then you get > into the whole narrow/wide/ultrawide argument, and how many drives are > optimal to put on a single scsi chain, how many chains you need, etc. This is why my request came in in the first place. For RDBMS work, actually, 300MB/spindle is about it (Try to get a hot performing 300MB drive, though :-) An interesting analysis I saw sometimes ago claims that the performance gap between processors and disks grows at 50%/year. The gap between processors and DRAM grows at abount the same rate. Based on this logic, more smaller drives is better. There is I/O logic overhead, cache sizes, etc. to be considered too. > Then there is the sticky issue of what stripe size to use. You, in the > past, have recomended small stripe sizes for use in the DPT > controller. I am not sure if that is because of hardware/software > limitations or an over-generalisation. The growing consensus is that > larger stripe sizes are better for news (sizes on the order of 32MB, > yes, thats 32 megabytes) are non unusal. Can DPT support that? 32MB per stripe? That means that the current DPT can cache only 2 stripes. Consider the following too (this is a friendly discussion, not an acusation session right? :-) * Most news servers use the Unix file system. Right? * Last I saw, ALL F/S I/O was done in 4Kbytes chunks. * Typical news posting is on the order of 8Kbytes or less (the pornography and stolen software postings exempted) * As news age and expire and new postings come in, the linearity of the F/S will decrease, not improve. I/E randomness will increase. * A typical disk drive will take, on a single I/O (I am not sure the SCSI standard will even allow that. Justin?) about 5-6 seconds to read/write this size stripe. This means that every cache miss will take 5-6 seconds to complete. * We ran some very carefully timed tests (on Slowlaris, Linux and FreeBSD (NOT on the DPT - did not have a driver yet) to confirm my findings from another job. The number of I/O operations per seconds is almost independant of block size, SCSI bus width and SCSI bus rate up to about 8KB blocks. With blocks larger than 8KB, the data transfer time begins to be visible. [ In another job, we had access to a very nice ($38,000 or so nice) SCSI analyzer. The ``paper accounting'' of SCSI bus cycles was very precisely confirmed on the CRT tube ] The reason for that is that most bus negotiations happen in slow/narrow mode. Now FCAL is another story. The above will lead you to the conclusion that smaller is better. The reality of course says otherwise. For many purposes, the number is around 32-128MB stripes. Remember that a good SCSI HBA driver (or firmware) will elevator sort the I/O and collapse ajacent requests into single or linked requests. The only way I can see 32MB stripes being even usable, is in setting them up as CCD stripes of this size. Of course, then you really do all your I/O in... 4096 bytes. If you want all these whole performance theories to go down the drain fast, consider RDBMS (or any true database work) and start thinking about ZERO LOSS I/O, where a return from a WRITE operation means ``I guarantee that the data is on disk, the disk will not lose the data, my WRITE does not collide with your WRITE, etc. or I will sell my in-laws to slavery and give you the money''. In 25 years of RDBMS design, I have never encountered database block size larger than 8K or I/O atomic operation larger than 64K. If I remember, the Berkeley F/S research indicated block sizes around 8KB to be optimal for file systems, but am not sure of the validity of this data anymore. Last point to ponder; The bus bandwidth on a P6 memory bus is about 532MB/sec. Theoretical limit for PCI is 132. Practical? Never seen anything useful going faster than 75MB/Sec, with peak demo stuff at 100-110MB/Sec. This gives you (on most motherboards) 4:1 ratio. With PCI-SCSI ratio of theoretical 2:1 and practical 4-10:1. Simon From owner-freebsd-scsi Wed Jul 23 23:21:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11745 for freebsd-scsi-outgoing; Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11713 for ; Wed, 23 Jul 1997 23:21:35 -0700 (PDT) Received: (qmail 22008 invoked by uid 1000); 24 Jul 1997 06:21:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Greg K. Cagle" Subject: RE: adding RAID to the OS without re-partitioning Cc: freebsd-scsi@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Greg K. Cagle"; On 23-Jul-97 you wrote: > I plan on adding a RAID disk array to my existing server. Ther server > has > three HDD's in it now, with "/" as one, "/usr/" as another, and a spare > that's partitioned as "/scratch/". > > The disk array will be an independent unit, and will hook up to the > external port on my Adaptec 2940UW. The company (Baydel) says that the > array will appear as one large volume to FreeBSD. > > My question: How do I include the new array as part of the filesystem, > without re-installing? I know I can make those choices when I first > install the OS, but can I add a partition now, without messing up > anything? I want to end up with the large RAID as my "/usr/" partition. > > Thanks for suggestions, > > Greg > > ps I have 2.1.5 on a Pentium Pro 200 with 128MB ram. Since no on else took it on, I will donate my $0.02. This is really not a SCSI issue at all. essentially, this is what you do: First, find out the name and size of the disk. Right after booting, do: dmesg | grep '^sd[0-9]' This will give you some output like: sd17(dpt0:1:0): Direct-Access 16394MB (32542592 528 byte sectors) You want to remember two things from the above example: 1. The disk is sd17 2. The reported size is 32,542,592 sectors. If you see (on a DPT): sd17: Forcing sector size to 512 Ignore that. It simply tells you that the disks have a physical size of 528 bytes. We use that to record ECC data. This insures that data transfers on the SCSI bus (cable) are ECC corrected. That's all. Next, create a file with this format: # This is the Sendero/Nomis SCSI RAID-5 array # It is composed of five 4GB Baracudas. # Reported capacity is 16,394MB (32,542,592x528) # Aligned to 1Mb ``cylinders'' it yields 32,540,672x512 blocks # or 15,889 ``cylinders'' # # Do not adjust partitions!!! g c15889 h64 s32 p 1 165 64 8388544 p 2 165 8388608 8388608 p 3 165 16777216 8388608 p 4 165 25165824 7374848 Adjust the cXXXX field in the geometry record to match capacity of the device (I take the number of sectors and mod 2048 itto arrive at the number of 1MB ``cylinders'' we have. It costs few megbytes of space but is so much easier to handle. The next step is to edit /etc/disktab and create an entry for each of these partitions. The terminology is confusing. What we have done so far is plan on which ``partitions'' will fdisk create. From this point forward, these partitions are actually called ``slices''. Also notice that until recently fdisk partitions (slices) were numbered 0-3, while disklabel slices are 1-4. Recently, at least this part is uniform; fdisk partitions are 1-4 and dislabel slices (same thing!) are also 1-4. Below is a typical /etc/disktab, for the LAST partition-slice (4) in the above RAID array: sd17.s4|sendero-5.s4|DPT Raid-5 composed of five 4GB Baracudas:\ :ty=simulated:\ :ns#2048:\ :nt#1:\ :nc#3601: \ <--- number of ``cylinders'' :sc#2048: \ :su#7374848:\ <---- su = nc * sc :se#512:\ :rm#7200:\ :pc#7374848:oc#0:tc=unused:bc#4096:fc#512: \ <-- the whole device :pa#2097088:oa#64:ta=4.2BSD:ba#4096:fa#512: \ <-- Partition a :pb#5277696:ob#2097152:tb=4.2BSD:bb#4096:fb#512: <-- partition b You can have partitions a,b,d,e,f,g,h. In theory you can have c as a partition but certain utilities ``know'' that c is hte whoile disk. Some things in FreeBSD also ``know'' that ``b'' is a swap device. Oh, when we say ``partition'' here, we mean FreeBSD partition WITHIN the fdisk partition, or more correctly (in this context); A device contains several fdisk slices, each contains several FreeBSD partitions. Enough ``theory''. go make the necessary nodes: cd /dev ./MAKEDEV sd17 ./MAKEDEV sd17s1a The above two created all the necessary entried for all the partitions, slices, and what-have-you. Now do: fdisk -i -f my_own_fdisk_file sd17 Now Listen Carefully: * MAKE SURE, ABSOLUTELY SURE you have dumped fdisk of your boot disk to a safe file, in the format indicated above. * MAKE SURE, ABSOLUTELY SURE you have the entries for (in our example) sd17 in /dev/ * TYPE the fdisk command EXACTLY as indicated above. Do NOT MISS an argument! If you do not, and I still miss sometimes, fdisk will write the new configuration, or some version of it ON YOUR BOOT DRIVE!!! It will do so with glee, quielty, without warning (sorry, it will put on the screen something like ``******* working on /dev/sd0 ****'' which you will MISS as you are so unsure and nervous about wiping your system out. If you saw that, you just did. If you did, don't panic! and DO NOT, I repeat, DO NOT reboot or shutdown your system! Just follow this procedure, to re-create the boot disk partitions-slices. Or back it up. you did back it up BEFORE starting this procedure. Right? Right... but did you actually read that tape? If all is well, fdisk will create the partitions and complain about the disk labels. This is OK. There are no labels yet, so why should they be correct? Once this is done, do the following: disklabel -w -r sd17s4 sd17.s4 "short/meaningful label" This will create /dev/sd17s4a and /dev/sd17s4b. As you run disklabel, it will complain about the label for this partition and for all the slices too. The reason is that when FreeBSD opens ANY raw device, it reads the fdisk data for the disk and all the labels for all the slices. Since you are just creating them, there will be complaints. just run each disklabel command twice and the complaint will disappear for that slice. After you created/labeled three slices, it will not complain about the fourth. If you want file systems there do: newfs /dev/rsd17s4a newfs /dev/rsd17s4b You can embelish, tune and improve how newfs makes the file system. You can change things with tunefs (or some such). I am not the person to ask about that. I use newfs as is. The last steps are just as easy. Say you have already /var/spool/news and you want to move it from /var to this new array, splitting it between two filesystems. Last time I installed news I had /var/spool/news/alt/binaries on a separate filesystem. Let's use that as an example. Edit /etc/fstab and add two new lines. Emulate what is already there, just replace the first two fields. Shutdown the news server. mount /dev/sd17s4a /mnt mkdir -p /mnt/alt/binaries chown news.news /mnt /mnt/alt/binaries mount /dev/sd17s4b /mnt/alt/binaries chown news.news /mnt/alt/binaries # Trust me on this one :-) cd /var/spool/news find . | cpio -dmpv /mnt sync umount /mnt/alt/binaries umount /mnt rm -rf /var/spool/news/* mount /var/spool/news mount /var/spool/news/alt/binaries Simple. Isn't it? And they said Unix is not better than NT. simon From owner-freebsd-scsi Thu Jul 24 02:25:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19293 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 02:25:53 -0700 (PDT) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19287 for ; Thu, 24 Jul 1997 02:25:48 -0700 (PDT) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.6/8.6.9) with SMTP id KAA17342; Thu, 24 Jul 1997 10:22:31 +0100 (BST) Message-ID: <33D71ED7.69D8BD19@cablenet.net> Date: Thu, 24 Jul 1997 10:22:31 +0100 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: Simon Shapiro CC: freebsd-scsi@freebsd.org Subject: Re: New DPT Driver References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > > > Then there is the sticky issue of what stripe size to use. You, in the > * Most news servers use the Unix file system. Right? > * Last I saw, ALL F/S I/O was done in 4Kbytes chunks. > The only way I can see 32MB stripes being even usable, is in setting them > up as CCD stripes of this size. Of course, then you really do all your > I/O in... 4096 bytes. I'm in the process of constructing some news servers and I intend to use ccd. What figure should I use as the interleave factor. The man page suggests that a high figure such as 65,536 should be used for news servers. The system has 8 ST5120N (2 gig narrow, 4500 RPM) drives, and I'm running the busses in Ultra mode (20 Mbps). regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-scsi Thu Jul 24 03:46:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA21952 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 03:46:46 -0700 (PDT) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA21947 for ; Thu, 24 Jul 1997 03:46:37 -0700 (PDT) Received: from axe (localhost [127.0.0.1]) by axe.cablenet.net (8.8.6/8.6.9) with SMTP id LAA17588 for ; Thu, 24 Jul 1997 11:42:24 +0100 (BST) Message-ID: <33D73190.3B54AFBF@cablenet.net> Date: Thu, 24 Jul 1997 11:42:24 +0100 From: Damian Hamill Organization: CableNet Ltd X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: New DPT Driver References: <33D71ED7.69D8BD19@cablenet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Damian Hamill wrote: > > Simon Shapiro wrote: > > > > > > Then there is the sticky issue of what stripe size to use. You, in the > > > * Most news servers use the Unix file system. Right? > > * Last I saw, ALL F/S I/O was done in 4Kbytes chunks. > > > The only way I can see 32MB stripes being even usable, is in setting them > > up as CCD stripes of this size. Of course, then you really do all your > > I/O in... 4096 bytes. > > I'm in the process of constructing some news servers and I intend to use > ccd. What figure should I use as the interleave factor. The man page > suggests that a high figure such as 65,536 should be used for news > servers. The system has 8 ST5120N (2 gig narrow, 4500 RPM) drives, and > I'm running the busses in Ultra mode (20 Mbps). I've answered this myself. With an interleave factor of 16384 a copy of /usr to the ccd file system had all disk activity on drives 1 & 5. With an interleave factor of 65536 the activity was spread around all 8 drives. regards damian -- * Damian Hamill M.D. damian@cablenet.net * CableNet & The Landscape Channel * http://www.cablenet.net/ http://www.landscapetv.com/ From owner-freebsd-scsi Thu Jul 24 04:13:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22940 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 04:13:52 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22914; Thu, 24 Jul 1997 04:13:29 -0700 (PDT) Message-Id: <199707241113.EAA22914@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA176122054; Thu, 24 Jul 1997 21:00:54 +1000 From: Darren Reed Subject: Re: Compaq's Built in SCSI To: Jay.Erickson@ibm.net Date: Thu, 24 Jul 1997 21:00:54 +1000 (EST) Cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG, md@dcs.qmw.ac.uk, brian@ibm.net, Tao@gate.sinica.ed In-Reply-To: <33D61D15.AA791100@ibm.net> from "Jay Erickson" at Jul 23, 97 10:02:47 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Jay Erickson, sie said: > > I searched the archives and didn't find a definitive answer. > > I want to install FreeBSD on a couple of Compaq Proliant 1000's with the > built in SCSI > controller or Compaq's Smart SCSI controller. The Installer kernel > doesn't seem to > recognize either. FWIW, Solaris 2 supports some of the Compaq Proliants...check http://access1.sun.com Darren From owner-freebsd-scsi Thu Jul 24 07:19:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA00668 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 07:19:37 -0700 (PDT) Received: from oneway.com (oneway.com [198.80.68.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA00643; Thu, 24 Jul 1997 07:19:30 -0700 (PDT) Received: from oneway.com (oneway.com [198.80.68.27]) by oneway.com (8.8.5/8.8.3) with SMTP id JAA14701; Thu, 24 Jul 1997 09:13:27 -0500 (CDT) Date: Thu, 24 Jul 1997 09:13:27 -0500 (CDT) From: Jay Kuri To: Peter Dufault cc: freebsd-scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: help: wiring down scsi devices doesn't work In-Reply-To: <199707221118.HAA06466@hda.hda.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have been trying, to no avail, to wire down a particular target > > device to pt0. Although config gives me no errors, and the kernel > > rebuilds fine, it does not wire down the device... and instead reports it > > (a scsi scanner) as uk0. > It didn't recognize it as a processor type. The device still needs > to claim to be a processor type for the kernel to connect it as > that. Gotcha... I was under the impression that the scanner was reporting itself as a processor (and this is what the docs for the driver said it would do) but it was really reporting itself as a type 6 (scanner... imagine that :) I thought that processor target and unknown target had some different functionality... It appears that I am wrong in that. Thanks for your help, Jay From owner-freebsd-scsi Thu Jul 24 10:43:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14295 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 10:43:14 -0700 (PDT) Received: from metrocon.com (root@metrocon.com [208.9.142.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14289; Thu, 24 Jul 1997 10:43:12 -0700 (PDT) Received: from metrocon.com (fbsd@localhost [127.0.0.1]) by metrocon.com (8.8.5/8.8.3) with ESMTP id NAA05027; Thu, 24 Jul 1997 13:44:05 GMT Message-Id: <199707241344.NAA05027@metrocon.com> To: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org Subject: CCD FileSystems Date: Thu, 24 Jul 1997 13:44:05 +0000 From: Free BSD Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all.. I am having some trouble. I need to do a ccd situation with 2- 9GB uw-scsi drives. Can someone direct me to detailed instructions please? It would also be nice if someone sends me a sample ccd disklabel with instructions on how to impliment it. Thanks alot.. Isaac Kohen Systems Administrator MetroCon Communications From owner-freebsd-scsi Thu Jul 24 16:59:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA03228 for freebsd-scsi-outgoing; Thu, 24 Jul 1997 16:59:44 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA03221; Thu, 24 Jul 1997 16:59:39 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id QAA11169; Thu, 24 Jul 1997 16:59:36 -0700 (PDT) Date: Thu, 24 Jul 1997 16:59:34 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org, scsi@freebsd.org Subject: Ugh, DPT killing my performance... :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk P6-200, 64MB RAM, DPT 2 channel Ultra Wide, plugged in to Seagate Barracuda's. (4GB). DPT has 64MB RAM, version 1.10 DPT patch, 2.2.2-RELEASE disk. All disks are on the same channel (0) of the DPT. The following script renders the system essentially unusable: while (1) (cd t1 && iozone 600) (cd t2 && iozone 600) bonnie -s 200 & wait end ls -l of /root takes > 20 seconds. TOP is showing > 99% idle time. systat 2 only shows 28 interrups/sec on IRQ 15, which is the DPT controller, according to the BIOS. Transfers shows about 20-30 tps. There are these occasional burps of > 20% system time, not sure where it's going. No other processes actively running. This concerns me a bit. I tried the same thing on a 3 disk ccd array, and it runs much smoother, w/o the long delays. Of course, no parity. The DPT is configured as RAID-5, 128k stripes. Other than the grief of installing it, not sure how much benefit there would be to changing this. From owner-freebsd-scsi Fri Jul 25 00:06:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18482 for freebsd-scsi-outgoing; Fri, 25 Jul 1997 00:06:40 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA18470 for ; Fri, 25 Jul 1997 00:06:30 -0700 (PDT) Received: (qmail 17502 invoked by uid 1000); 25 Jul 1997 07:06:44 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 25 Jul 1997 00:06:44 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: Ugh, DPT killing my performance... :( Cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 24-Jul-97 you wrote: > > > P6-200, 64MB RAM, DPT 2 channel Ultra Wide, plugged in to Seagate > Barracuda's. (4GB). DPT has 64MB RAM, version 1.10 DPT patch, > 2.2.2-RELEASE disk. All disks are on the same channel (0) of the DPT. > > The following script renders the system essentially unusable: > > while (1) > > (cd t1 && iozone 600) > (cd t2 && iozone 600) > bonnie -s 200 & > > wait > end > > > ls -l of /root takes > 20 seconds. > > TOP is showing > 99% idle time. > > systat 2 only shows 28 interrups/sec on IRQ 15, which is the DPT > controller, according to the BIOS. Transfers shows about 20-30 tps. Ah, This is it! Take the DPT off that IRQ15. On a P6-200 I am peaking at 1,200 tps, kernel make is about 400, make world 300 or so. On many motherboards IRQ 15 is a garbage can for all sorts of stray signals. If you compiled with DPT_MEASURE_PERFORMANCE; mknod /dev/dpt0 c 130 0 echo -n "dump softc" > /dev/dpt0 get_dpt /dev/dpt0 > /tmp/foo Now look at the output. The second line, tells you the count of aborted interrupts, spurious interrupts, minimum interrupt latelncy and maximum interrupt latency. The third line lists each SCSI command number, name [section in the spec], minimum time to executre, maximum time to execute. The fourth line tells you maximim/minimum waiting time, submitted time, completed time. The next line tells you the number of times commands collided in the driver, # of times the DPT was too busy to accept a command, worst # of retries, best # of retries. These will tell us where the DPT + driver are spending their time. Corrective action can then be suggested. > There are these occasional burps of > 20% system time, not sure where > it's > going. > > No other processes actively running. > > > This concerns me a bit. concerns me A LOT :-) > I tried the same thing on a 3 disk ccd array, and it runs much smoother, > w/o the long delays. Of course, no parity. > The DPT is configured as RAID-5, 128k stripes. Other than the grief of > installing it, not sure how much benefit there would be to changing this. Why grief? I am planning on a new dptmgr for FreeBSD, so your comments are valuable to me. Simon From owner-freebsd-scsi Sat Jul 26 19:54:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09576 for freebsd-scsi-outgoing; Sat, 26 Jul 1997 19:54:55 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09526 for ; Sat, 26 Jul 1997 19:54:51 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id WAA04155; Sat, 26 Jul 1997 22:54:50 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id WAA21107; Sat, 26 Jul 1997 22:54:49 -0400 (EDT) To: Damian Hamill cc: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: New DPT Driver In-reply-to: Your message of "Thu, 24 Jul 1997 11:42:24 BST." <33D73190.3B54AFBF@cablenet.net> Date: Sat, 26 Jul 1997 22:54:49 -0400 Message-ID: <21105.869972089@orion.webspan.net> Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Damian Hamill wrote in message ID <33D73190.3B54AFBF@cablenet.net>: > I've answered this myself. With an interleave factor of 16384 a copy of > /usr to the ccd file system had all disk activity on drives 1 & 5. With > an interleave factor of 65536 the activity was spread around all 8 > drives. A file copy is nowhere near the sort of test you wish to perform if you want to simulate a news server. In fact, the only *RELIABLE* test I have heard of to date is to run a news server for a few days at each stripe setting and see. The loading is just too difficult to simulate Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info