From owner-freebsd-scsi Tue May 26 08:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20964 for freebsd-scsi-outgoing; Tue, 26 May 1998 08:57:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA20933 for ; Tue, 26 May 1998 08:57:17 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 17153 invoked by uid 1000); 26 May 1998 16:58:53 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 26 May 1998 12:58:53 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Raul Zighelboim Subject: RE: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom , Charles Owens Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-May-98 Raul Zighelboim wrote: > > My 0.02 cents: > I did not installed FreeBSd on a DPT controller, but with an > Adaptec controller. Nevertheless, I have a DPT controller on a system > with a large fs (71780140 1K blocks). The system works, works well and > has been up for 4 days as a very busy usenet news spool directory. > This is running 2.2-RELENG from last sunday. This confirms my observations. Thanx. > As a sidebar; the DOS configuration software can only create arrays with > up to 1 mbyte interleave. Is this a limitation on the hardware or the > software ? Is (will there be) a way to create an array with a larger > interleave (32 megs comes to mind). An interleave factor larger than 1MB will be very inefficient: a. The SCSI bus will be used (locked) for long periods. This will cause poor multi-tasking response. b. The cache memory will be able to contain very few stripes. Also notice that in the context of FreeBSD, anything larger than 64K is sort of mute, as the O/S limits all SCSI transfers to that size. I do not know yet how CAM will do, but suspect it to be the same. Ideally, stripe size should be such that the latency in setting up a transfer + the latency in completeing a DPT-Host transfer are about equal to the time to transfer one block (the reality is a bit more complex than that); In this manner, the DPT can continue to ``feed'' blocks to the system (or the other way around) without pausing for disk. This is why a multiple-bus equipped DPT can achive transfer rates that are limited by the PCI bus and/or the O/S. This takes some careful tuning and experimentation. > Thanks, Simon, for a job well done. Thanx. I am going to get started on CAM port in the next few days. > > ================================================== > Raul Zighelboim rzig@verio.net > >> -----Original Message----- >> From: Charles Owens [SMTP:owensc@enc.edu] >> Sent: Friday, May 22, 1998 2:43 PM >> To: Simon Shapiro >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG >> Subject: RE: DPT install problem >> >> On Fri, 22 May 1998, Simon Shapiro wrote: >> >> > >> > On 21-May-98 Tom wrote: >> > > >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap >> a new >> > > DPT based system. However, sysinstall hangs after newfs'ing the >> > > filesystems. >> > > >> > > I'm using a 21GB array, with auto-defaults for the filesystems, >> so /usr >> > > is over 20GB in size. If I delete /usr and replace it with a >> 500MB >> > > filesystem, leaving the remaining space unallocated, sysinstall >> has no >> > > problem completing the newfs step. >> > > >> > > Anyone else had problems with sysinstall on a mid-sized array >> like >> > > this? >> > >> > Yup. Me :-) >> > But not on 3.0-current. I noticed that 2.2 does not like huge >> partitions, >> > but this is not consnstent. >> > >> > Simon >> >> This has me a bit nervous. This July I will be implementing an NFS >> server >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... >> but >> perhaps 3.0-current is my only choice? Is this -stable problem >> understood, with a fix coming any time soon? >> >> Any other concerns that I should be sweating about as I'm planning on >> building an array of this size? (and it will probably double in size >> the >> following summer) >> >> Thanks, >> --- >> ---------------------------------------------------------------------- >> --- >> Charles N. Owens Email: >> owensc@enc.edu >> >> http://www.enc.edu/~owensc >> Network & Systems Administrator >> Information Technology Services "Outside of a dog, a book is a >> man's >> Eastern Nazarene College best friend. Inside of a dog it's >> too dark to read." - Groucho Marx >> ---------------------------------------------------------------------- >> --- >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-scsi" in the body of the message --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 09:04:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22760 for freebsd-scsi-outgoing; Tue, 26 May 1998 09:04:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA22746 for ; Tue, 26 May 1998 09:04:34 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 17921 invoked by uid 1000); 26 May 1998 17:06:15 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805222221.PAA02816@dingo.cdrom.com> Date: Tue, 26 May 1998 13:06:15 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-May-98 Mike Smith wrote: >> >> > However, there are a couple of things that you personally (and other >> > concerned users) can do to help the situation. >> > >> > - Contribute commentary (as you have), documentation and source/ >> > procedural fixes. Remeber that FreeBSD is a volunteer project - >> > your support means that it will continue to improve. >> > - Donate a DPT controller to our testing pool so that we can test >> > with it. Chances are we can scrape enough disks together in one >> > place to meet the 20GB mark if we have one. >> >> I recently donated TWO DPT controllers and FIVE disk drives. They went >> to >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > Then we need some accountability from these prominent figures. Where > is their feedback on this discussion? I should not speak for others but I belive their systems are up and coming. Alas, they have been supplied with only few drives each. There are only few of us with large enough arrays to notice these problems. >> An ajacent problem, is that fsck will fail on such filesystems. >> The failure mode is fsck -p in /etc/rc. It does not have, by default >> enough resources to run a large parallel fsck. I added the following to >> /etc/rc: > > You should update the daemon class in /etc/login.conf. Can you verify > that the current settings there (/usr/src/etc/login.conf) are adequate? I am using (as of today, still to be tried): # # Settings used by /etc/rc # daemon:\ :coredumpsize@:\ :coredumpsize-cur=0:\ :datasize=infinity:\ :datasize-cur@:\ :maxproc=512:\ :maxproc-cur@:\ :memoryuse-cur=infinity:\ :memorylocked-cur=infinity:\ :openfiles=1024:\ :openfiles-cur@:\ :stacksize=infinity:\ :stacksize-cur@:\ :tc=default: as opposed to: ulimit -t unlimited ulimit -f unlimited ulimit -d unlimited ulimit -s unlimited ulimit -c unlimited ulimit -m unlimited ulimit -l unlimited BTW, what is foo@ in this file? > > (Note that a normal build does not update /etc, so you may be suffering > needlessly...) > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 09:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24400 for freebsd-scsi-outgoing; Tue, 26 May 1998 09:11:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA24395 for ; Tue, 26 May 1998 09:11:30 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 18024 invoked by uid 1000); 26 May 1998 17:13:10 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 26 May 1998 13:13:10 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Eivind Eklund Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-May-98 Tom wrote: > > On Fri, 22 May 1998, Eivind Eklund wrote: > >> On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: >> > Yes, it seems to be a sysinstall interaction. If I leave the space >> > unallocated, and then disklabel and newfs it later, it works fine. >> > >> > Currently it is pretty hard to bootstrap a new DPT system. You have >> > to >> > be able to build a kernel somewhere else as sysinstall will install a >> > non-DPT kernel, and you can't use sysinstall to allocate large DPT >> > partitions. I fear for the new user. >> >> sysinstall doesn't do this anymore. The DPT driver is activated as >> part of the standard sysinstall now. > > I've noticed that. But this won't help anyone until 2.2.7 is released, > or somone makes a 2.2.6 snapshot with the new GENERIC kernel. I should have a kernel image in ftp://ftp.simon-shapiro.org/FreeBSD. >> As for large arrays: I think that will have to be left to you that >> actually have those large arrays - it is kind of difficult for us >> others to find out where the problem is. I suspect libdisk might be >> the culprit; it interact with the slice code using different IOCTLs >> than disklabel, IIRC. > > So you think that sysinstall makes a bogus label? Remember, sysinstall > hangs basically right after newfs'ing the large filesystem. Either newfs > hangs while cleaning up, or something that sysinstall does after > newfs'ing > all the filesystems hangs. > > Another interesting tibbit, is that sysinstall seems to be generating > once a second disk i/o requests during this hung state. Could be stuck > in > loop. > >> Eivind. > > Tom > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 09:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25741 for freebsd-scsi-outgoing; Tue, 26 May 1998 09:18:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25497; Tue, 26 May 1998 09:17:38 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA09118; Tue, 26 May 1998 16:17:37 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA15943; Tue, 26 May 1998 18:17:36 +0200 (MET DST) Message-ID: <19980526181726.17568@follo.net> Date: Tue, 26 May 1998 18:17:26 +0200 From: Eivind Eklund To: shimon@simon-shapiro.org, Tom Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: DPT install problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Simon Shapiro on Tue, May 26, 1998 at 01:13:10PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 26, 1998 at 01:13:10PM -0400, Simon Shapiro wrote: > > On 23-May-98 Tom wrote: > > > > On Fri, 22 May 1998, Eivind Eklund wrote: > > > >> On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: > >> > Yes, it seems to be a sysinstall interaction. If I leave the space > >> > unallocated, and then disklabel and newfs it later, it works fine. > >> > > >> > Currently it is pretty hard to bootstrap a new DPT system. You have > >> > to > >> > be able to build a kernel somewhere else as sysinstall will install a > >> > non-DPT kernel, and you can't use sysinstall to allocate large DPT > >> > partitions. I fear for the new user. > >> > >> sysinstall doesn't do this anymore. The DPT driver is activated as > >> part of the standard sysinstall now. > > > > I've noticed that. But this won't help anyone until 2.2.7 is released, > > or somone makes a 2.2.6 snapshot with the new GENERIC kernel. > > I should have a kernel image in ftp://ftp.simon-shapiro.org/FreeBSD. This shouldn't be necessary any more - there are daily snapshots at ftp://releng22.freebsd.org/pub/FreeBSD including the DPT driver. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 09:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26301 for freebsd-scsi-outgoing; Tue, 26 May 1998 09:20:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26149; Tue, 26 May 1998 09:19:42 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id MAA17648; Tue, 26 May 1998 12:11:17 -0400 (EDT) Date: Tue, 26 May 1998 12:11:17 -0400 (EDT) From: Charles Owens Reply-To: Charles Owens To: Simon Shapiro cc: Raul Zighelboim , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Subject: RE: DPT install problem 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 On Tue, 26 May 1998, Simon Shapiro wrote: > > On 22-May-98 Raul Zighelboim wrote: > > > > My 0.02 cents: > > I did not installed FreeBSd on a DPT controller, but with an > > Adaptec controller. Nevertheless, I have a DPT controller on a system > > with a large fs (71780140 1K blocks). The system works, works well and > > has been up for 4 days as a very busy usenet news spool directory. > > This is running 2.2-RELENG from last sunday. > > This confirms my observations. Thanx. > > > As a sidebar; the DOS configuration software can only create arrays with > > up to 1 mbyte interleave. Is this a limitation on the hardware or the > > software ? Is (will there be) a way to create an array with a larger > > interleave (32 megs comes to mind). > > An interleave factor larger than 1MB will be very inefficient: > > a. The SCSI bus will be used (locked) for long periods. This will > cause poor multi-tasking response. > > b. The cache memory will be able to contain very few stripes. > > Also notice that in the context of FreeBSD, anything larger than 64K is > sort of mute, as the O/S limits all SCSI transfers to that size. I do not > know yet how CAM will do, but suspect it to be the same. > > Ideally, stripe size should be such that the latency in setting up a > transfer + the latency in completeing a DPT-Host transfer are about equal > to the time to transfer one block (the reality is a bit more complex than > that); In this manner, the DPT can continue to ``feed'' blocks to the > system (or the other way around) without pausing for disk. This is why a > multiple-bus equipped DPT can achive transfer rates that are limited by the > PCI bus and/or the O/S. This takes some careful tuning and experimentation. The setup I'm planning consists of 14 4.5GB UW (probably Seagate Cheetahs) drives split across two busses (using the DPT 3334UW/2). If you don't mind, could you comment a bit further as to what this tuning would entail in my case? The array will be at the heart of a file server cluster housing user and group home directories for 1300 or so users. Also, how much cache RAM on the controller is practically useful? Thanks, Charles > > > > ================================================== > > Raul Zighelboim rzig@verio.net > > > >> -----Original Message----- > >> From: Charles Owens [SMTP:owensc@enc.edu] > >> Sent: Friday, May 22, 1998 2:43 PM > >> To: Simon Shapiro > >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG > >> Subject: RE: DPT install problem > >> > >> On Fri, 22 May 1998, Simon Shapiro wrote: > >> > >> > > >> > On 21-May-98 Tom wrote: > >> > > > >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap > >> a new > >> > > DPT based system. However, sysinstall hangs after newfs'ing the > >> > > filesystems. > >> > > > >> > > I'm using a 21GB array, with auto-defaults for the filesystems, > >> so /usr > >> > > is over 20GB in size. If I delete /usr and replace it with a > >> 500MB > >> > > filesystem, leaving the remaining space unallocated, sysinstall > >> has no > >> > > problem completing the newfs step. > >> > > > >> > > Anyone else had problems with sysinstall on a mid-sized array > >> like > >> > > this? > >> > > >> > Yup. Me :-) > >> > But not on 3.0-current. I noticed that 2.2 does not like huge > >> partitions, > >> > but this is not consnstent. > >> > > >> > Simon > >> > >> This has me a bit nervous. This July I will be implementing an NFS > >> server > >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... > >> but > >> perhaps 3.0-current is my only choice? Is this -stable problem > >> understood, with a fix coming any time soon? > >> > >> Any other concerns that I should be sweating about as I'm planning on > >> building an array of this size? (and it will probably double in size > >> the > >> following summer) > >> > >> Thanks, > >> --- > >> ---------------------------------------------------------------------- > >> --- > >> Charles N. Owens Email: > >> owensc@enc.edu > >> > >> http://www.enc.edu/~owensc > >> Network & Systems Administrator > >> Information Technology Services "Outside of a dog, a book is a > >> man's > >> Eastern Nazarene College best friend. Inside of a dog it's > >> too dark to read." - Groucho Marx > >> ---------------------------------------------------------------------- > >> --- > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-scsi" in the body of the message > > --- > > > Sincerely Yours, > > Simon Shapiro Shimon@Simon-Shapiro.ORG > 770.265.7340 > --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 10:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09251 for freebsd-scsi-outgoing; Tue, 26 May 1998 10:22:09 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09241 for ; Tue, 26 May 1998 10:22:06 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 18792 invoked by uid 1000); 26 May 1998 18:23:47 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 26 May 1998 14:23:47 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Charles Owens Subject: RE: DPT install problem Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, Raul Zighelboim Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-May-98 Charles Owens wrote: > On Tue, 26 May 1998, Simon Shapiro wrote: > >> >> On 22-May-98 Raul Zighelboim wrote: >> > >> > My 0.02 cents: >> > I did not installed FreeBSd on a DPT controller, but with an >> > Adaptec controller. Nevertheless, I have a DPT controller on a system >> > with a large fs (71780140 1K blocks). The system works, works well >> > and >> > has been up for 4 days as a very busy usenet news spool directory. >> > This is running 2.2-RELENG from last sunday. >> >> This confirms my observations. Thanx. >> >> > As a sidebar; the DOS configuration software can only create arrays >> > with >> > up to 1 mbyte interleave. Is this a limitation on the hardware or the >> > software ? Is (will there be) a way to create an array with a larger >> > interleave (32 megs comes to mind). >> >> An interleave factor larger than 1MB will be very inefficient: >> >> a. The SCSI bus will be used (locked) for long periods. This will >> cause poor multi-tasking response. >> >> b. The cache memory will be able to contain very few stripes. >> >> Also notice that in the context of FreeBSD, anything larger than 64K is >> sort of mute, as the O/S limits all SCSI transfers to that size. I do >> not >> know yet how CAM will do, but suspect it to be the same. >> >> Ideally, stripe size should be such that the latency in setting up a >> transfer + the latency in completeing a DPT-Host transfer are about >> equal >> to the time to transfer one block (the reality is a bit more complex >> than >> that); In this manner, the DPT can continue to ``feed'' blocks to the >> system (or the other way around) without pausing for disk. This is why >> a >> multiple-bus equipped DPT can achive transfer rates that are limited by >> the >> PCI bus and/or the O/S. This takes some careful tuning and >> experimentation. > > The setup I'm planning consists of 14 4.5GB UW (probably Seagate > Cheetahs) > drives split across two busses (using the DPT 3334UW/2). If you don't > mind, could you comment a bit further as to what this tuning would entail > in my case? > > The array will be at the heart of a file server cluster housing user and > group home directories for 1300 or so users. > > Also, how much cache RAM on the controller is practically useful? Use the default stripe size (32k-64K). When selecting drives, alternate between the busses. Use top quality cabling and termination. Leave 1 drive as a hot spare. Experiment with your application and stripe sizes (although for home directories, anything 16K and above will work. Try to split the array into several filesystems; fsck on 50GB takes a while. AS much cache as possible. Cannot have too much. Play with the percentage of read-ahead and the percentage of dirty pages in dptmgr. Play with individual drives' cache parameters too. Post the results (or at least send them to me). Seriously consider using DPT drives, and DPT ECC memory, if possible, in DPT cabinets. You will get a much more reliable setup, with easier maintenance. Simon > > Thanks, > Charles > >> > >> > ================================================== >> > Raul Zighelboim rzig@verio.net >> > >> >> -----Original Message----- >> >> From: Charles Owens [SMTP:owensc@enc.edu] >> >> Sent: Friday, May 22, 1998 2:43 PM >> >> To: Simon Shapiro >> >> Cc: Tom; freebsd-stable@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG >> >> Subject: RE: DPT install problem >> >> >> >> On Fri, 22 May 1998, Simon Shapiro wrote: >> >> >> >> > >> >> > On 21-May-98 Tom wrote: >> >> > > >> >> > > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to >> >> > > bootstrap >> >> a new >> >> > > DPT based system. However, sysinstall hangs after newfs'ing the >> >> > > filesystems. >> >> > > >> >> > > I'm using a 21GB array, with auto-defaults for the filesystems, >> >> so /usr >> >> > > is over 20GB in size. If I delete /usr and replace it with a >> >> 500MB >> >> > > filesystem, leaving the remaining space unallocated, sysinstall >> >> has no >> >> > > problem completing the newfs step. >> >> > > >> >> > > Anyone else had problems with sysinstall on a mid-sized array >> >> like >> >> > > this? >> >> > >> >> > Yup. Me :-) >> >> > But not on 3.0-current. I noticed that 2.2 does not like huge >> >> partitions, >> >> > but this is not consnstent. >> >> > >> >> > Simon >> >> >> >> This has me a bit nervous. This July I will be implementing an NFS >> >> server >> >> with a 60GB DTP-based array. My plan has been to use 2.2-stable... >> >> but >> >> perhaps 3.0-current is my only choice? Is this -stable problem >> >> understood, with a fix coming any time soon? >> >> >> >> Any other concerns that I should be sweating about as I'm planning on >> >> building an array of this size? (and it will probably double in size >> >> the >> >> following summer) >> >> >> >> Thanks, >> >> --- >> >> ---------------------------------------------------------------------- >> >> --- >> >> Charles N. Owens Email: >> >> owensc@enc.edu >> >> >> >> http://www.enc.edu/~owensc >> >> Network & Systems Administrator >> >> Information Technology Services "Outside of a dog, a book is a >> >> man's >> >> Eastern Nazarene College best friend. Inside of a dog it's >> >> too dark to read." - Groucho Marx >> >> ---------------------------------------------------------------------- >> >> --- >> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> >> with "unsubscribe freebsd-scsi" in the body of the message >> >> --- >> >> >> Sincerely Yours, >> >> Simon Shapiro >> Shimon@Simon-Shapiro.ORG >> 770.265.7340 >> > > --- > ------------------------------------------------------------------------- > Charles N. Owens Email: owensc@enc.edu > http://www.enc.edu/~owensc > Network & Systems Administrator > Information Technology Services "Outside of a dog, a book is a man's > Eastern Nazarene College best friend. Inside of a dog it's > too dark to read." - Groucho Marx > ------------------------------------------------------------------------- > > --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 10:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12384 for freebsd-scsi-outgoing; Tue, 26 May 1998 10:39:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12355; Tue, 26 May 1998 10:39:34 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA20179; Tue, 26 May 1998 12:39:04 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261739.MAA20179@dyson.iquest.net> Subject: Re: DPT install problem In-Reply-To: from Simon Shapiro at "May 26, 98 01:06:15 pm" To: shimon@simon-shapiro.org Date: Tue, 26 May 1998 12:39:04 -0500 (EST) Cc: mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 > > On 22-May-98 Mike Smith wrote: > >> > >> > However, there are a couple of things that you personally (and other > >> > concerned users) can do to help the situation. > >> > > >> > - Contribute commentary (as you have), documentation and source/ > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > >> > your support means that it will continue to improve. > >> > - Donate a DPT controller to our testing pool so that we can test > >> > with it. Chances are we can scrape enough disks together in one > >> > place to meet the 20GB mark if we have one. > >> > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > >> to > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > Then we need some accountability from these prominent figures. Where > > is their feedback on this discussion? > Do you want working kernel threads and SMP or DPT support? I am working feverishly on the SMP and kernel threads stuff, and physically cannot do any more in the day. I do plan to work on the DPT stuff, but I can only do one type of thing at a time... John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 12:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07637 for freebsd-scsi-outgoing; Tue, 26 May 1998 12:54:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07631; Tue, 26 May 1998 12:54:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00549; Tue, 26 May 1998 11:47:18 -0700 (PDT) Message-Id: <199805261847.LAA00549@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John S. Dyson" cc: shimon@simon-shapiro.org, mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Tue, 26 May 1998 12:39:04 CDT." <199805261739.MAA20179@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 11:47:18 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > On 22-May-98 Mike Smith wrote: > > >> > > >> > However, there are a couple of things that you personally (and other > > >> > concerned users) can do to help the situation. > > >> > > > >> > - Contribute commentary (as you have), documentation and source/ > > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > > >> > your support means that it will continue to improve. > > >> > - Donate a DPT controller to our testing pool so that we can test > > >> > with it. Chances are we can scrape enough disks together in one > > >> > place to meet the 20GB mark if we have one. > > >> > > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > > >> to > > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > > > Then we need some accountability from these prominent figures. Where > > > is their feedback on this discussion? > > > Do you want working kernel threads and SMP or DPT support? I am working > feverishly on the SMP and kernel threads stuff, and physically cannot do > any more in the day. I just want to know what these people are doing if not answering questions. Guessing and begging users for input is traditional stuff, but if there's a better alternative, I'm all for it. > I do plan to work on the DPT stuff, but I can only do one type of thing > at a time... Sounds reasonable to me. What we need are some underlings for you to boss around doing your grunt work. JD and the moonshine gang? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 May 26 14:37:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25107 for freebsd-scsi-outgoing; Tue, 26 May 1998 14:37:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25082; Tue, 26 May 1998 14:37:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA00792; Tue, 26 May 1998 15:37:04 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805262137.PAA00792@panzer.plutotech.com> Subject: Re: DPT install problem In-Reply-To: from Simon Shapiro at "May 26, 98 12:58:53 pm" To: shimon@simon-shapiro.org Date: Tue, 26 May 1998 15:37:03 -0600 (MDT) Cc: rzig@verio.net, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, tom@sdf.com, owensc@enc.edu X-Mailer: ELM [version 2.4ME+ PL28s (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 Simon Shapiro wrote... > On 22-May-98 Raul Zighelboim wrote: > > As a sidebar; the DOS configuration software can only create arrays with > > up to 1 mbyte interleave. Is this a limitation on the hardware or the > > software ? Is (will there be) a way to create an array with a larger > > interleave (32 megs comes to mind). > > An interleave factor larger than 1MB will be very inefficient: > > a. The SCSI bus will be used (locked) for long periods. This will > cause poor multi-tasking response. > > b. The cache memory will be able to contain very few stripes. > > Also notice that in the context of FreeBSD, anything larger than 64K is > sort of mute, as the O/S limits all SCSI transfers to that size. I do not > know yet how CAM will do, but suspect it to be the same. It will be the same. The 64K limitation is a generic FreeBSD limitation, so CAM won't change it. CAM won't limit it, though. Here at Pluto, we've been running large chunks (> 64K) through CAM and the Adaptec driver by passing physical memory addresses in through the passthrough driver. (and therefore you bypass the whole struct buf thing and physio) If we ever get a buffer chaining (or similar) scheme in place, it'll be possible to do any size I/O without jumping through hoops. > > Thanks, Simon, for a job well done. > > Thanx. I am going to get started on CAM port in the next few days. Good deal. Contact me via private email about getting access to the CAM source repository. 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 Tue May 26 14:48:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27893 for freebsd-scsi-outgoing; Tue, 26 May 1998 14:48:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27760; Tue, 26 May 1998 14:48:03 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA17993; Tue, 26 May 1998 21:48:01 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA29607; Tue, 26 May 1998 23:47:56 +0200 (MET DST) Message-ID: <19980526234755.44290@follo.net> Date: Tue, 26 May 1998 23:47:55 +0200 From: Eivind Eklund To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem References: <199805261739.MAA20179@dyson.iquest.net> <199805261847.LAA00549@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com>; from Mike Smith on Tue, May 26, 1998 at 11:47:18AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 26, 1998 at 11:47:18AM -0700, Mike Smith wrote: > > Do you want working kernel threads and SMP or DPT support? I am working > > feverishly on the SMP and kernel threads stuff, and physically cannot do > > any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. I'm answering all questions I can. I can't answer questions about true 20GB DPT arrays with more than guesses for at the absolute mimimum four more months. Every question you've had I've tried to answer if I could give any information :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 15:39:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08776 for freebsd-scsi-outgoing; Tue, 26 May 1998 15:39:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08760; Tue, 26 May 1998 15:39:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01429; Tue, 26 May 1998 14:32:33 -0700 (PDT) Message-Id: <199805262132.OAA01429@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Mike Smith , Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Tue, 26 May 1998 13:06:15 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 14:32:33 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> An ajacent problem, is that fsck will fail on such filesystems. > >> The failure mode is fsck -p in /etc/rc. It does not have, by default > >> enough resources to run a large parallel fsck. I added the following to > >> /etc/rc: > > > > You should update the daemon class in /etc/login.conf. Can you verify > > that the current settings there (/usr/src/etc/login.conf) are adequate? > > I am using (as of today, still to be tried): > > # > # Settings used by /etc/rc > # > daemon:\ > :coredumpsize@:\ > :coredumpsize-cur=0:\ > :datasize=infinity:\ > :datasize-cur@:\ > :maxproc=512:\ > :maxproc-cur@:\ > :memoryuse-cur=infinity:\ > :memorylocked-cur=infinity:\ > :openfiles=1024:\ > :openfiles-cur@:\ > :stacksize=infinity:\ > :stacksize-cur@:\ > :tc=default: untried ie. you haven't verified whether this configuration works or fails, correct? > BTW, what is foo@ in this file? from 'man 3 getcap' (whence you are referred from login.conf(5)) When a database is searched for a capability record, the first matching record in the search is returned. When a record is scanned for a capa- bility, the first matching capability is returned; the capability :nameT@: will hide any following definition of a value of type T for name; and the capability :name@: will prevent any following values of name from being seen. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 May 26 15:59:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13986 for freebsd-scsi-outgoing; Tue, 26 May 1998 15:59:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA13949 for ; Tue, 26 May 1998 15:58:57 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1524 invoked by uid 1000); 27 May 1998 00:00:11 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com> Date: Tue, 26 May 1998 20:00:11 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, tom@sdf.com, "John S.Dyson" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-May-98 Mike Smith wrote: ... >> Do you want working kernel threads and SMP or DPT support? I am working >> feverishly on the SMP and kernel threads stuff, and physically cannot do >> any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. I will have my home lab up and running in the next few days (week?). Any offer of help in unpacking 200 boxes is welcome. Once this is done, I'll have a bit more in DPT hardware for testing. I only can test large arrays on 3.0, as Sendero is the only really large array I have here. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 16:31:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19271 for freebsd-scsi-outgoing; Tue, 26 May 1998 16:31:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19266 for ; Tue, 26 May 1998 16:31:41 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1878 invoked by uid 1000); 27 May 1998 00:32:55 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805262132.OAA01429@dingo.cdrom.com> Date: Tue, 26 May 1998 20:32:55 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-May-98 Mike Smith wrote: >> >> An ajacent problem, is that fsck will fail on such filesystems. >> >> The failure mode is fsck -p in /etc/rc. It does not have, by default >> >> enough resources to run a large parallel fsck. I added the following >> >> to >> >> /etc/rc: >> > >> > You should update the daemon class in /etc/login.conf. Can you verify >> > that the current settings there (/usr/src/etc/login.conf) are >> > adequate? >> >> I am using (as of today, still to be tried): >> >> # >> # Settings used by /etc/rc >> # >> daemon:\ >> :coredumpsize@:\ >> :coredumpsize-cur=0:\ >> :datasize=infinity:\ >> :datasize-cur@:\ >> :maxproc=512:\ >> :maxproc-cur@:\ >> :memoryuse-cur=infinity:\ >> :memorylocked-cur=infinity:\ >> :openfiles=1024:\ >> :openfiles-cur@:\ >> :stacksize=infinity:\ >> :stacksize-cur@:\ >> :tc=default: > > untried ie. you haven't verified whether this configuration works or > fails, correct? Seems to work under 3.0-current as of last week. No idea about 2.2 :-( > >> BTW, what is foo@ in this file? > > from 'man 3 getcap' (whence you are referred from login.conf(5)) > > When a database is searched for a capability record, the first > matching > record in the search is returned. When a record is scanned for a > capa- > bility, the first matching capability is returned; the capability > :nameT@: will hide any following definition of a value of type T for > name; and the capability :name@: will prevent any following values > of > name from being seen. Sounds elaborate. An example will help (I am slower than usual today :-) Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 16:33:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19575 for freebsd-scsi-outgoing; Tue, 26 May 1998 16:33:37 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19556 for ; Tue, 26 May 1998 16:33:29 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1905 invoked by uid 1000); 27 May 1998 00:34:42 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805262137.PAA00792@panzer.plutotech.com> Date: Tue, 26 May 1998 20:34:42 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Kenneth D. Merry" Subject: Re: DPT install problem Cc: owensc@enc.edu, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, rzig@verio.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-May-98 Kenneth D. Merry wrote: > Simon Shapiro wrote... >> On 22-May-98 Raul Zighelboim wrote: >> > As a sidebar; the DOS configuration software can only create arrays >> > with >> > up to 1 mbyte interleave. Is this a limitation on the hardware or the >> > software ? Is (will there be) a way to create an array with a larger >> > interleave (32 megs comes to mind). >> >> An interleave factor larger than 1MB will be very inefficient: >> >> a. The SCSI bus will be used (locked) for long periods. This will >> cause poor multi-tasking response. >> >> b. The cache memory will be able to contain very few stripes. >> >> Also notice that in the context of FreeBSD, anything larger than 64K is >> sort of mute, as the O/S limits all SCSI transfers to that size. I do >> not >> know yet how CAM will do, but suspect it to be the same. > > It will be the same. The 64K limitation is a generic FreeBSD > limitation, so CAM won't change it. CAM won't limit it, though. Here at > Pluto, we've been running large chunks (> 64K) through CAM and the > Adaptec > driver by passing physical memory addresses in through the passthrough > driver. (and therefore you bypass the whole struct buf thing and physio) Ugly :-) We need this type of support in raw devices, though, so userland can pass it in reasonable manner. > If we ever get a buffer chaining (or similar) scheme in place, > it'll be possible to do any size I/O without jumping through hoops. > >> > Thanks, Simon, for a job well done. >> >> Thanx. I am going to get started on CAM port in the next few days. > > Good deal. Contact me via private email about getting access to > the CAM source repository. > > Ken > -- > Kenneth Merry > ken@plutotech.com --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 17:24:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29050 for freebsd-scsi-outgoing; Tue, 26 May 1998 17:24:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28840; Tue, 26 May 1998 17:22:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA07565; Wed, 27 May 1998 10:22:38 +1000 Date: Wed, 27 May 1998 10:22:38 +1000 From: Bruce Evans Message-Id: <199805270022.KAA07565@godzilla.zeta.org.au> To: ken@plutotech.com, shimon@simon-shapiro.org Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It will be the same. The 64K limitation is a generic FreeBSD >limitation, so CAM won't change it. CAM won't limit it, though. Here at Except in theory anyone can recompile the kernel with a higher limit, and the limit is actually 124K for IDE... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 26 19:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14739 for freebsd-scsi-outgoing; Tue, 26 May 1998 19:03:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14494; Tue, 26 May 1998 19:02:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02549; Tue, 26 May 1998 17:56:23 -0700 (PDT) Message-Id: <199805270056.RAA02549@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Mike Smith , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Subject: cap-format databases (was Re: DPT install problem ) In-reply-to: Your message of "Tue, 26 May 1998 20:32:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 17:56:23 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > >> BTW, what is foo@ in this file? > > > > from 'man 3 getcap' (whence you are referred from login.conf(5)) > > > > When a database is searched for a capability record, the first > > matching > > record in the search is returned. When a record is scanned for a > > capa- > > bility, the first matching capability is returned; the capability > > :nameT@: will hide any following definition of a value of type T for > > name; and the capability :name@: will prevent any following values > > of > > name from being seen. > > Sounds elaborate. An example will help (I am slower than usual today :-) Read the getcap(3) manpage. A simple example: foo: :bar#33:baz: fish: :zog#1:bar@:tc=foo: Retrieving the 'foo' entry gives the capabilities: bar = 33 baz = true Retrieving the 'fish' entry gives the capabilities: zog = 1 baz = true ie. the presence of the 'bar@' entry in 'fish' suppresses the 'bar' capibility when 'foo' is included. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 May 27 05:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21766 for freebsd-scsi-outgoing; Wed, 27 May 1998 05:49:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21756; Wed, 27 May 1998 05:49:34 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA24357; Wed, 27 May 1998 22:49:28 +1000 Date: Wed, 27 May 1998 22:49:28 +1000 From: Bruce Evans Message-Id: <199805271249.WAA24357@godzilla.zeta.org.au> To: eivind@yes.no, mike@smith.net.au Subject: Re: DPT install problem Cc: current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >However, as long as the issue is only the size of the partitions, I >think there are better ways of solving this - e.g, a compressing >variant of the vn device. This would let regression testing run on >any box, instead of having to throw away 20GB of diskspace. (There >were also some hints about more issues in one of Tom's messages). Or the standard variant of the vn devices. It already compresses never-written-to blocks to 4 bytes each. I have tested files of size 16TB-1 and filesystems of size 1TB-512 on vn devices. A 1TB file system with 33 cylinder groups of size 31GB each took only 78 seconds to newfs and 70 seconds to fsck (when it was empty :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 08:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21808 for freebsd-scsi-outgoing; Wed, 27 May 1998 08:34:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21799 for ; Wed, 27 May 1998 08:34:12 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-226.HiWAAY.net [208.147.148.226]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id KAA21283 for ; Wed, 27 May 1998 10:34:08 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id KAA11608 for ; Wed, 27 May 1998 10:25:25 -0500 (CDT) Message-Id: <199805271525.KAA11608@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: ncr problem? From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 10:25:25 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This system is running RELENG_2_2 as of the evening of April 20. "options FAILSAFE" is in my config file. % uname -a FreeBSD nospam.hiwaay.net 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Mon Apr 20 20:49:10 CDT 1998 root@nospam.hiwaay.net:/usr/src/sys/compile/PPRO200 i386 Reported this problem several weeks ago but got no replies: May 1 21:37:46 nospam /kernel: ncr0:0: ERROR (20:0) (8-0-0) (f/3d) @ (script 418:c0000004). May 1 21:37:46 nospam /kernel: ncr0: script cmd = c1000060 May 1 21:37:46 nospam /kernel: ncr0: regdump: da 00 00 3d 47 0f 00 0f 20 08 80 00 00 00 07 0a. May 1 21:37:46 nospam /kernel: ncr0: have to clear fifos. May 1 21:37:46 nospam /kernel: ncr0: restart (fatal error). May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): COMMAND FAILED (9 ff) @f07b5800. May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted May 1 21:37:46 nospam /kernel: , retries:3 May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): WIDE SCSI (16 bit) enabledsd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) May 1 21:53:51 nospam /kernel: ncr0:0: ERROR (81:0) (8-0-0) (f/3d) @ (mem 322828:00000000). May 1 21:53:51 nospam /kernel: ncr0: regdump: da 00 40 3d 47 0f 00 0f 35 08 80 00 80 00 0f 0a. May 1 21:53:51 nospam /kernel: ncr0: restart (fatal error). May 1 21:53:51 nospam /kernel: sd1(ncr0:0:0): COMMAND FAILED (9 ff) @f07b5800. May 1 21:53:51 nospam /kernel: sd1(ncr0:0:0): WIDE SCSI (16 bit) enabledsd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) May 1 21:53:55 nospam /kernel: pid 16320 (XF86_Mach32), uid 0: exited on signal 6 And now another occured: May 26 19:24:20 nospam /kernel: ncr0:0: ERROR (81:0) (8-0-0) (f/3d) @ (script 424:c1000060). May 26 19:24:20 nospam /kernel: ncr0: script cmd = 725d0000 May 26 19:24:20 nospam /kernel: ncr0: regdump: da 00 00 3d 47 0f 00 0f 20 08 00 00 80 00 0f 0a. May 26 19:24:20 nospam /kernel: ncr0: restart (fatal error). May 26 19:24:20 nospam /kernel: sd1(ncr0:0:0): COMMAND FAILED (9 ff) @f07b5800. May 26 19:24:20 nospam /kernel: sd1(ncr0:0:0): WIDE SCSI (16 bit) enabledsd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) At the very least, can somebody decode the above and explain? Bad blocks? Disk? Card? This is what dmesg has to say (at boot) about my SCSI stuff: ahc0 rev 0 int a irq 9 on pci0:9:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST32550N 0021" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) (ahc0:5:0): "ARCHIVE Python 28388-XXX 4.CM" type 1 removable SCSI 2 st0(ahc0:5:0): Sequential-Access density code 0x13, drive empty (ahc0:6:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2 st1(ahc0:6:0): Sequential-Access density code 0x0, drive empty ncr0 rev 3 int a irq 11 on pci0:11:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) (ncr0:0:0): "IBM OEM DCHS09W 2222" type 0 fixed SCSI 2 sd1(ncr0:0:0): Direct-Access sd1(ncr0:0:0): WIDE SCSI (16 bit) enabled sd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) 8689MB (17796077 512 byte sectors) Just today I was planning on pulling the little 2G drive off the 2940 for Macintosh use. Was thinking about leaving the 2940 in for tape drives only, also thinking about using the narrow internal connector on the Asus SC875 for the tape drives. But if funny things are happening I'd rather not mess with what works. Then again, maybe moving the tapes to to ncr0 would break things bad enough to find the problem? Any ideas? Firmware in the IBM 9G drive? Firmware on the '875? Bad cables? -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 08:38:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22903 for freebsd-scsi-outgoing; Wed, 27 May 1998 08:38:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22838 for ; Wed, 27 May 1998 08:38:38 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 21913 invoked by uid 1000); 27 May 1998 16:39:56 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805270022.KAA07565@godzilla.zeta.org.au> Date: Wed, 27 May 1998 12:39:56 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Bruce Evans Subject: Re: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com, ken@plutotech.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-May-98 Bruce Evans wrote: >> It will be the same. The 64K limitation is a generic FreeBSD >>limitation, so CAM won't change it. CAM won't limit it, though. Here at > > Except in theory anyone can recompile the kernel with a higher limit, > and the limit is actually 124K for IDE... I am not so sure this is really a good thing to do. Except as necessary for particular applications. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 11:31:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27485 for freebsd-scsi-outgoing; Wed, 27 May 1998 11:31:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27444; Wed, 27 May 1998 11:31:24 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id LAA11461; Wed, 27 May 1998 11:29:22 -0700 (MST) From: "Chad R. Larson" Message-Id: <199805271829.LAA11461@freebie.dcfinc.com> Subject: Re: DPT install problem To: bde@zeta.org.au (Bruce Evans) Date: Wed, 27 May 1998 11:29:21 -0700 (MST) Cc: ken@plutotech.com, shimon@simon-shapiro.org, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com In-Reply-To: <199805270022.KAA07565@godzilla.zeta.org.au> from Bruce Evans at "May 27, 98 10:22:38 am" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (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 > It will be the same. The 64K limitation is a generic FreeBSD > limitation, so CAM won't change it. CAM won't limit it, though. I feel like I walked into the middle of a conversation. What, exactly, is CAM? Why would I be interested in it? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 11:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01636 for freebsd-scsi-outgoing; Wed, 27 May 1998 11:53:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw.jmrodgers.com (gw.jmrodgers.com [205.247.224.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01574; Wed, 27 May 1998 11:52:49 -0700 (PDT) (envelope-from meuston@jmrodgers.com) Received: from max.jmrodgers.com (max.jmrodgers.com [205.247.224.209]) by gw.jmrodgers.com (8.8.8/8.8.8) with SMTP id OAA04153; Wed, 27 May 1998 14:51:41 -0400 (EDT) (envelope-from meuston@jmrodgers.com) Received: by localhost with Microsoft MAPI; Wed, 27 May 1998 14:51:40 -0400 Message-ID: <01BD897E.F511A1E0.meuston@jmrodgers.com> From: Max Euston To: "'chad@dcfinc.com'" Cc: "freebsd-scsi@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: RE: DPT install problem Date: Wed, 27 May 1998 14:51:37 -0400 Organization: J.M. Rodgers Co., Inc. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 On Wednesday, May 27, 1998 2:29 PM, Chad R. Larson [SMTP:chad@freebie.dcfinc.com] wrote: > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? See: ftp://ftp.freebsd.org/pub/FreeBSD/cam/README Max --- Max Euston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 11:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03080 for freebsd-scsi-outgoing; Wed, 27 May 1998 11:59:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03031 for ; Wed, 27 May 1998 11:59:19 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id LAA19494 for ; Wed, 27 May 1998 11:59:17 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Wed, 27 May 1998 11:59:17 -0700 (PDT) From: Chris Timmons To: freebsd-scsi@FreeBSD.ORG Subject: Micropolis 4345WS (Toshiba "Equium" 6200M) 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 received a couple of those Toshiba computers which Insight had the special on (intel dual p6 mb, integrated pro100 ethernet, aha-7880, etc.) The 12x atapi cd-room boots our freebsd CD's so quickly that you forget that you're booting from a CD. Really nice systems, but mine came with Micropolis 4345WS drives at firmware revision zC19. The manufacture date of my systems was around 4/97. Unfortunately I couldn't get any version of FreeBSD to install without the aha driver complaining about the drive timing out, and aborting the install. No matter what the settings on the 7880 (disable wide negotiation, throttle down xfer rate, etc) and after verifying drive jumpers, termination. As soon as sysinstall started doing anything disk intensive, the drives would lose it. I had both systems side by side with a pile of FreeBSD CD's and each behaved the same whether it was 2.2.2, 10/6/97 3.0-snap, 2/2/98 3.0-snap, etc. I did some searching around the net and learned that Micropolis has been history for a while. Fortunately firmware kit X502_4.exe is available from an ftp server in germany. I built an ASPI floppy (adaptec now gives away their dos/aspi drivers at their www page) and was able to upgrade the drive firmware. As soon as the firmware was upgraded all problems ceased. I haven't really thrashed the drive yet and cranked back up the xfer rate (& wide negotiation) so we'll see how the drive works under real load. Since other people have been buying these systems, I'm a little surprised that I'm the only person so far to have reported the problem. Fortunately it appears that there is a workaround (forget about any 5-year warranty on the tomahawk drives though :( -Chris p.s. a dejanews power search of 'micropolis AND firmware' works pretty good :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 12:14:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06305 for freebsd-scsi-outgoing; Wed, 27 May 1998 12:14:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06269; Wed, 27 May 1998 12:14:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id NAA05934; Wed, 27 May 1998 13:13:34 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805271913.NAA05934@panzer.plutotech.com> Subject: Re: DPT install problem In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com> from "Chad R. Larson" at "May 27, 98 11:29:21 am" To: chad@dcfinc.com Date: Wed, 27 May 1998 13:13:34 -0600 (MDT) Cc: bde@zeta.org.au, ken@plutotech.com, shimon@simon-shapiro.org, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, owensc@enc.edu, rzig@verio.net, tom@sdf.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Chad R. Larson wrote... > > It will be the same. The 64K limitation is a generic FreeBSD > > limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? See: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README 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 May 27 12:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07781 for freebsd-scsi-outgoing; Wed, 27 May 1998 12:20:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07539; Wed, 27 May 1998 12:19:46 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA07000; Wed, 27 May 1998 19:19:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA05352; Wed, 27 May 1998 21:19:36 +0200 (MET DST) Message-ID: <19980527211935.63164@follo.net> Date: Wed, 27 May 1998 21:19:35 +0200 From: Eivind Eklund To: chad@dcfinc.com Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: What CAM is (was Re: DPT install problem) References: <199805270022.KAA07565@godzilla.zeta.org.au> <199805271829.LAA11461@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com>; from Chad R. Larson on Wed, May 27, 1998 at 11:29:21AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 27, 1998 at 11:29:21AM -0700, Chad R. Larson wrote: > > It will be the same. The 64K limitation is a generic FreeBSD > > limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? CAM is the new disk subsystem, being implemented to follow the CAM specification. This system is used by Digital Unix at least, but I don't remember/know if that was where it originated. An API specification and guideline to writing CAM-based drivers is at http://www.partner.digital.com/www-swdev/pages/Home/TECH/documents/Digital_UNIX/V4.0/AA-PS3GD-TET1_html/TOC.html Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 12:46:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12624 for freebsd-scsi-outgoing; Wed, 27 May 1998 12:46:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA12489 for ; Wed, 27 May 1998 12:46:03 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4887 invoked by uid 1000); 27 May 1998 20:47:16 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805271829.LAA11461@freebie.dcfinc.com> Date: Wed, 27 May 1998 16:47:16 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: chad@dcfinc.com Subject: Re: DPT install problem Cc: tom@sdf.com, rzig@verio.net, owensc@enc.edu, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, ken@plutotech.com, (Bruce Evans) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 27-May-98 Chad R. Larson wrote: >> It will be the same. The 64K limitation is a generic FreeBSD >> limitation, so CAM won't change it. CAM won't limit it, though. > > I feel like I walked into the middle of a conversation. What, exactly, > is CAM? Why would I be interested in it? Like I say to my kids ``If you do not know, you do not need to know... ;-)'' Now seriously, from my perspective (Justin and others wrote and support it): It is a new, replacement kernel layer code that sits between the kernel lowest I/O abstraction layer and SCSI device drivers. It implements this layer according to some SCSI ANSI specifications as to how such layers should be written. If you are outside kernel internals, you should not care, except that it is totally incompatible with the existing way FreeBSD does the SCSI interfacing. This means that someone has to re-write the drivers so they work again. Quoted advantages to this move are many and best explained by those who wrote this code. The current DPT driver is not conpatible with this layer and will not be for several weeks to come. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 14:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03241 for freebsd-scsi-outgoing; Wed, 27 May 1998 14:18:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns.mauswerks.net (root@ns.mauswerks.com [204.152.96.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03212; Wed, 27 May 1998 14:18:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@[209.54.254.2]) by ns.mauswerks.net (8.8.0/8.6.9) with ESMTP id OAA14725; Wed, 27 May 1998 14:20:17 -0700 Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id OAA12696; Wed, 27 May 1998 14:18:17 -0700 Date: Wed, 27 May 1998 14:18:17 -0700 From: Matthew Jacob Message-Id: <199805272118.OAA12696@feral.com> To: chad@dcfinc.com, eivind@yes.no Subject: Re: What CAM is (was Re: DPT install problem) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Try also: http://www.symbios.com/x3t10/io/t10/drafts/cam/cam-r12b.pdf for the 'close to' formal ANSI specification. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 27 19:30:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06093 for freebsd-scsi-outgoing; Wed, 27 May 1998 19:30:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06034 for ; Wed, 27 May 1998 19:30:05 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id UAA08222; Wed, 27 May 1998 20:29:57 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805280229.UAA08222@panzer.plutotech.com> Subject: Re: Tape driver - What do we really want? In-Reply-To: from Hans Huebner at "May 22, 98 02:29:17 am" To: hans@artcom.de Date: Wed, 27 May 1998 20:29:57 -0600 (MDT) Cc: gibbs@pluto.plutotech.com, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 [ I've been inexcusably lazy in replying to this... ] Hans Huebner wrote... > Kenneth D. Merry wrote: > > Hans Huebner wrote... > > > > * Implement MTIOCGET fully > > > > We might want to have two versions of the > > MTIOCGET ioctl -- one with all the bells and whistles (i.e. density, > > compression, etc.) and one that uses the "traditional" structure that other > > machines accessing a FreeBSD box via the rmt protocol would understand. > > The "traditional" structure does provide for sending current position > > information, though. > > I am not sure whether the current rmt protocol is used at all. The mtget > structure is directly passed between the rmt client and server, which > makes the protocol non-interoperable between platforms. The system itself > does not use the mtget structure except in mt(1), all other references to > MTIOCGET seem to not use the returned data. > > I can't see what other applications do, but I suspect that nobody really > uses the mtget structure. Please correct me if I'm wrong. You're probably right. > > > * Create 'mt capabilities' command > > > > > > The permissible compression modes should be printable with a new > > > subcommand to mt, maybe 'capabilities'. Along the way, the permissible > > > modes of the tape should be made a list (contrasted to the four-mode > > > scheme we currently have). > > > > Right. If we're going to have a list of things, we should make it > > dynamic, not a fixed size. > > I'd even propose to pull the model- and vendor-specific driver > initialization out of the kernel into a user mode application. Basically, > this seems to require a get/set ioctl interface to the quirks of a device. > This will require documentation and review of quirks usage in the driver. > > The user-mode application would use standard CAM calls to access the mode > pages of the drive as well as on-disk configuration information to > determine the permissible modes and set up the driver-internal mode > configuration table or list. > > The default configuration should be sane enough to restore common tape > formats without having to perform elaborate initialization upon the > device, though. This is what we already have. Well, I would rather have the kernel automatically setup known drives. For unknown drives, or to override the kernel defaults, we could have some sort of config file or options to mt to setup various quirks or register capabilities for the device. What I want to avoid is the situation that you need to run mt or some other program in order for the driver to run optimally with the device. It would be acceptible to have to run mt to set quirks/capabilities if the drive in question is unknown to the kernel, but once we know enough about it, the device's capabilities and quirks should go into the kernel database. Another thing I would like to avoid is having mt groking through the passthrough driver and mode pages. mt is more of a generic magnetic tape interface, and so needs to be extensible to IDE and floppy based tape drives. > > > * Make mt work with remote tape drives > > > > > > The mt command should work with remote tape drives to the extent that the > > > rmt protocol allows. This is needed to support media changer servers > > > which, through a custom protocol, mount tapes at the request of > > > applications running on other systems in the network. > > > > Sounds interesting...but if the media changer servers in question > > use a custom protocol, how is adding rmt support to mt going to help? > > It would save me from having to implement a special mt-type utility to > remotely work with a tape drive. The changer protocol is only concerned > with media and drives, not with the data contained on the media. I see. Well, maybe what you could do is have device specific routines in separate files that are linked into mt. Then, based on a command line option mt would call the device-specific routines to formulate the rmt protocol commands to send to the remote device. > I'm well aware about the limitations of the rmt protocol. In practice, > using it to transfer data from or to a remote tape drive is often avoided > in favour of a transparent tcp data channel (e.g. rsh, ssh). It could be > useful for remote control, though (if mt would support remote tape > drives). Yeah, I can see how that would be cool. Something like: mt -f ken@hostname:/dev/nrsa0 fsf 2 I take it that's what you're talking about? 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 Thu May 28 10:22:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12310 for freebsd-scsi-outgoing; Thu, 28 May 1998 10:22:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12299 for ; Thu, 28 May 1998 10:22:38 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id TAA11392; Thu, 28 May 1998 19:20:56 +0200 Message-ID: <356D9CF8.1E7667F5@we.lc.ehu.es> Date: Thu, 28 May 1998 19:20:56 +0200 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: AHC: "cheksum error" reading SEEPROM with Iwill PIILS mb Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have just purchased a new system for running FreeBSD. It is based on the Iwill PIILS motherboard, which uses the 440LX chipset and includes an Adaptec 7880 SCSI controller. I'm running FreeBSD-stable now, but I have found a problem related to SCSI: When the AHC driver tries to read the 7880's SEEPROM, the operation fails with a "cheksum error". I'm afraid that the 7880 chip on my PIILS motherboard is different (perhaps another version?): for example, I cannot choose the termination type using the Adaptec SCSI BIOS ("High ON/Low ON", "High ON/Low Off"...); instead, I can only select "Enable" or "Disable". However, the "cheksum error" trying to read the 7880's SEEPROM does not prevent the AHC driver from working properly. Until now, I can use both the SCSI disk and CD-ROM without any problem. The version of the SCSISelect utility is 1.26S2. The BIOS is Award, version 4.51PG. And these are the codes on the 7880 chip: AIC7880P AQWA 750 722511 BF3671.1 I'm ready to make any tests on my system; however, in this case I will need some help from the person(s) responsible of the AHC driver. Cheers, -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 28 14:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26804 for freebsd-scsi-outgoing; Thu, 28 May 1998 14:13:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26788 for ; Thu, 28 May 1998 14:13:02 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id GAA25545; Fri, 29 May 1998 06:42:24 +0930 (CST) (envelope-from grog) Message-ID: <19980529064224.K25469@freebie.lemis.com> Date: Fri, 29 May 1998 06:42:24 +0930 From: Greg Lehey To: "m. w." Cc: FreeBSD SCSI Mailing List Subject: Re: plextor SCSI cdrom References: <19980528210858.1091.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980528210858.1091.qmail@hotmail.com>; from m. w. on Thu, May 28, 1998 at 02:08:57PM -0700 WWW-Home-Page: http://www.lemis.com/~grog 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 Thu, 28 May 1998 at 14:08:57 -0700, m. w. wrote: > > >>> Hi, people-- >>> I seem to have a slight problem with FreeBSD version 2.2.6 seeing >>> my cdrom and tape drive. I have an Adaptec AHA-2940UW controller with a >>> Plextor 12x cdrom and Conner tape drive running off of it. NT sees >>> everything just fine, but when I boot from the cd to install BSD, it >>> probes the controller and finds nothing on any of the id's. It gets an >>> unknown response and says that the board is not responding. On the fifth >>> id it should find the cdrom, but it passes over it just like everything >>> else. The cables and termination are just fine. I can get as far as >>> selecting which media I want to install from, and when I select cdrom, >>> it simply says it can't find one. If anyone has any ideas, they'd be >>> appreciated. >> >> Let's see the dmesg output. >> >> Greg > > Well, here's the stuff it gives me: > ----------------------------------------------------------- > Probing for devices on PCI bus 0: > (it finds my chipset here) > ahc0 rev 0 int a irq 10 on PCI > 0:11:0 > ahc0: aic 7880 Wide Channel, SCSI id = 7, 16SCBs > ahc0 waiting for scsi devices to settle > (ahc 0:0:0): "Seagate ST19171W 0023" type 0 fixed SCSI 2 > sdo (aho 0:0:0): Direct-Access 8683MB (lists clusters and stuff) > ahc0: board is not responding > (ahc 0:3:0): SCB 0x0 timedout in datain phase, SCSISIGI = 0x44 > SEQADDR = 0x128 SCSIEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 > (ahc 0:3:0): abort message in message buffer > ahc0: board is not responding > cmd fail > (ahc 0:3:0): SCB 0x1 timedout while recovery in progress > (ahc 0:3:0) "unknown unknown ????" type 13 fixed scsi 0 > uk0(ahc 0:3:0): Unknown > ahc0: board is not responding > (ahc 0:3:1): SCB 0x2 timedout while recovery in progress > (ahc 0:3:1): "unknown unknown ????" type 13 fixed scsi 0 > uk1(ahc0:3:1): Unknown > ahc0: board is not responding > cmd fail > ----------------------------------------------------------- > > It repeats this for every ID it probes, and then goes on with the rest > of the pci and isa detection, which has no problems. I'm pretty sure the > userconfig screen lists the drq and everything right, but I'll check > again. I haven't seen anything like this before. I'm copying the -scsi list. Maybe somebody there has an idea. Greg -- See complete headers for address 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 Thu May 28 17:39:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06692 for freebsd-scsi-outgoing; Thu, 28 May 1998 17:39:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06413; Thu, 28 May 1998 17:37:46 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 19:49:05 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> From: tcobb To: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Cc: "'simon@simon-shapiro.org'" Subject: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 19:49:04 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD CURRENT circa 5/18/98. I'm running the latest available firmware flash for the card, all on a P5-233MMX with 128MB RAM. Recently I lost a harddrive in my 24GB RAID5 array. The array was configured with a HOT SPARE which should have allowed it to rebuild completely online, with no interruption in service (except some minor slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER failed miserably. When my array went into degraded mode, the DPT DRIVER froze access to the partitions. Upon reboot, during device probe, the DPT DRIVER returned a 1 SECTOR (0 MB) sense for the array, despite the fact that the array was operating properly (though degraded). After this, the kernel panic'd before completing the boot process with a "Page Fault in Supervisor Mode" error, and continued to panic this way until the DPT Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and do it - doing the rebuild of that size RAID5 array takes more than an hour). After a complete rebuild, the DPT DRIVER showed the array sizes correctly. During this process, booting into DOS revealed the array to be fine, even while the array was degraded -- it also wasn't confused by degraded mode and showed correct partition information. I believe that the DPT DRIVER is not correctly sensing that the array is okay, even though it is in degraded mode, and incorrectly returns sector/MB values which panic the kernel. I don't recommend depending on the proper operation of this driver for your High-Availability needs. HISTORY I've used DPT in FreeBSD since last November, first with the hacked 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing me about once per week. As 2.2.6, the MBUF leak disappeared and was replaced with a once every 2-3 day panic which it appeared was not going to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet and upgraded recently to 3.0, which seemed to fix both of these prior panics only to reveal that the supposedly "high availability" software driver for my HA hardware is miserable during the most critical times. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 28 19:50:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00927 for freebsd-scsi-outgoing; Thu, 28 May 1998 19:50:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00852; Thu, 28 May 1998 19:49:59 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 22:49:23 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> From: tcobb To: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 22:49:23 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD CURRENT circa 5/18/98. I'm running the latest available firmware flash for the card, all on a P5-233MMX with 128MB RAM. Recently I lost a harddrive in my 24GB RAID5 array. The array was configured with a HOT SPARE which should have allowed it to rebuild completely online, with no interruption in service (except some minor slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER failed miserably. When my array went into degraded mode, the DPT DRIVER froze access to the partitions. Upon reboot, during device probe, the DPT DRIVER returned a 1 SECTOR (0 MB) sense for the array, despite the fact that the array was operating properly (though degraded). After this, the kernel panic'd before completing the boot process with a "Page Fault in Supervisor Mode" error, and continued to panic this way until the DPT Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and do it - doing the rebuild of that size RAID5 array takes more than an hour). After a complete rebuild, the DPT DRIVER showed the array sizes correctly. During this process, booting into DOS revealed the array to be fine, even while the array was degraded -- it also wasn't confused by degraded mode and showed correct partition information. I believe that the DPT DRIVER is not correctly sensing that the array is okay, even though it is in degraded mode, and incorrectly returns sector/MB values which panic the kernel. I don't recommend depending on the proper operation of this driver for your High-Availability needs. HISTORY I've used DPT in FreeBSD since last November, first with the hacked 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing me about once per week. As 2.2.6, the MBUF leak disappeared and was replaced with a once every 2-3 day panic which it appeared was not going to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet and upgraded recently to 3.0, which seemed to fix both of these prior panics only to reveal that the supposedly "high availability" software driver for my HA hardware is miserable during the most critical times. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 28 20:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03810 for freebsd-scsi-outgoing; Thu, 28 May 1998 20:08:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03805; Thu, 28 May 1998 20:08:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA02883; Thu, 28 May 1998 19:03:46 -0700 (PDT) Message-Id: <199805290203.TAA02883@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" , "'simon@simon-shapiro.org'" Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Thu, 28 May 1998 19:49:04 EDT." <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 19:03:46 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > HISTORY > I've used DPT in FreeBSD since last November, first with the hacked > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing > me about once per week. As 2.2.6, the MBUF leak disappeared and was > replaced with a once every 2-3 day panic which it appeared was not going > to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet > and upgraded recently to 3.0, which seemed to fix both of these prior > panics only to reveal that the supposedly "high availability" software > driver for my HA hardware is miserable during the most critical times. Given that biodone is only called from disk drivers, and I guess you're probably only using the DPT driver, it sounds like your two problems are one. Certainly, given that 3.0 upgrade was taken against the indicators, it's hard to feel that many of your accusations are terribly justifiable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 May 28 20:55:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10355 for freebsd-scsi-outgoing; Thu, 28 May 1998 20:55:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10313; Thu, 28 May 1998 20:55:29 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 23:54:50 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 23:54:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Thursday, May 28, 1998 10:04 PM > To: tcobb > Cc: 'freebsd-current@freebsd.org'; 'freebsd-scsi@freebsd.org'; > 'simon@simon-shapiro.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > > HISTORY > > I've used DPT in FreeBSD since last November, first with the hacked > > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that > was crashing > > me about once per week. As 2.2.6, the MBUF leak disappeared and was > > replaced with a once every 2-3 day panic which it appeared > was not going > > to get fixed by anyone (bidone: buffer not busy). So, I > bit the bullet > > and upgraded recently to 3.0, which seemed to fix both of > these prior > > panics only to reveal that the supposedly "high > availability" software > > driver for my HA hardware is miserable during the most > critical times. > > Given that biodone is only called from disk drivers, and I > guess you're > probably only using the DPT driver, it sounds like your two problems > are one. > > Certainly, given that 3.0 upgrade was taken against the > indicators, it's > hard to feel that many of your accusations are terribly justifiable. Excuse me? Could you please explain what you mean by "taken against the indicators"? It was clear from talking to more than one person on the core team that the biodone issues were unlikely to get resolved in -stable. This, plus deficiencies in the -stable NFS code (and other -stable instabilities) caused me to have to upgrade this machine to -current in order to keep using FreeBSD for it. I was quite reluctant to do this, believe me. But it was the best recommendation I was given. My problem report (most of which you snipped) pointed out a deficiency in the DPT driver code which renders it useless in HA applications. I believe that this deficiency is likely to be present in ALL VERSIONS of this code, unless suddenly, people are putting the newest code in the oldest versions of the OS. "Indicators" are that I shouldn't be using FreeBSD for any High Availability or critical operations -- I AM using FreeBSD for > 15 live servers. Now, what was your point? -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 02:44:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29434 for freebsd-scsi-outgoing; Fri, 29 May 1998 02:44:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29402; Fri, 29 May 1998 02:44:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA07262; Fri, 29 May 1998 09:44:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA25768; Fri, 29 May 1998 11:44:21 +0200 (MET DST) Message-ID: <19980529114301.44319@follo.net> Date: Fri, 29 May 1998 11:43:01 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net>; from tcobb on Thu, May 28, 1998 at 10:49:23PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 28, 1998 at 10:49:23PM -0400, tcobb wrote: > I believe that the DPT DRIVER is not correctly sensing that the array is > okay, even though it is in degraded mode, and incorrectly returns > sector/MB values which panic the kernel. I don't recommend depending on > the proper operation of this driver for your High-Availability needs. I have an older DPT, but I still want to add my experiences to the above: (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded mode. This has worked just fine with the driver in -current, with the RAID full (of partitions, not data. I can't understand that the amount of data should make a difference - the controller shouldn't know about this anyway). (2) The DPT controller on this has reported alternating wrong sense of the disk setup to the BIOS. This is obviously NOT a driver problem. As for your problems, I'm sorry to hear about them, but have no idea how to fix it. I've had none of the problems you have :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 02:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01146 for freebsd-scsi-outgoing; Fri, 29 May 1998 02:50:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01022; Fri, 29 May 1998 02:50:09 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 05:49:31 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> From: tcobb To: "'Eivind Eklund'" , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 05:49:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Eivind Eklund [mailto:eivind@yes.no] > Sent: Friday, May 29, 1998 5:43 AM > To: tcobb; 'freebsd-current@freebsd.org'; 'freebsd-scsi@freebsd.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > On Thu, May 28, 1998 at 10:49:23PM -0400, tcobb wrote: > > I believe that the DPT DRIVER is not correctly sensing that > the array is > > okay, even though it is in degraded mode, and incorrectly returns > > sector/MB values which panic the kernel. I don't recommend > depending on > > the proper operation of this driver for your > High-Availability needs. > > I have an older DPT, but I still want to add my experiences to the > above: > > (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded > mode. This has worked just fine with the driver in -current, with > the RAID full (of partitions, not data. I can't understand that > the amount of data should make a difference - the controller > shouldn't know about this anyway). Perhaps the difference is RAID-1 versus RAID-5. > (2) The DPT controller on this has reported alternating wrong sense of > the disk setup to the BIOS. This is obviously NOT a driver > problem. True. Interestingly enough, I've never had a problem with the wrong BIOS info from my DPT card. Only with the incorrect sensed info when using the DPT driver on a RAID-5 array when that array is in degraded mode. The fact that it panics trying to boot is amazing to me. It is NOT trying to boot from the RAID-5 by the way. > As for your problems, I'm sorry to hear about them, but have no idea > how to fix it. I've had none of the problems you have :-( Lucky for you, less so for me. ;) -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 03:27:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16567 for freebsd-scsi-outgoing; Fri, 29 May 1998 03:27:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16463; Fri, 29 May 1998 03:27:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA09157; Fri, 29 May 1998 10:27:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA25887; Fri, 29 May 1998 12:27:11 +0200 (MET DST) Message-ID: <19980529122551.16212@follo.net> Date: Fri, 29 May 1998 12:25:51 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net>; from tcobb on Fri, May 29, 1998 at 05:49:30AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 29, 1998 at 05:49:30AM -0400, tcobb wrote: > > (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded > > mode. This has worked just fine with the driver in -current, with > > the RAID full (of partitions, not data. I can't understand that > > the amount of data should make a difference - the controller > > shouldn't know about this anyway). > > Perhaps the difference is RAID-1 versus RAID-5. This might be so, or there might (I'm probably blaspheming by saying this) be a difference or bug in the handling of degradation from DPT to DPT. What is obvious is only that you're having problems with a particular controller/driver/kernel combination, and that a part of the driver has problems coping with failure somewhere else. I don't think it would be wise to consider the problem to be narrowed down more than that. Now, to be able to debug this as effectively as possible I suggest you/we try to create a list of test-cases that we believe would lock down the problem: Hypothesis 1: The problem occur when using your type of controller, RAID5+HotSpare, "large" amounts of capacity used, your kernel, and a disk fail. Verification: Create above setup, try to fail a disk on it. Now, which parameters to vary depend on whether we can get the above to crash. It might be dependent on having exactly equal disks, too :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 03:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18713 for freebsd-scsi-outgoing; Fri, 29 May 1998 03:32:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18656; Fri, 29 May 1998 03:32:07 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA09421; Fri, 29 May 1998 10:32:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA25905; Fri, 29 May 1998 12:31:49 +0200 (MET DST) Message-ID: <19980529123029.12289@follo.net> Date: Fri, 29 May 1998 12:30:29 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> <19980529122551.16212@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980529122551.16212@follo.net>; from Eivind Eklund on Fri, May 29, 1998 at 12:25:51PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 29, 1998 at 12:25:51PM +0200, Eivind Eklund wrote: > Hypothesis 1: The problem occur when using your type of controller, > RAID5+HotSpare, "large" amounts of capacity used, your kernel, and > a disk fail. > Verification: Create above setup, try to fail a disk on it. > > Now, which parameters to vary depend on whether we can get the above > to crash. It might be dependent on having exactly equal disks, too > :-( This was a pretty dumb way of saying this. What I meant was that forming further hypotheses/verifiction pairs in any effective manner seems pretty difficult without knowing the results of the above test. If you have more data, or more hypotheses/verification pairs, then come with 'em. If you want to be 100% certain of coming to a conclusion, this is usually the way to do it (but it can be expensive in terms of the number of tests you have to do). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 11:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29215 for freebsd-scsi-outgoing; Fri, 29 May 1998 11:13:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29185 for ; Fri, 29 May 1998 11:13:21 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 417 invoked by uid 1000); 29 May 1998 19:14:42 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> Date: Fri, 29 May 1998 15:14:42 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "simon@simon-shapiro.org" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 28-May-98 tcobb wrote: > I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD > CURRENT circa 5/18/98. I'm running the latest available firmware flash > for the card, all on a P5-233MMX with 128MB RAM. What version is ``latest''? I have several ``latest'' here. > Recently I lost a harddrive in my 24GB RAID5 array. The array was > configured with a HOT SPARE which should have allowed it to rebuild > completely online, with no interruption in service (except some minor > slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER > failed miserably. the DPT driver HAS NOTHING TO DO with the RAID array. It is seen strinctly as a disk. > When my array went into degraded mode, the DPT DRIVER froze access to > the partitions. Upon reboot, during device probe, the DPT DRIVER > returned a 1 SECTOR (0 MB) sense for the array, despite the fact that > the array was operating properly (though degraded). After this, the > kernel panic'd before completing the boot process with a "Page Fault in > Supervisor Mode" error, and continued to panic this way until the DPT > Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and > do it - doing the rebuild of that size RAID5 array takes more than an > hour). After a complete rebuild, the DPT DRIVER showed the array sizes > correctly. This is strange. I routinely (although rarely coluntarily) run into degraded mode. The size reported by the DPT driver, is the size rerported to the driver by the DPT firmware. If it shows as ZERO, it is either ZERO, or the array is more than degraded (dead). > During this process, booting into DOS revealed the array to be fine, > even while the array was degraded -- it also wasn't confused by degraded > mode and showed correct partition information. So, was it fine, or was it degraded? > I believe that the DPT DRIVER is not correctly sensing that the array is > okay, even though it is in degraded mode, and incorrectly returns > sector/MB values which panic the kernel. I don't recommend depending on > the proper operation of this driver for your High-Availability needs. I beg to differ. The DPT driver does not do any sensing at all. The SCSI layer calls for SENSE commands. The DPT driver is simply a protocol translator. I do not even look at the commands, nor their results/contents. Extending your recommendation, I'll repeat what was said here endlessly; Do NOT use 3.0-CURRENT for any mission critical software. Extending it further, do no use any computer software for mission critical under any conditions. All systems fail, except those with the power off. > HISTORY > I've used DPT in FreeBSD since last November, first with the hacked > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing > me about once per week. As 2.2.6, the MBUF leak disappeared and was > replaced with a once every 2-3 day panic which it appeared was not going > to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet > and upgraded recently to 3.0, which seemed to fix both of these prior > panics only to reveal that the supposedly "high availability" software > driver for my HA hardware is miserable during the most critical times. It may help, in the future, if you contact me for help. >From your description, you have a marginal disk subsystem. Either bad cabling, bad power, bad controller. None of your symptoms is relevant to the DPT driver. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 11:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00794 for freebsd-scsi-outgoing; Fri, 29 May 1998 11:19:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00777 for ; Fri, 29 May 1998 11:19:46 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id LAA25610; Fri, 29 May 1998 11:19:34 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Fri, 29 May 1998 11:19:33 -0700 (PDT) From: Chris Timmons To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Quantum Atlas II warning In-Reply-To: <199805140512.XAA13306@pluto.plutotech.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 Although I haven't yet seen the ugly failure syndrome (yet) that you alluded to, do you suppose that the later firmware will help with this sad situation? This is the repo disk for cvsup.freebsd.org: da2: Fixed Direct Access SCSI2 device da2: Serial Number PCB=2011300001 ; HDA=184704251342 da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 64H 32S/T 4341C) (da2:ahc1:0:4:0): tagged openings now 31 (da2:ahc1:0:4:0): tagged openings now 30 (da2:ahc1:0:4:0): tagged openings now 29 (da2:ahc1:0:4:0): tagged openings now 28 (da2:ahc1:0:4:0): tagged openings now 27 (da2:ahc1:0:4:0): tagged openings now 26 (da2:ahc1:0:4:0): tagged openings now 25 (da2:ahc1:0:4:0): tagged openings now 24 Our news server, now running 2.2.6-STABLE+CAM is noticeably revitalized - throughput increase with CAM was substantial as others running -current+CAM had reported. That system has all barracudas and hasn't had to dynamically lower the tagged openings at all. CAM really, really helps (but you knew that :) -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 11:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03315 for freebsd-scsi-outgoing; Fri, 29 May 1998 11:28:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03309 for ; Fri, 29 May 1998 11:28:50 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id MAA24115; Fri, 29 May 1998 12:28:02 -0600 (MDT) Message-Id: <199805291828.MAA24115@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Chris Timmons cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Quantum Atlas II warning In-reply-to: Your message of "Fri, 29 May 1998 11:19:33 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 12:23:55 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Although I haven't yet seen the ugly failure syndrome (yet) that you >alluded to, do you suppose that the later firmware will help with this sad >situation? This is the repo disk for cvsup.freebsd.org: > >da2: Fixed Direct Access SCSI2 device >da2: Serial Number PCB=2011300001 ; HDA=184704251342 >da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing >Enabled >da2: 4341MB (8890760 512 byte sectors: 64H 32S/T 4341C) >(da2:ahc1:0:4:0): tagged openings now 31 >(da2:ahc1:0:4:0): tagged openings now 30 >(da2:ahc1:0:4:0): tagged openings now 29 >(da2:ahc1:0:4:0): tagged openings now 28 >(da2:ahc1:0:4:0): tagged openings now 27 >(da2:ahc1:0:4:0): tagged openings now 26 >(da2:ahc1:0:4:0): tagged openings now 25 >(da2:ahc1:0:4:0): tagged openings now 24 I'm afraid that a firmware upgrade will not address this problem. You can artificially force the tag counts higher for the drive, but the, somewhat arbitrary count of 24, was chosen so that QUEUE FULLs don't occur "all the time" during write operations. The cache on the Atlas II fills really easily, so the tag count tends to drop, but we don't allow it to fall below 24 so that read operations still benefit from tagged queuing. >Our news server, now running 2.2.6-STABLE+CAM is noticeably revitalized - >throughput increase with CAM was substantial as others running >-current+CAM had reported. That system has all barracudas and hasn't had >to dynamically lower the tagged openings at all. If you really pound the disks, it should drop to 63, but no lower. The Barracudas have a built in limit of 63 transactions. >CAM really, really helps (but you knew that :) 8-) >-Chris -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 12:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15485 for freebsd-scsi-outgoing; Fri, 29 May 1998 12:15:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA15420 for ; Fri, 29 May 1998 12:14:57 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1256 invoked by uid 1000); 29 May 1998 20:16:18 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> Date: Fri, 29 May 1998 16:16:18 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" , Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-May-98 tcobb wrote: ... > My problem report (most of which you snipped) pointed out a deficiency > in the DPT driver code which renders it useless in HA applications. I > believe that this deficiency is likely to be present in ALL VERSIONS of > this code, unless suddenly, people are putting the newest code in the > oldest versions of the OS. We all trust that you use FreeBSD 3.0-current and a DPT controller in said system. What you have failed to demonstrate is that the FreeBSD DRIVER is at fault. I am very anxious to discover and repair ANY bug in this driver as many people use this setup for mission critical work. Since I read the driver code few times and am somewhat familiar with it, I cannot find support to your claim that the failure you report (and we trust there is a failure) is induced in the driver. I am very interested in helping you solve your problem, but going into the driver and tearing up the code, searching for unknown and unlikely breakage is not an efficient use of my time and will most likely not advance our common goal of getting your system up and running and the problem eradicated. As you can observe elsewhere, a FreeBSD SCSI HBA driver in general (and the DPT driver in particular) is not involving itself with the contents of the SCSI commands passed to it from the kernel. Nor does it concern itself with the results of these commands. In the FreeBSD driver, similar to other DPT drivers (but not identical), I perfrom certain checks with the DPT hardware. These happen at boot time, BEFORE any of the kernel boot prompts you see. None of these has anything to do with what devices are attached to the bus, but strictly with the controller; Who are you? How are you doing?, etc. But never anything to do with attached devices. Reporting an array size zero (or one) is most likely caused by the array being DEAD, not degraded. Have you run the dptmgr verify function against the entire array? DOS does not perform much analysis and can be misleading. Unless you explicitly instruct the DPTMGR software to access data on a disk (or array), only the first sector is being accessed. Thus, it is entirely possible that the array is inaccessible beyond one sector, if that. Your symptoms can be caused by many causes, all of them within the realm of DPT hardware and attached devices. I really do not know the purpose of your messages on this subject. You really have not asked for help fixing the problem. Neither did you offer any diagnistics data to me, or the group as a whole. If your purpose is to create an acusation, it is well written, with the minor flow of it being inaccurate and quite wrong in its conclusion. If your purpose is to solve the problem, please send me the following (with a copy to the group, if you care) a. Exact Configuration; What CPU, what memory, DPT card model, type of cache memory, amount of cache, exact firmware version, exact BIOS version (NOT the same thing!) What disks are in which array, etc. I'll also need to know how the disks are programmed into the array, their bus and target IDs, etc. I need this information from both the hardware configuration and the logical view screens. b. Exact Setup; These disks, what brand and model? What firmware version on each disk? How are these disks mounted and in what? The type of cables you use, the type of terminators you use, etc. c. Is the system bootable now? Is it on the net? Can I have a root login on it for a while? d. Are you going to be available to run dptmgr for me and be my eyes and fingers, while in DOS or SU mode? e. Have you run all the DPT diagnostics to assure that the arrays are really healthy and accessible? Have you wiggled the wires to every device, while the tests are running? Have you printed out the DPT error log for the controller (from DPTMGR)? Have you run the statistics, to see the error counts and rates? Please provide me with this data, so I can try and help you. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 12:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20267 for freebsd-scsi-outgoing; Fri, 29 May 1998 12:40:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20224; Fri, 29 May 1998 12:40:15 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id PAA03125; Fri, 29 May 1998 15:40:12 -0400 (EDT) Date: Fri, 29 May 1998 15:40:12 -0400 (EDT) From: The Hermit Hacker To: freebsd-scsi@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: May20th CAM drivers with today's (May29th) sources ... 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'm having a panic problems on my server, and want to upgrade, but am using CAM...does anyone know of any problems with using May20th drivers with May29th sources? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 12:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23450 for freebsd-scsi-outgoing; Fri, 29 May 1998 12:51:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA23379 for ; Fri, 29 May 1998 12:51:29 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1584 invoked by uid 1000); 29 May 1998 20:52:49 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> Date: Fri, 29 May 1998 16:52:49 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" , Eivind Eklund Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-May-98 tcobb wrote: >> (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded >> mode. This has worked just fine with the driver in -current, with >> the RAID full (of partitions, not data. I can't understand that >> the amount of data should make a difference - the controller >> shouldn't know about this anyway). > > Perhaps the difference is RAID-1 versus RAID-5. What has that got to do with the over-hacked driver, again? Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 17:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11207 for freebsd-scsi-outgoing; Fri, 29 May 1998 17:35:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11178 for ; Fri, 29 May 1998 17:35:32 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id SAA02271; Fri, 29 May 1998 18:31:14 -0600 (MDT) Date: Fri, 29 May 1998 18:31:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805300031.SAA02271@narnia.plutotech.com> To: "Jose M. Alcaide" cc: scsi@FreeBSD.ORG Subject: Re: AHC: "cheksum error" reading SEEPROM with Iwill PIILS mb Newsgroups: pluto.freebsd.scsi In-Reply-To: <356D9CF8.1E7667F5@we.lc.ehu.es> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <356D9CF8.1E7667F5@we.lc.ehu.es> you wrote: > Hello, > > I have just purchased a new system for running FreeBSD. It is > based on the Iwill PIILS motherboard, which uses the 440LX > chipset and includes an Adaptec 7880 SCSI controller. > I'm running FreeBSD-stable now, but I have found a problem > related to SCSI: > > When the AHC driver tries to read the 7880's SEEPROM, the operation > fails with a "cheksum error". This is because your system does not have a serial eeprom attached the the aic7880. The only way the driver can determine this is by attempting to read it and to perform a checksum comparison. If a serial eeprom is not found, the driver is smart enough to pull the "left over BIOS settings" off the chip and use them. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 29 20:01:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02413 for freebsd-scsi-outgoing; Fri, 29 May 1998 20:01:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02405; Fri, 29 May 1998 20:01:34 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA05097; Fri, 29 May 1998 22:00:59 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805300300.WAA05097@dyson.iquest.net> Subject: Re: DPT install problem In-Reply-To: <199805261847.LAA00549@dingo.cdrom.com> from Mike Smith at "May 26, 98 11:47:18 am" To: mike@smith.net.au (Mike Smith) Date: Fri, 29 May 1998 22:00:59 -0500 (EST) Cc: toor@dyson.iquest.net, shimon@simon-shapiro.org, mike@smith.net.au, tom@sdf.com, freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 > > > > > > On 22-May-98 Mike Smith wrote: > > > >> > > > >> > However, there are a couple of things that you personally (and other > > > >> > concerned users) can do to help the situation. > > > >> > > > > >> > - Contribute commentary (as you have), documentation and source/ > > > >> > procedural fixes. Remeber that FreeBSD is a volunteer project - > > > >> > your support means that it will continue to improve. > > > >> > - Donate a DPT controller to our testing pool so that we can test > > > >> > with it. Chances are we can scrape enough disks together in one > > > >> > place to meet the 20GB mark if we have one. > > > >> > > > >> I recently donated TWO DPT controllers and FIVE disk drives. They went > > > >> to > > > >> two separate FreeBSD prominent figures, but still do not add up to 20GB. > > > > > > > > Then we need some accountability from these prominent figures. Where > > > > is their feedback on this discussion? > > > > > Do you want working kernel threads and SMP or DPT support? I am working > > feverishly on the SMP and kernel threads stuff, and physically cannot do > > any more in the day. > > I just want to know what these people are doing if not answering > questions. Guessing and begging users for input is traditional stuff, > but if there's a better alternative, I'm all for it. > > > I do plan to work on the DPT stuff, but I can only do one type of thing > > at a time... > > Sounds reasonable to me. What we need are some underlings for you to > boss around doing your grunt work. JD and the moonshine gang? > I have worked in mgmt before, I make a much better 'grunt'. :-). Also, if we can find someone who can do things more quickly or efficiently, and Simon agrees, I am willing to ship the equipment to someone else. I consider the equipment as a project resource donated by Simon, and am willing to do what I can do to make things move more quickly as needed and agreed by everyone concerned!!! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 00:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06315 for freebsd-scsi-outgoing; Sat, 30 May 1998 00:10:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05973; Sat, 30 May 1998 00:09:02 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sat, 30 May 1998 03:08:26 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAE8@freya.circle.net> From: tcobb To: "'shimon@simon-shapiro.org'" Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: DPT Redux Date: Sat, 30 May 1998 03:08:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I won't respond to each of Simon's many emails over the past 24 hours, simply because most of them were out-of-context reactions to a thread that grew from my original DPT post yesterday. Instead, I think that the most productive thing is to provide a bit more of the information requested. The system is using a single PM3334UW/2 with drives configured in the following logical arrays: 2 1GB drives as RAID-1 (sd0) 7 4GB drives as RAID-5 (sd1) 1 4GB hot swap Event #1: 1 of the RAID-5 drives fails, DPT hardware begins to auto-rebuild with the hot swap drive DPT driver freezes access to sd1, system remains running but access to sd1 hangs I shutdown and rebooted machine (SYNC failed on shutdown) Allowed FreeBSD to boot, it returned the following for sd1 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 0MB (1 512 byte sectors) Then, system continued booting and finally panic'd with a "Page Fault in Supervisor Mode" error prior to mounting drives. I then booted the system with a DOS floppy, used DPTmgr to examine array. The array was complete, but in degraded mode. It had begun rebuilding itself, which specs say can happen in the background while other accesses are going on. I tested redundancy info on the array AND tested random reads on the array -- all succeeded. So, I exited DPTmgr, and tried booting back to FreeBSD, same problem as above occurred (0MB 1 sector, panic). Then, I rebooted into DOS and let the DPT card run its rebuild from there. It completed about 1.5 hours later, and showed the array optimal. I then rebooted into FreeBSD which showed the correct info again. Event #2: This was the next day. Hard drive fails in array (this was the ex-hot swap from above). This leaves the array with no hotswap to insert, but no data lost. The array is now again in degraded mode. The card screams bloody murder. HOWEVER, the DPT driver does NOT hang on access to the sd1 partition. I successfully shutdown the machine (SYNC succeeded this time). I insert a new harddrive into the array so that the DPT hardware will begin rebuilding with this new drive. On reboot, FreeBSD showed the same results as above (0MB, 1 sector, panic). Rebooting back to DOS and running DPTmgr showed that the array was in degraded mode, but that no data was lost and that redundancy information was all there. It automatically began rebuilding with the new drive. I tested rebooting into FreeBSD, same results (0/1/panic). Rebooted back to DOS, allowed the hardware to finish its rebuild (1.5 hours), rebooted to FreeBSD and it showed the correct results. So, here's the summary for those of you who've stayed with me. With RAID-5 and a HOT SWAP drive, a single drive failure caused the DPT driver in FreeBSD to hang on access to the partition. This appears to be because DPT was doing a background rebuild automatically. With RAID-5 and NO hot swap drive, a single drive failure does NOT cause the DPT driver in FreeBSD to hang on access to the partition. This appears to be because DPT was NOT doing a background rebuild -- there being no drives to rebuild into. With RAID-5 and a new drive to rebuild on, the DPT hardware begins automatic rebuilds of the array. However, in these conditions the DPT driver (or other FreeBSD component) does not correctly sense the size information and panics the kernel during bootup. This symptom goes away after the rebuild is complete. This symptom does not appear when in DOS under the same circumstances. DOS DPTmgr checks show the array of the correct size. BIOS bootup screen for DPT shows the array of the correct size. The super-summary is that it appears the the DPT driver or other FreeBSD code component is not correctly coordinating with the DPT hardware (or sensing status properly) when the DPT hardware is doing a background rebuild of the array. This array has been running non-stop since November 1997. Cabling is good. Active terminators and custom cables created by Granite are used. Seagate and Micropolis drives are used. The RAID-5 array is in an external rackmount case. -Troy Cobb Circle Net, Inc. http://www.circle.net Here's the dmesg ouput, trimmed to show relevant data. FreeBSD 3.0-CURRENT #0: Sun May 24 04:30:04 EDT 1998 root@kali.circle.net:/usr/src/sys/compile/BENZAITEN-4 CPU: Pentium (232.67-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 128147456 (125144K bytes) DEVFS: ready for devices DPT: RAID Manager driver, Version 1.0.5 Probing for devices on PCI bus 0: DPT: PCI SCSI HBA Driver, version 1.4.2 chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 dpt0: rev 0x02 int a irq 9 on pci0.20.0 dpt0: DPT type 3, model PM3334UW firmware 07M0, Protocol 0 on port 6310 with Write-Back cache. LED = 0000 0000 dpt0: Enabled Options: Recover Lost Interrupts Collect Metrics Optimize CPU Cache dpt0: waiting for scsi devices to settle scbus0 at dpt0 bus 0 dpt0: Initializing Lost IRQ Timer sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1029MB (2109328 512 byte sectors) dpt0: waiting for scsi devices to settle scbus1 at dpt0 bus 1 sd1 at scbus1 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 20503MB (41990720 512 byte sectors) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 00:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07547 for freebsd-scsi-outgoing; Sat, 30 May 1998 00:17:49 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07498; Sat, 30 May 1998 00:16:23 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sat, 30 May 1998 03:15:46 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAE9@freya.circle.net> From: tcobb To: "'shimon@simon-shapiro.org'" , "'freebsd-scsi@freebsd.org'" Cc: "freebsd-current@freebsd.org" , Karl Pielorz Subject: RE: DPT driver fails and panics with Degraded Array Date: Sat, 30 May 1998 03:15:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Simon Shapiro [mailto:shimon@simon-shapiro.org] [SNIP] > At this point, the load on > the system will > reach 140-400 (we run the tests against RAID-0 and RAID-1, the > performance differs) >From my quick review of the replies of FreeBSD DPT RAID users, all of them appear to be using their arrays in RAID-0 or RAID-1 configurations. According to Simon's test procedure for his releases (portion copied above), he too only uses the DPT RAID-0 and RAID-1 features. In my setup, I'm using both RAID-5 and RAID-1. I have yet to have a drive failure on the RAID-1 array (*knock on wood*), the problems I saw were with the RAID-5 array and rebuilds. *PERHAPS* the key point is that the driver developer hasn't tested the FreeBSD DPT driver with a RAID-5 array. Perhaps not. What is clear from my prior post (the really long one) is that in my configuration the DPT driver or some other FreeBSD software component does not correctly deal with the DPT hardware doing a background rebuild. I'm going to try to obtain another DPT card and setup another small array for further testing. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 03:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25281 for freebsd-scsi-outgoing; Sat, 30 May 1998 03:28:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ninbox.ml.org ([207.242.81.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25276 for ; Sat, 30 May 1998 03:28:36 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.8.7/8.8.5) with ESMTP id FAA00706 for ; Sat, 30 May 1998 05:28:32 -0500 (CDT) Message-ID: <356FDF50.761A180C@airnet.net> Date: Sat, 30 May 1998 05:28:32 -0500 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: NCR 53C406 Support? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any support in the works, existing, or planned for the 53C406? I have one on a PAS-Clone that used ASPI+CAM under DOS. I would be more than happy to test, but I am not -current or -stable (yet). -- Kris Kirby --------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 07:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18828 for freebsd-scsi-outgoing; Sat, 30 May 1998 07:52:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA18807 for ; Sat, 30 May 1998 07:52:45 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id QAA15123; Sat, 30 May 1998 16:52:26 +0200 Message-ID: <35701D2A.8851BC80@we.lc.ehu.es> Date: Sat, 30 May 1998 16:52:26 +0200 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: scsi@FreeBSD.ORG Subject: Re: AHC: "cheksum error" reading SEEPROM with Iwill PIILS mb References: <199805300031.SAA02271@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > > > When the AHC driver tries to read the 7880's SEEPROM, the operation > > fails with a "cheksum error". > > This is because your system does not have a serial eeprom attached > the the aic7880. The only way the driver can determine this is > by attempting to read it and to perform a checksum comparison. If > a serial eeprom is not found, the driver is smart enough to pull the > "left over BIOS settings" off the chip and use them. > Please accept my apologies for my ignorance about this question. I have other two systems (Dell Poweredges) with embedded 7880 controllers and the SEEPROM is read without problems on them. I saw that "checksum error" for the first time when I installed FreeBSD on the new Iwill-based system. I was convinced that the SEEPROM was included in the 7880 chip. What's the utility of the SEEPROM? If my Iwill PIILS mb has no SEEPROM, could this affect to the behavior of the AHC driver and consequently to the overall performance of SCSI? Thanks, -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 18:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10864 for freebsd-scsi-outgoing; Sat, 30 May 1998 18:44:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10858 for ; Sat, 30 May 1998 18:44:17 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id VAA25694; Sat, 30 May 1998 21:44:02 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: "Jose M. Alcaide" cc: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: AHC: "cheksum error" reading SEEPROM with Iwill PIILS mb In-reply-to: Your message of "Thu, 28 May 1998 19:20:56 +0200." <356D9CF8.1E7667F5@we.lc.ehu.es> Date: Sat, 30 May 1998 21:44:02 -0400 Message-ID: <25690.896579042@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jose M. Alcaide" wrote in message ID <356D9CF8.1E7667F5@we.lc.ehu.es>: > When the AHC driver tries to read the 7880's SEEPROM, the operation > fails with a "cheksum error". I'm afraid that the 7880 chip on my > PIILS motherboard is different (perhaps another version?): for > example, I cannot choose the termination type using the Adaptec > SCSI BIOS ("High ON/Low ON", "High ON/Low Off"...); instead, I can > only select "Enable" or "Disable". However, the "cheksum error" > trying to read the 7880's SEEPROM does not prevent the AHC driver > from working properly. Until now, I can use both the SCSI disk and > CD-ROM without any problem. The SEEPROM (Serial EEPROM) is something that Adaptec PCI cards use to store their configuration on. However, on-board controllers don't have an SEEPROM as they normally have the settings in the BIOS. Hence, the SEEPROM checksum fails because there isn't one :) The AHC driver has sensible enough defaults that it should Just Work (TM) when an SEEPROM is not found. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 30 21:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27261 for freebsd-scsi-outgoing; Sat, 30 May 1998 21:14:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27246; Sat, 30 May 1998 21:14:16 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA09016; Sat, 30 May 1998 20:09:41 -0700 (PDT) Message-Id: <199805310309.UAA09016@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: DPT Redux In-reply-to: Your message of "Sat, 30 May 1998 03:08:21 EDT." <509A2986E5C5D111B7DD0060082F32A402FAE8@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 20:09:41 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I shutdown and rebooted machine (SYNC failed on shutdown) > Allowed FreeBSD to boot, it returned the following for sd1 > sd1: type 0 fixed SCSI 2 > sd1: Direct-Access 0MB (1 512 byte sectors) > > Then, system continued booting and finally panic'd with a "Page Fault in > Supervisor Mode" error prior to mounting drives. Did you happen to write down the details from this message? In conjunction with your kernel image, these are required in order to determine what happened. It's possible that something doesn't like being asked to boot from a zero-sized disk. It's also possible that something else later got upset - it's not clear where in the chain of events the panic occurred (see above). Thanks for the extra info. Are you able to simulate the failure by eg. disconnecting one of the 'active' drives? If you can't do this on a regular basis, I believe we are able to arrange temporary access to a similar but idle system where this can be simulate. Simon may also be able to offer some suggestions inre. possible poor interaction between the dpt driver and some firmware revisions. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat May 30 21:26:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28802 for freebsd-scsi-outgoing; Sat, 30 May 1998 21:26:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28793; Sat, 30 May 1998 21:26:51 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sun, 31 May 1998 00:26:12 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAF6@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: RE: DPT Redux Date: Sun, 31 May 1998 00:26:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > > I shutdown and rebooted machine (SYNC failed on shutdown) > > Allowed FreeBSD to boot, it returned the following for sd1 > > sd1: type 0 fixed SCSI 2 > > sd1: Direct-Access 0MB (1 512 byte sectors) > > > > Then, system continued booting and finally panic'd with a > "Page Fault in > > Supervisor Mode" error prior to mounting drives. > > Did you happen to write down the details from this message? In > conjunction with your kernel image, these are required in order to > determine what happened. This is the one thing I neglected to do, unfortunately - I just got the error name, not the rest of the info. The situation was a surprise and had become an emergency at the point it was clear that FreeBSD wasn't going to reboot. The kernel file I can certainly supply. > It's possible that something doesn't like being asked to boot from a > zero-sized disk. It's also possible that something else later got > upset - it's not clear where in the chain of events the panic > occurred > (see above). Actually, it wasn't booting from the "zero-sized" disk. From my earlier email, I noted that I have two arrays configured, the first sd0, is the boot disk and RAID-1 and contains all relevant system directories, the second sd1, is simply an NFS export partition and is RAID-5. It was the second disk (sd1) which showed the "0 MB/1 sector" problem. > Thanks for the extra info. Are you able to simulate the > failure by eg. > disconnecting one of the 'active' drives? If you can't do this on a > regular basis, I believe we are able to arrange temporary access to a > similar but idle system where this can be simulate. Simon > may also be > able to offer some suggestions inre. possible poor > interaction between > the dpt driver and some firmware revisions. I'm hoping to be able to create a duplicate array to this one for testing, also. I'm getting resistance to budgeting additional funds for DPT/FreeBSD at the moment :( The machine in question is currently (and still) a live NFS server. I'm working on scheduling some downtime for it in the next few days get a hotswap drive back in there. I expect that I'll have to keep it down (1.5hrs) for a complete array rebuild on the RAID-5 given the interactions I've seen recently. My instinct is that, assuming someone could setup a RAID-5 array with HOT SWAP disk, and then yanked a live drive, that they'd see the same symptoms that I did. Or, even simpler would be to tell the array to rebuild, then try to boot FreeBSD... -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message