From owner-freebsd-scsi Sun May 17 00:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17497 for freebsd-scsi-outgoing; Sun, 17 May 1998 00:27:47 -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 AAA17492 for ; Sun, 17 May 1998 00:27:45 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id BAA01716; Sun, 17 May 1998 01:23:30 -0600 (MDT) Date: Sun, 17 May 1998 01:23:30 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805170723.BAA01716@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: Atrocious transfer rates... Newsgroups: pluto.freebsd.scsi In-Reply-To: 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 you wrote: > On Fri, 15 May 1998, Chris Timmons wrote: > > Well, got hit by a system hang again tonight :( Running a > 0514/15 kernel, with the latest CAM snapshot... BTW, are you positive the hangs are SCSI related? Do you have any serial console messages to help us debug this problem? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 00:58:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19761 for freebsd-scsi-outgoing; Sun, 17 May 1998 00:58:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19755; Sun, 17 May 1998 00:58:11 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (root@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id JAA01364; Sun, 17 May 1998 09:58:12 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id JAA00278; Sun, 17 May 1998 09:58:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199805170758.JAA00278@greenpeace.grondar.za> To: gibbs@FreeBSD.ORG cc: scsi@FreeBSD.ORG Subject: CAM broken with SMP/current/AHC Date: Sun, 17 May 1998 09:58:02 +0200 From: Mark Murray Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I added the latest CAM snapshot diffs to my current tree and I get the following panic on boot: SMP: AP CPU#1 Launched! panic: ahc_intr: AWAITING_MSG for an SCB that does not have a waiting message mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 boot() called on CPU#0 syncing disks... done Automatic reboot in 15 seconds - press any key on the console to abort Any ideas? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 09:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06792 for freebsd-scsi-outgoing; Sun, 17 May 1998 09:23:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (tc-19.acadiau.ca [131.162.2.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06783 for ; Sun, 17 May 1998 09:23:09 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id NAA03647; Sun, 17 May 1998 13:23:09 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 17 May 1998 13:23:09 -0300 (ADT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Atrocious transfer rates... In-Reply-To: <199805170723.BAA01716@narnia.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 On Sun, 17 May 1998, Justin T. Gibbs wrote: > In article you wrote: > > On Fri, 15 May 1998, Chris Timmons wrote: > > > > Well, got hit by a system hang again tonight :( Running a > > 0514/15 kernel, with the latest CAM snapshot... > > BTW, are you positive the hangs are SCSI related? Do you have any > serial console messages to help us debug this problem? Nothing, it just goes dead...:( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 09:32:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07686 for freebsd-scsi-outgoing; Sun, 17 May 1998 09:32:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (tc-19.acadiau.ca [131.162.2.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07681 for ; Sun, 17 May 1998 09:32:55 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id NAA03728; Sun, 17 May 1998 13:32:58 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 17 May 1998 13:32:58 -0300 (ADT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Atrocious transfer rates... In-Reply-To: <199805170652.AAA01616@narnia.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 On Sun, 17 May 1998, Justin T. Gibbs wrote: > Upgrade your firmware already... If I had access to the box, this would be an easy solution, but I'm 2500km away from it :( Is there a way, in Unix, of performing this upgrade? I have a serial console configured on this box...no video card, no keyboard...if I can do it from Unix, then I can do it from here...if not, then I have to get them up there to fight with it :( As for the firmware upgrade itself...where do I get it from? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 09:41:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08786 for freebsd-scsi-outgoing; Sun, 17 May 1998 09:41:33 -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 JAA08751; Sun, 17 May 1998 09:41:23 -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 KAA29693; Sun, 17 May 1998 10:41:14 -0600 (MDT) Message-Id: <199805171641.KAA29693@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Mark Murray cc: gibbs@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: CAM broken with SMP/current/AHC In-reply-to: Your message of "Sun, 17 May 1998 09:58:02 +0200." <199805170758.JAA00278@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 May 1998 10:37:02 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi > >I added the latest CAM snapshot diffs to my current tree and I >get the following panic on boot: > >SMP: AP CPU#1 Launched! >panic: ahc_intr: AWAITING_MSG for an SCB that does not have a waiting message >mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 >boot() called on CPU#0 > >syncing disks... done >Automatic reboot in 15 seconds - press any key on the console to abort > >Any ideas? I started hunting around for where the system launches the other CPUs, but I haven't found it yet. My guess is that just at the point of startup, these CPUs are vulnerable to receiving interrupts at the same time as CPU 0. I've done some analysis with Russell Cattelan on this, and the only way I can see for this error to occur is if one of the interrupt driver lists is corrupted by unexpected interrupt re-entrance. Why wouldn't this affect the old SCSI code? CAM continues with the boot process while still configuring the devices on the bus, but after registering the presence of the devices to the system. This allows the boot to block only during the configuration of the devices it cares about (like your root disk). But, this does open the window for I/O to occur while extra CPUs are started. >M >-- >Mark Murray >Join the anti-SPAM movement: http://www.cauce.org -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 09:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09252 for freebsd-scsi-outgoing; Sun, 17 May 1998 09:45:41 -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 JAA09247 for ; Sun, 17 May 1998 09:45:39 -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 KAA29849; Sun, 17 May 1998 10:45:40 -0600 (MDT) Message-Id: <199805171645.KAA29849@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: The Hermit Hacker cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Atrocious transfer rates... In-reply-to: Your message of "Sun, 17 May 1998 13:32:58 -0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 May 1998 10:41:28 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Sun, 17 May 1998, Justin T. Gibbs wrote: > >> Upgrade your firmware already... > > If I had access to the box, this would be an easy solution, but >I'm 2500km away from it :( Is there a way, in Unix, of performing this >upgrade? I have a serial console configured on this box...no video card, >no keyboard...if I can do it from Unix, then I can do it from here...if >not, then I have to get them up there to fight with it :( You could attempt to write a utility that uses the "write buffer" SCSI command to load the firmware. Unfortunately most vendors set some vendor specific bits in the command or require a certain pattern of commands for the firmware to stick. Your best bet is to boot a DOS floppy with the ASPI drivers for the adaptec, and the firmware stuff on it. > As for the firmware upgrade itself...where do I get it from? ftp://ftp.quantum.com/Firmware/AtlasI/L915 Or something like that. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 09:58:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10506 for freebsd-scsi-outgoing; Sun, 17 May 1998 09:58:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10488; Sun, 17 May 1998 09:58:05 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (root@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id SAA16622; Sun, 17 May 1998 18:58:00 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id SAA03015; Sun, 17 May 1998 18:57:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199805171657.SAA03015@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: gibbs@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: CAM broken with SMP/current/AHC Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 May 1998 18:57:57 +0200 From: Mark Murray Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" wrote: > I started hunting around for where the system launches the other CPUs, but > I haven't found it yet. My guess is that just at the point of startup, sys/i386/i386/mp_machdep.c > these CPUs are vulnerable to receiving interrupts at the same time as CPU > 0. I've done some analysis with Russell Cattelan on this, and the only > way I can see for this error to occur is if one of the interrupt driver > lists is corrupted by unexpected interrupt re-entrance. Sounds reasonable. Unfortunately I know very little about the kernel. I'll play.. > Why wouldn't this affect the old SCSI code? CAM continues with the boot > process while still configuring the devices on the bus, but after > registering the presence of the devices to the system. This allows the > boot to block only during the configuration of the devices it cares about > (like your root disk). But, this does open the window for I/O to occur > while extra CPUs are started. Could slpx() and friends be the answer? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 17 10:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10758 for freebsd-scsi-outgoing; Sun, 17 May 1998 10:00:32 -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 KAA10750; Sun, 17 May 1998 10:00:28 -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 LAA00511; Sun, 17 May 1998 11:00:22 -0600 (MDT) Message-Id: <199805171700.LAA00511@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Mark Murray cc: "Justin T. Gibbs" , gibbs@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: CAM broken with SMP/current/AHC In-reply-to: Your message of "Sun, 17 May 1998 18:57:57 +0200." <199805171657.SAA03015@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 May 1998 10:56:10 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Could slpx() and friends be the answer? It would fail on UP as well as fail on the last snapshot if the problem was missing spl protection in the adaptec driver. Little has changed in the adaptec code since 0413, so my guess is that an SMP change in the last month has caused this problem. >M >-- >Mark Murray >Join the anti-SPAM movement: http://www.cauce.org -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 01:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06783 for freebsd-scsi-outgoing; Mon, 18 May 1998 01:42:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06631; Mon, 18 May 1998 01:41:56 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (root@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id KAA14954; Mon, 18 May 1998 10:41:55 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id KAA00316; Mon, 18 May 1998 10:41:49 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199805180841.KAA00316@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 to: gibbs@FreeBSD.ORG, tegge@freeebsd.org cc: scsi@FreeBSD.ORG Subject: Followup: Re: CAM broken with SMP/current/AHC Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 May 1998 10:41:49 +0200 From: Mark Murray Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark Murray wrote: > Hi > > I added the latest CAM snapshot diffs to my current tree and I > get the following panic on boot: > > SMP: AP CPU#1 Launched! > panic: ahc_intr: AWAITING_MSG for an SCB that does not have a waiting message > mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 > boot() called on CPU#0 > > syncing disks... done > Automatic reboot in 15 seconds - press any key on the console to abort I cvsupped up to the stage where Tor's SMP interrupt handling code was in the kernel and rebuilt. Same panic, but with different numbers: SMP: AP CPU#1 Launched! panic: ahc_intr: AWAITING_MSG for an SCB that does not have a waiting message mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 boot() called on CPU#1 syncing disks... done Automatic reboot in 15 seconds - press any key on the console to abort M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 07:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22727 for freebsd-scsi-outgoing; Mon, 18 May 1998 07:56:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22715 for ; Mon, 18 May 1998 07:56:05 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by keg.cs.vu.nl with smtp (Smail3.1.28.1 #48) id m0ybRKd-00078iC; Mon, 18 May 98 16:56 +0200 Date: Mon, 18 May 1998 16:56:03 +0200 (MET DST) From: Guido Kollerie Reply-To: Guido Kollerie To: freebsd-scsi@FreeBSD.ORG Subject: CAM/stable/BT-958 questions 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 have installed the CAM-980513-stable patch (file date: 15th May) on a 2.2-stable system (CTM delta 718). It seems to be running just fine, nevertheless I have a few questions: 1. The README said: "You will also likely want a "pass0" device. Look in DM, LINT or GENERIC for examples." However pass0 is not mentioned anywhere in LINT or GENERIC. I am not sure what DM is. Is pass0 a Current feature not applicable to Stable? 2. What's going on here? bt0: bt_cmd: Timeout waiting for adapter ready, status = 0x0 bt0: btfetchtransinfo - Inquire Setup Info Failed 3. Why is the Fujitsu harddrive (da0) listed as having "10MB/s tranfers"? It's a fast-wide scsi device. Hence I expected 20MB/s tranfers. Oh and Justin, thank you for having written a driver which fully utilizes the BT-958! I will do some performance tests (make buildworld) to see how much difference Command Tagged Queueing makes. If you want me to do some additional tests, please let me know! -- Guido Kollerie Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Mon May 18 15:24:07 CEST 1998 root@myname.my.domain:/usr/src/sys/compile/KINCHENNA Calibrating clock(s) ... i586 clock: 132941621 Hz, i8254 clock: 1193067 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x001d9000 - 0x01ffdfff, 31608832 bytes (7717 pages) avail memory = 31006720 (30280K bytes) pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x8000005c pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=12508086) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 2 on pci0:0:0 chip1 rev 1 on pci0:7:0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ15, D: IRQ11 MB0: , MB1: chip2 rev 0 on pci0:7:1 mapreg[20] type=1 addr=0000f000 size=0010. Primary IDE: disabled Secondary IDE: disabled vga0 rev 1 int a irq 11 on pci0:17:0 mapreg[10] type=0 addr=e0800000 size=4000. mapreg[14] type=0 addr=e0000000 size=800000. reg16: ioaddr=0x6100 size=0x4 bt0 rev 8 int a irq 15 on pci0:18:0 mapreg[10] type=1 addr=00006100 size=0004. mapreg[14] type=0 addr=e0804000 size=1000. reg16: ioaddr=0x6100 size=0x4 bt0: BT-958 FW Rev. 5.06I Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs bt0: Using Strict Round Robin Mailbox Mode pci0: uses 8409088 bytes of memory from e0000000 upto e0804fff. pci0: uses 20 bytes of I/O space from 6100 upto f00f. Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: video mode:24 sc0: VGA registers in BIOS for mode:24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: VGA registers to be used for mode:24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in bt: unit number (1) too high bt1 not found at 0x330 npx0 flags 0x1 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 7 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa imasks: bio c0080040, tty c003009a, net c0060000 BIOS Geometries: 0:0123fe3f 0..291=292 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround bt0: Using Strict Round Robin Mailbox Mode bt0: bt_cmd: Timeout waiting for adapter ready, status = 0x0 bt0: btfetchtransinfo - Inquire Setup Info Failed Considering FFS root f/s. da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number 50000631 da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2291MB (4693462 512 byte sectors: 255H 63S/T 292C) (da1:bt0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:bt0:0:4:0): NOT READY asc:3a,0 (da1:bt0:0:4:0): Medium not present da1 at bt0 bus 0 target 4 lun 0 da1: Removable Direct Access SCSI2 device da1: 3.300MB/s transfers da1: Attempt to query device size, failed cd0 at bt0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0s1: type 0xa5, start 63, end = 4498199, size 4498137 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 08:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24752 for freebsd-scsi-outgoing; Mon, 18 May 1998 08:08:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from colossus.dyn.ml.org (206-18-113-198.la.inreach.net [206.18.113.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24727; Mon, 18 May 1998 08:08:37 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id IAA07793; Mon, 18 May 1998 08:06:39 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.2.p0.FreeBSD:980518080638:206=_" In-Reply-To: Date: Mon, 18 May 1998 08:06:38 -0700 (PDT) Organization: Computer Help From: Donald Burr To: The Hermit Hacker , FreeBSD SCSI Subject: RE: Bad shutdown... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format --_=XFMail.1.2.p0.FreeBSD:980518080638:206=_ Content-Type: text/plain; charset=us-ascii -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 16-May-98, The Hermit Hacker wrote: > This is based on a 0515 kernel, with the CAM snapshot applied to it... > > hub# halt > > syncing disks... 3 3 done > panic: lockmgr: pid 318, not exclusive lock holder 1 unlocking > > dumping to dev 20401, offset 262144 > dump Aborting dump due to I/O error. status == 0x200, scsi status == 0x0 > i/o error > Automatic reboot in 15 seconds - press a key on the console to abort Just FYI, I'm seeing the exact same thing, except I don't use CAM. This is on a P133 with a kernel cvsupped and compiled around may 12. Attached are outputs of 'dmesg' and my kernel config file. Has this been fixed? Is it even known? - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWBOfvjpixuAwagxAQFshgP9G1eC8EYEGA92rvL4hJ/7g+gGdcnrx0Hk A/Ybc69m2l/79nauinyuOIL/QQAxRBgmEr/o8Dej2soOJMg2bBo04VuaXzy65PSz ZJOXH2XxEDRG/h3t37O+6UXh4V1NEIujx+KHL6DRHqnAtQw7Dm7hS4d3Onlsri+A hgKR2P6rO8k= =m4Er -----END PGP SIGNATURE----- --_=XFMail.1.2.p0.FreeBSD:980518080638:206=_ Content-Disposition: attachment; filename="CONTROL" Content-Transfer-Encoding: 7bit Content-Description: CONTROL Content-Type: text/plain; charset=us-ascii; name=CONTROL; SizeOnDisk=8244 # # $Id: CONTROL,v 3.5 1998/05/11 11:38:22 dburr Exp $ # # $Log: CONTROL,v $ # Revision 3.5 1998/05/11 11:38:22 dburr # Added firewall stuff. # Made it work. # # Revision 3.4 1998/05/11 08:13:03 dburr # Added IP firewalling. # # Revision 3.3 1998/05/11 08:10:32 dburr # Removed a few oudated stuff. # Took out the new POSIX realtime stuff. # Cleaned up other minor things. # # Revision 3.2 1998/05/11 05:31:11 dburr # Eliminated entry for 'log' pseudo-device. # (apparently no longer required in CURRENT) # # Revision 3.1 1998/05/11 05:29:58 dburr # Updated for 3.0-CURRENT. # # Revision 2.5 1998/04/21 08:33:38 dburr # Added OVERRIDE_TUNER to fix that weird Temic PAL thing. # # Revision 2.4 1998/04/10 11:16:03 dburr # Moved ed0 to irq 10. # # Revision 2.3 1998/04/10 10:42:51 dburr # Fixed defs of ed0, sb0, sbxvi0, and xsbmidi0 because I switched # back to the non-PnP ethernet card. # # Revision 2.2 1998/04/10 08:12:45 dburr # Commented out Coda stuff, until I actually download the thing! # # Revision 2.1 1998/04/10 08:08:48 dburr # Migrated configuration file to fit with FreeBSD 2.2.6-RELEASE. # # Revision 1.19 1998/04/10 07:53:32 dburr # Changed ed0, sb0, sbxvi0, sbmidi0 to reflect crazy configuration # that PnP BIOS assigned when changing Ethernet cards. # # Revision 1.18 1998/04/06 00:57:56 dburr # Changed defines to use ISA ethernet card instead of PCI. # # Revision 1.17 1998/04/05 23:29:52 dburr # Added driver for BrookTree 848 PCI TV capture card. # # Revision 1.16 1998/03/21 10:35:03 dburr # SCBPAGING wasn't the cause of the troubles, so I put it back in. # # Revision 1.15 1998/03/20 18:30:52 dburr # Removed AHC_SCBPAGING_ENABLE to try and fix problems with tosha. # # Revision 1.14 1998/03/14 12:39:59 dburr # Upped maxusers to try and help the file table problem. # # Revision 1.13 1998/03/13 09:06:23 dburr # Upped CHILD_MAX and OPEN_MAX to 512. # # Revision 1.12 1998/03/02 11:14:47 dburr # Upped max child procs and files to 256 per user. # # Revision 1.11 1998/02/23 11:03:59 dburr # Re-enabled SCB paging. # # Revision 1.10 1998/02/16 17:30:35 dburr # Fixed typo in joy0 declaration. # # Revision 1.9 1998/02/16 17:30:00 dburr # Removed PnP support. # # Revision 1.8 1998/02/04 10:07:44 dburr # Removed flags for the nonexistent 2nd IDE disk. # Switched to FreeBSD native sound driver. # Removed NCR/SymBIOS driver since I have # decided to keep the Adaptec card. # # Revision 1.7 1998/01/24 07:43:29 dburr # Trying out original sound driver. # # Revision 1.6 1998/01/24 03:37:58 dburr # Added driver for joystick port. # # Revision 1.5 1998/01/24 03:36:33 dburr # Fixed declaration of sound driver. # # Revision 1.4 1998/01/13 14:21:59 root # fixed for new sound driver. # # Revision 1.3 1998/01/13 07:50:44 root # Added lines for PnP support. # Deleted old sound driver lines. # Added support for PnP sound card. # # Revision 1.2 1998/01/13 07:43:01 root # removed all unused entries. # trimmed down all comments. # # Revision 1.1 1998/01/13 07:25:03 root # Initial revision # # # kernel config file for control.colossus.dyn.ml.org # machine "i386" # we are on an Intel x86 architecture ident CONTROL # identification of this kernel maxusers 100 # sizes certain tables for 10 users options "MAXDSIZ=(256*1024*1024)" # max. proc size = 256MB options "DFLDSIZ=(256*1024*1024)" # dflt. proc. size = 256MB options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 dumps on wd0 # where root fs and crashdumps are cpu "I586_CPU" # our cpu is a Pentium options "CPU_SUSP_HLT" # suspend the CPU on system halt options "COMPAT_43" # syscalls compatible with 4.3BSD options USER_LDT # allow user-level control of i386 ldt options SYSVSHM # SysV IPC (shared memory) options SYSVSEM # SysV IPC (semaphores) options SYSVMSG # SysV IPC (message queues) options "MD5" # MD5 checking in kernel options "VM86" # VM86 mode (for doscmd) options KTRACE # kernel tracing via ktrace(2) options PERFMON # Pentium performance monitors options UCONSOLE # let users grab the console options INET # Internet communications protocols pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device sl 2 # Serial Line IP pseudo-device ppp 2 # Point-to-point protocol pseudo-device bpfilter 6 # Berkeley packet filter pseudo-device tun 2 # Tunnel driver(user process ppp) options PPP_BSDCOMP # PPP BSD compression support options PPP_DEFLATE # PPP zlib/deflate/gzip support options PPP_FILTER # enable bpf filtering options "TCP_COMPAT_42" # emulate 4.2BSD TCP bugs options IPFIREWALL # IP firewalling options IPFIREWALL_DEFAULT_TO_ACCEPT # defaults to accepting all conn's options IPDIVERT # enable ipfw divert sockets options FFS # Fast filesystem options NFS # Network File System options "CD9660" # ISO 9660 filesystem options MSDOSFS # MS DOS File System options PROCFS # Process filesystem options NSWAPDEV=5 # max. number of swap devices options QUOTA # enable disk quotas controller scbus0 # base SCSI code device ch0 # SCSI media changers device sd0 # SCSI disks device st0 # SCSI tapes device cd0 # SCSI CD-ROMs device od0 # SCSI optical disk device worm0 at scbus? # SCSI worm device pt0 at scbus? # SCSI processor type device sctarg0 at scbus? # SCSI target options SCSIDEBUG # enable SCSI debug macros options SCSI_REPORT_GEOMETRY # always report geometry options OD_BOGUS_NOT_READY # fix od sense key weirdness options OD_AUTO_TURNOFF # auto-spindown od's pseudo-device pty 16 # Pseudo ttys - can go as high as 256 pseudo-device speaker # Play music out your speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 # Vnode driver (turns file into device) pseudo-device snp 4 # Snoop - to look at pty/vty/etc.. pseudo-device ccd 4 # Concatenated disk driver pseudo-device su # scsi user pseudo-device ssc # super scsi controller isa0 # ISA bus options "AUTO_EOI_1" # Enable AUTO_EOI for master 8259 options "AUTO_EOI_2" # Enable AUTO_EOI for slave 8259 options BOUNCE_BUFFERS # needed if >16MB RAM for busmaster device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # syscons console driver options MAXCONS=12 # number of virtual consoles device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr # math coprocessor support controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ff vector wdintr # primary IDE controller disk wd0 at wdc0 drive 0 # primary master drive controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ff vector wdintr # secondary IDE controller disk wd2 at wdc1 drive 0 # secondary master drive controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr # floppy drive controller disk fd0 at fdc0 drive 0 # floppy drive 1 device lpt0 at isa? port? tty irq 7 vector lptintr # printer port device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # PS/2 mouse port device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr # serial port 1 device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr # serial port 2 device ed0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector edintr # Ethernet card controller snd0 # sound card controller device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # SoundBlaster 16 device sbxvi0 at isa? drq 5 # SoundBlaster 16 device sbmidi0 at isa? port 0x330 # SoundBlaster 16 device opl0 at isa? port 0x388 # OPL-3 FM synthesizer device joy0 at isa? port "IO_GAME" # Joystick port device pca0 at isa? port IO_TIMER1 tty # PC audio driver (sound out speaker) controller pci0 # PCI bus device bktr0 # BrookTree 848 PCI TV capture card options OVERRIDE_TUNER=1 # force it to be Temic NTSC tuner controller ahc0 # Adaptec PCI SCSI card options AHC_TAGENABLE # Enable tagged command queueing options AHC_SCBPAGING_ENABLE # Enable SCB paging options AHC_ALLOW_MEMIO # Allow memory-mapped I/O options SCSI_DELAY=5 # let SCSI devices spinup before probe options "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)" # increase max. shared memory size --_=XFMail.1.2.p0.FreeBSD:980518080638:206=_ Content-Disposition: attachment; filename="dmesg" Content-Transfer-Encoding: 7bit Content-Description: dmesg Content-Type: text/plain; charset=us-ascii; name=dmesg; SizeOnDisk=3234 Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Tue May 12 15:16:43 PDT 1998 dburr@control.colossus.dyn.ml.org:/usr/src-current/sys/compile/CONTROL Timecounter "i8254" frequency 1193182 Hz cost 4046 ns Timecounter "TSC" frequency 133637136 Hz cost 245 ns CPU: Pentium (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62197760 (60740K bytes) Probing for devices on PCI bus 0: chip0: rev 0x23 on pci0.0.0 chip1: rev 0x25 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 vga0: rev 0x9a on pci0.8.0 ahc0: rev 0x01 int a irq 11 on pci0.9.0 ahc0: aic7860 Single Channel, SCSI Id=7, 3/8 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device scbus0 target 0 lun 0: type 0 fixed SCSI 2 sd0 at scbus0 target 0 lun 0 sd0: Direct-Access 1003MB (2055035 512 byte sectors) sd0: with 4119 cyls, 5 heads, and an average 99 sectors/track scbus0 target 1 lun 0: type 5 removable SCSI 2 cd0 at scbus0 target 1 lun 0 cd0: CD-ROM can't get the size scbus0 target 2 lun 0: type 5 removable SCSI 2 cd1 at scbus0 target 2 lun 0 cd1: CD-ROM can't get the size bktr0: rev 0x12 int a irq 9 on pci0.10.0 Miro TV, Temic NTSC tuner. Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:c0:f0:1d:2c:2d, type NE2000 (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ff on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick sctarg0 at scbus255 target 255 lun 255 sctarg0: Processor Target Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers IP packet filtering initialized, divert enabled, default to accept, logging disa bled --_=XFMail.1.2.p0.FreeBSD:980518080638:206=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 09:12:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04848 for freebsd-scsi-outgoing; Mon, 18 May 1998 09:12:04 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.dpt.com (root@ns1.dpt.com [206.138.241.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04743 for ; Mon, 18 May 1998 09:12:00 -0700 (PDT) (envelope-from salyzyn_mark@dpt.com) Received: from bohica.bohica.dpt.com (salyzyn-mark.dpt.com [198.242.63.84]) by ns1.dpt.com (8.8.7/8.8.7) with SMTP id MAA00324 for ; Mon, 18 May 1998 12:11:37 -0400 Received: by bohica.bohica.dpt.com [198.242.63.84] (NX5.67f2/NX3.0M) id AA27861; Mon, 18 May 98 12:11:53 -0400 Message-Id: <9805181611.AA27861@bohica.bohica.dpt.com> Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Received: by NeXT.Mailer (1.118.2) From: Mark Salyzyn Date: Mon, 18 May 98 12:11:52 -0400 To: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT storage manager Reply-To: salyzyn@dpt.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA04807 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <894885411.0013755.0@office.demon.net>, you wrote: > Having noticed the beta version of the DPT storage management software >for BSDI is infact the SCO binary running under emulation. I was wondering if >anyone had tried to get this working under FreeBSD? The underlying tools (passthrough, dpteng and dptelog) are native ports though. There are some individuals working on various aspects of a port of Storage Manager tools to FreeBSD. No one is currently working in the actual Storage Manager port, just the underlying tools. Once the underlying tools is completed and tested, there is a *possibility* that the SCO Motif and Curses storage managers will function under FreeBSD *only* if the SCO emulation is as reliable as the BSDi SCO emulation. We can only cross our fingers (As I did when we produced the BSDi version). For instance, there are many bugs in the BSD/OS 2.1 release of Storage Manager as a direct result of the SCO emulation problems. DPT has a desire to create native ports for BSDi and FreeBSD of the Storage Manager application, but currently no resources have been assigned to the task. Sincerely -- Mark Salyzyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 10:34:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20934 for freebsd-scsi-outgoing; Mon, 18 May 1998 10:34:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ELR17.ateng.az.honeywell.com (elr17.ateng.az.Honeywell.COM [129.239.169.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA20915 for ; Mon, 18 May 1998 10:34:09 -0700 (PDT) (envelope-from egravel@elr346.ateng.az.honeywell.com) Received: from elr346.ateng.az.honeywell.com by elr346.ateng.az.honeywell.com with SMTP; Mon, 18 May 1998 10:33:24 -0700 Message-ID: <35600E72.504CE9E4@elr346.ateng.az.honeywell.com> Date: Mon, 18 May 1998 10:33:22 -0700 From: Emmanuel Gravel Organization: Honeywell X-Mailer: Mozilla 3.03Gold (X11; I; OpenVMS V6.1 VAXstation 4000-90) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Jaz or SyJet as backup drive Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone used a Jaz or SyJet drive as a backup device (instead of a tape drive)? This is an option I'm considering, understanding the lowering costs of both drive and media of these devices, and the close-to-harddrive speeds they have. I'm wondering if the software can use them effectively. Thanks! Emmanuel Gravel egravel@elr346.ateng.az.honeywell.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 12:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14310 for freebsd-scsi-outgoing; Mon, 18 May 1998 12:50:29 -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 MAA14283 for ; Mon, 18 May 1998 12:50:18 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA06035; Mon, 18 May 1998 13:10:56 -0600 (MDT) Date: Mon, 18 May 1998 13:10:56 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805181910.NAA06035@narnia.plutotech.com> To: Guido Kollerie cc: scsi@FreeBSD.ORG Subject: Re: CAM/stable/BT-958 questions Newsgroups: pluto.freebsd.scsi In-Reply-To: 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 you wrote: > I have installed the CAM-980513-stable patch (file date: 15th May) > on a 2.2-stable system (CTM delta 718). It seems to be running just > fine, nevertheless I have a few questions: > > 1. The README said: > > "You will also likely want a "pass0" device. Look in DM, LINT or > GENERIC for examples." > > However pass0 is not mentioned anywhere in LINT or GENERIC. I am not > sure what DM is. Is pass0 a Current feature not applicable to Stable? I forgot to bundle the DM config file with the 2.2-stable snapshot. Sorry. Pass0 is the pass through interface. You'll need it in order to use camcontrol or xmcd. > 2. What's going on here? > > bt0: bt_cmd: Timeout waiting for adapter ready, status = 0x0 > bt0: btfetchtransinfo - Inquire Setup Info Failed We weren't able to get transfer negotiation settings for one of the drives because the command timed out. I'm looking at alternative ways to get the information that may be more robust. It seems that the adapter doesn't like having lots of outstanding SCSI commands when you make this request. > 3. Why is the Fujitsu harddrive (da0) listed as having "10MB/s > tranfers"? It's a fast-wide scsi device. Hence I expected 20MB/s > tranfers. Probably because the controller hadn't finished negotiating with the drive when we asked. We have no way of easily ensuring that the negotiation has taken place unless we force the card to probe all devices. Forcing the card to probe them all may fail if a device can't handle multiple luns (which the SCSI code probe will avoid), so I wanted to avoid that. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 19:55:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18784 for freebsd-scsi-outgoing; Mon, 18 May 1998 19:55:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18707 for ; Mon, 18 May 1998 19:54:43 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from localhost (crb@localhost) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id WAA04700; Mon, 18 May 1998 22:59:46 -0400 (EDT) (envelope-from crb@ChrisBowman.com) X-Authentication-Warning: quark.ChrisBowman.com: crb owned process doing -bs Date: Mon, 18 May 1998 22:59:45 -0400 (EDT) From: "Christopher R. Bowman" To: Emmanuel Gravel cc: scsi@FreeBSD.ORG Subject: Re: Jaz or SyJet as backup drive In-Reply-To: <35600E72.504CE9E4@elr346.ateng.az.honeywell.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 On Mon, 18 May 1998, Emmanuel Gravel wrote: >Has anyone used a Jaz or SyJet drive as a backup device (instead of >a tape drive)? This is an option I'm considering, understanding the >lowering costs of both drive and media of these devices, and the >close-to-harddrive speeds they have. I'm wondering if the software >can use them effectively. > >Thanks! > >Emmanuel Gravel >egravel@elr346.ateng.az.honeywell.com I used to use a syjet, but I found that the drive was not particularlly tollerant of the heat that builds up in my fairly loaded case, and thus I don't use it for anything any more, since I have not been able to find muffin fans here in Washington DC. (I some one local has a suggestion I would love to hear). At about $60 per cartridge they are pretty expensive. You might want to wait for the Castlewood systems Orb which should have large cartridges at about half the price. --------- Christopher R. Bowman crb@ChrisBowman.com My home page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 18 21:32:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02290 for freebsd-scsi-outgoing; Mon, 18 May 1998 21:32:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (root@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02263 for ; Mon, 18 May 1998 21:32:13 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id VAA17757; Mon, 18 May 1998 21:12:14 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805190312.VAA17757@panzer.plutotech.com> Subject: Re: CAM/stable/BT-958 questions In-Reply-To: from Guido Kollerie at "May 18, 98 04:56:03 pm" To: gkoller@cs.vu.nl Date: Mon, 18 May 1998 21:12:14 -0600 (MDT) Cc: 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 Guido Kollerie wrote... > I have installed the CAM-980513-stable patch (file date: 15th May) > on a 2.2-stable system (CTM delta 718). It seems to be running just > fine, nevertheless I have a few questions: > > 1. The README said: > > "You will also likely want a "pass0" device. Look in DM, LINT or > GENERIC for examples." > > However pass0 is not mentioned anywhere in LINT or GENERIC. I am not > sure what DM is. Is pass0 a Current feature not applicable to Stable? The passthrough driver is in GENERIC in the -current CAM snapshot. If it isn't in GENERIC in the -stable snapshot, that is a bug. It should also be in LINT, but it isn't. DM is a config file for Justin's test box that usually ships with the -current snapshot. If it isn't in -stable, that's probably a bug. The passthrough driver is part of both the stable and current snapshots, though. It is basically a CAM passthrough driver. It allows you to send raw SCSI commands to a device. It also allows you to send other, non-SCSI CAM CCBs. You can do most of the things that a peripheral driver would do via the passthrough driver, if you choose. If you have the passthrough driver in your kernel configuration, there will be one passthrough driver instance created for each SCSI device in your system. By default, the passthrough driver doesn't announce itself on boot. If you boot with -v, you will see the passthrough driver probe messages. The passthrough driver allows programs like xmcd, tosha, cdrecord and camcontrol to function. So it's highly recommended. :) As for your other questions, I'll leave them for Justin to answer, since he wrote the BusLogic driver. 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 19 00:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08688 for freebsd-scsi-outgoing; Tue, 19 May 1998 00:29:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08625 for ; Tue, 19 May 1998 00:29:15 -0700 (PDT) (envelope-from hans@artcom.de) Received: from transrapid.artcom.de by mail.artcom.de with smtp id m0ybihy-00023QC; Tue, 19 May 1998 09:29:18 +0000 (GMT) Date: Tue, 19 May 1998 09:29:18 +0000 (GMT) From: Hans Huebner To: ken@plutotech.com, gibbs@plutotech.com cc: freebsd-scsi@FreeBSD.ORG Subject: Tape driver - What do we really want? 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 Hello there, having thought about the tape subsystem for some time, I'm now trying to make up my mind on the changes which would be desireable. I will add most of the functionality suggested here to the CAM tape subsystem in the near future. Please comment on or add to my list, if you feel the need: * Fast locate support There should be a MTLOCATE operation in MTIOCOP which locates a given block address with the SCSI LOCATE command. This raises the question on how to interpret the data returned by the READ POSITION command (which would be used in MTIOCGET). The SCSI-2 draft specifies a reply format which is different from what the DLT and DDS2 drives I have support. The specification says that block addresses are two bytes long, which is obviously too short. Would we default to the modern format (four bytes for block addresses), or would we want to have quirks for drives which do not adhere to SCSI-2? A new mt subcommand, say 'seek', will be needed to locate a block position using the new MTIOCOP operation. * Implement MTIOCGET fully In particular, the current position should be read and returned (as discussed above). * Make 'mt status' print only the status Currently, 'mt status' prints the status and the permissible compression modes. This is not quite what I'd expect. I'd want to make 'mt status' output the current file number, block position (if available), block size, compression mode and a description of the current position (at BOT, at EOT, at File Mark, not at file mark). As it has been discussed in freebsd-scsi, the block size of the tape can only be determined by reading a block from the tape. Also, this number is valid only for the current block, as the block size may change on tape. Nevertheless, such a feature would be useful since most tapes are blocked at a fixed block size, and all the user wants is to know what option to specify to tar/cpio/restore/dd or whatever. * 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). While we are at it: I also think that having a more elaborate configuration for individual tape drives' capabilities would be desireable. As of now, FreeBSD/CAM is kind of 'naive' with respect to SCSI tape drives, and uses only the least common denominator of the capabilities individual tape drives have. What comes to mind are - Default block sizes for different types of drives - List of supported SCSI features (LOCATE support, compression etc.) - Timeouts for various operations (then again, maybe not) * 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. I'd strive for simplicity, of course. But then again, some features would really be helpful. Keep in mind that I am working on the CAM driver, not the old SCSI stuff. Your input is appreciated. Regards, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 06:52:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18204 for freebsd-scsi-outgoing; Tue, 19 May 1998 06:52:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18193 for ; Tue, 19 May 1998 06:52:54 -0700 (PDT) (envelope-from mollers.pad@sni.de) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.8.8/8.8.8) id NAA19648 for scsi@freebsd.org; Tue, 19 May 1998 13:52:47 GMT Message-Id: <199805191352.NAA19648@nixpbe.pdb.sni.de> Subject: Problems with Microtek E6 and AHA2825 To: scsi@FreeBSD.ORG Date: Tue, 19 May 98 15:52:45 MEST From: Josef Moellers X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have what appears to be a Microtec E6 (new). I have it connected to an AHA2825. It works OK unter Windoze, and under FreeBSD 2.2.5 I can send an INQUIRY command and get the data back. However, when I start sane-0.72, the system panics due to an unexpected bus free phase. Any suggestions? TIA, -- Josef Moellers mollers.pad@sni.de PS Dieser Artikel enthaelt einzig und allein meine persoenlichen Ansichten! PS This article contains my own, personal opinion only! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 10:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01394 for freebsd-scsi-outgoing; Tue, 19 May 1998 10:23:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA01379 for ; Tue, 19 May 1998 10:23:33 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA30443 (5.67b/IDA-1.5 for freebsd-scsi@FreeBSD.ORG); Tue, 19 May 1998 19:23:11 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id TAA01620; Tue, 19 May 1998 19:17:55 +0200 (MET DST) From: Wilko Bulte Message-Id: <199805191717.TAA01620@yedi.iaf.nl> Subject: Re: CAM/stable/BT-958 questions In-Reply-To: <199805190312.VAA17757@panzer.plutotech.com> from "Kenneth D. Merry" at "May 18, 98 09:12:14 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Tue, 19 May 1998 19:17:55 +0200 (MET DST) Cc: gkoller@cs.vu.nl, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote... > Guido Kollerie wrote... > If you have the passthrough driver in your kernel configuration, > there will be one passthrough driver instance created for each SCSI device > in your system. By default, the passthrough driver doesn't announce itself > on boot. If you boot with -v, you will see the passthrough driver probe > messages. > > The passthrough driver allows programs like xmcd, tosha, cdrecord > and camcontrol to function. So it's highly recommended. :) But only for machines for which you a very sure that no freaky hacker gains root access... A FORMAT UNIT is way faster than rm -rf / ... Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 17:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02389 for freebsd-scsi-outgoing; Tue, 19 May 1998 17:59:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from priscilla.mu.org (root@priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02380 for ; Tue, 19 May 1998 17:59:40 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id TAA16824; Tue, 19 May 1998 19:45:30 -0500 (CDT) (envelope-from paul) Message-ID: <19980519194530.A16812@mu.org> Date: Tue, 19 May 1998 19:45:30 -0500 From: Paul Saab To: scsi@FreeBSD.ORG Subject: Re: CAM/stable/BT-958 questions References: <199805181910.NAA06035@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805181910.NAA06035@narnia.plutotech.com>; from Justin T. Gibbs on Mon, May 18, 1998 at 01:10:56PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs (gibbs@narnia.plutotech.com) wrote: > In article you wrote: > > I have installed the CAM-980513-stable patch (file date: 15th May) > > on a 2.2-stable system (CTM delta 718). It seems to be running just > > fine, nevertheless I have a few questions: > > > > 1. The README said: > > > > "You will also likely want a "pass0" device. Look in DM, LINT or > > GENERIC for examples." > > > > However pass0 is not mentioned anywhere in LINT or GENERIC. I am not > > sure what DM is. Is pass0 a Current feature not applicable to Stable? > > I forgot to bundle the DM config file with the 2.2-stable snapshot. > Sorry. Pass0 is the pass through interface. You'll need it in order > to use camcontrol or xmcd. When I run camcontrol -l under -stable I get this... camcontrol: cam_real_open_device: Path Inquiry CCB failed cam_real_open_device: Inappropriate ioctl for device Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 19:54:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24938 for freebsd-scsi-outgoing; Tue, 19 May 1998 19:54:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24914 for ; Tue, 19 May 1998 19:54:04 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.8.7/8.8.7) with ESMTP id WAA07912 for ; Tue, 19 May 1998 22:53:47 -0400 (EDT) From: Cory Kempf Received: (from ckempf@localhost) by singularity.enigami.com (8.8.8/8.8.8) id WAA28943 for freebsd-scsi@freebsd.org; Tue, 19 May 1998 22:51:59 -0400 (EDT) (envelope-from ckempf@enigami.com) Date: Tue, 19 May 1998 22:51:59 -0400 (EDT) Message-Id: <199805200251.WAA28943@singularity.enigami.com> To: freebsd-scsi@FreeBSD.ORG Subject: GENERIC kernel build broken? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I cvsup'd the latest sources of about, an hour or so ago, applied the -current snapshot, (fixed the .rej from sbin/Makefile), and attempted to build GENERIC: loading kernel isp_freebsd.o: Undefined symbol `_scsi_alloc_bus' referenced from text segment isp_freebsd.o: Undefined symbol `_scsi_attachdevs' referenced from text segment isp.o: Undefined symbol `_scsi_done' referenced from text segment isp.o: Undefined symbol `_scsi_done' referenced from text segment subr_devstat.o: Undefined symbol `_getmicroruntime' referenced from text segment subr_devstat.o: Undefined symbol `_getmicroruntime' referenced from text segment I am guessing that this is a SCSI issue, not a -current issue? +C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 20:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03879 for freebsd-scsi-outgoing; Tue, 19 May 1998 20:55:00 -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 UAA03870 for ; Tue, 19 May 1998 20:54:57 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id VAA25053; Tue, 19 May 1998 21:54:48 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805200354.VAA25053@panzer.plutotech.com> Subject: Re: GENERIC kernel build broken? In-Reply-To: <199805200251.WAA28943@singularity.enigami.com> from Cory Kempf at "May 19, 98 10:51:59 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 19 May 1998 21:54:48 -0600 (MDT) Cc: 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 Cory Kempf wrote... > Hi all, > I cvsup'd the latest sources of about, an hour or so ago, applied the > -current snapshot, (fixed the .rej from sbin/Makefile), and attempted > to build GENERIC: > > loading kernel > isp_freebsd.o: Undefined symbol `_scsi_alloc_bus' referenced from text segment > isp_freebsd.o: Undefined symbol `_scsi_attachdevs' referenced from text segment > isp.o: Undefined symbol `_scsi_done' referenced from text segment > isp.o: Undefined symbol `_scsi_done' referenced from text segment This is the QLogic SCSI/FC driver that Matthew Jacob wrote. It hasn't been ported to CAM just yet, so you'd better take it out of your kernel. > subr_devstat.o: Undefined symbol `_getmicroruntime' referenced from text segment > subr_devstat.o: Undefined symbol `_getmicroruntime' referenced from text segment That's a known problem, it has been changed to getmicrouptime(), I believe. You can probably just replace the getmicroruntime() calls in subr_devstat.c with getmicrouptime(). > I am guessing that this is a SCSI issue, not a -current issue? It's a CAM issue, not a -current issue. 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 19 21:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08154 for freebsd-scsi-outgoing; Tue, 19 May 1998 21:31:50 -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 VAA08146 for ; Tue, 19 May 1998 21:31:46 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id WAA25425; Tue, 19 May 1998 22:31:42 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805200431.WAA25425@panzer.plutotech.com> Subject: Re: CAM/stable/BT-958 questions In-Reply-To: <19980519194530.A16812@mu.org> from Paul Saab at "May 19, 98 07:45:30 pm" To: paul@mu.org (Paul Saab) Date: Tue, 19 May 1998 22:31:42 -0600 (MDT) Cc: 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 Paul Saab wrote... > Justin T. Gibbs (gibbs@narnia.plutotech.com) wrote: > > In article you wrote: > > > I have installed the CAM-980513-stable patch (file date: 15th May) > > > on a 2.2-stable system (CTM delta 718). It seems to be running just > > > fine, nevertheless I have a few questions: > > > > > > 1. The README said: > > > > > > "You will also likely want a "pass0" device. Look in DM, LINT or > > > GENERIC for examples." > > > > > > However pass0 is not mentioned anywhere in LINT or GENERIC. I am not > > > sure what DM is. Is pass0 a Current feature not applicable to Stable? > > > > I forgot to bundle the DM config file with the 2.2-stable snapshot. > > Sorry. Pass0 is the pass through interface. You'll need it in order > > to use camcontrol or xmcd. > > When I run camcontrol -l under -stable I get this... > camcontrol: cam_real_open_device: Path Inquiry CCB failed > cam_real_open_device: Inappropriate ioctl for device What it's telling you is that for some reason, the CAMIOCOMMAND ioctl definition in camcontrol isn't the same as the CAMIOCOMMAND ioctl definition in the kernel. Do you by any chance have some old CAM headers lying around somewhere? They'd be in /usr/include/cam/... 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 19 22:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15266 for freebsd-scsi-outgoing; Tue, 19 May 1998 22:24:27 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from priscilla.mu.org (paul@priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15259 for ; Tue, 19 May 1998 22:24:26 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id AAA17789; Wed, 20 May 1998 00:23:34 -0500 (CDT) (envelope-from paul) Message-ID: <19980520002333.A17764@mu.org> Date: Wed, 20 May 1998 00:23:34 -0500 From: Paul Saab To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: CAM/stable/BT-958 questions References: <19980519194530.A16812@mu.org> <199805200431.WAA25425@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805200431.WAA25425@panzer.plutotech.com>; from Kenneth D. Merry on Tue, May 19, 1998 at 10:31:42PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry (ken@plutotech.com) wrote: > Paul Saab wrote... > > > > When I run camcontrol -l under -stable I get this... > > camcontrol: cam_real_open_device: Path Inquiry CCB failed > > cam_real_open_device: Inappropriate ioctl for device > > What it's telling you is that for some reason, the CAMIOCOMMAND > ioctl definition in camcontrol isn't the same as the CAMIOCOMMAND ioctl > definition in the kernel. > > Do you by any chance have some old CAM headers lying around > somewhere? They'd be in /usr/include/cam/... This is the first time I installed CAM, so I don't think I have any old headers around. Other than not being able to use camcontrol, I have been pleased with how it is functioning. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 22:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15935 for freebsd-scsi-outgoing; Tue, 19 May 1998 22:28: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 WAA15924 for ; Tue, 19 May 1998 22:28:35 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA25784; Tue, 19 May 1998 23:28:31 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805200528.XAA25784@panzer.plutotech.com> Subject: Re: CAM/stable/BT-958 questions In-Reply-To: <19980520002333.A17764@mu.org> from Paul Saab at "May 20, 98 00:23:34 am" To: paul@mu.org (Paul Saab) Date: Tue, 19 May 1998 23:28:31 -0600 (MDT) Cc: 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 Paul Saab wrote... > Kenneth D. Merry (ken@plutotech.com) wrote: > > Paul Saab wrote... > > > > > > When I run camcontrol -l under -stable I get this... > > > camcontrol: cam_real_open_device: Path Inquiry CCB failed > > > cam_real_open_device: Inappropriate ioctl for device > > > > What it's telling you is that for some reason, the CAMIOCOMMAND > > ioctl definition in camcontrol isn't the same as the CAMIOCOMMAND ioctl > > definition in the kernel. > > > > Do you by any chance have some old CAM headers lying around > > somewhere? They'd be in /usr/include/cam/... > > This is the first time I installed CAM, so I don't think I have > any old headers around. Other than not being able to use camcontrol, > I have been pleased with how it is functioning. That's bizarre. I'm glad you're happy with the rest of it, though. :) Are there any other stable/CAM users out there? Have you been able to use camcontrol? (remember you have to have device pass0 in your kernel config file and you need to make the xpt and pass devices in /dev) What I'm trying to determine is whether this is an isolated incident or whether it's a problem with the -stable port in general. 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 19 23:20:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24032 for freebsd-scsi-outgoing; Tue, 19 May 1998 23:20:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from priscilla.mu.org (paul@priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24004 for ; Tue, 19 May 1998 23:20:18 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id BAA17990; Wed, 20 May 1998 01:19:27 -0500 (CDT) (envelope-from paul) Message-ID: <19980520011927.A17985@mu.org> Date: Wed, 20 May 1998 01:19:27 -0500 From: Paul Saab To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: CAM/stable/BT-958 questions References: <19980520002333.A17764@mu.org> <199805200528.XAA25784@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805200528.XAA25784@panzer.plutotech.com>; from Kenneth D. Merry on Tue, May 19, 1998 at 11:28:31PM -0600 X-Mutt-References: <199805200528.XAA25784@panzer.plutotech.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry (ken@plutotech.com) wrote: > > That's bizarre. I'm glad you're happy with the rest of it, though. :) > > Are there any other stable/CAM users out there? Have you been able to use > camcontrol? (remember you have to have device pass0 in your kernel config > file and you need to make the xpt and pass devices in /dev) What I'm > trying to determine is whether this is an isolated incident or whether it's > a problem with the -stable port in general. I modified the GENERIC kernel -stable CAM and assumed that pass0 was in the kernel file. It works as it should now. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 19 23:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24390 for freebsd-scsi-outgoing; Tue, 19 May 1998 23:22:29 -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 XAA24379 for ; Tue, 19 May 1998 23:22:24 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id AAA26269; Wed, 20 May 1998 00:22:17 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805200622.AAA26269@panzer.plutotech.com> Subject: Re: CAM/stable/BT-958 questions In-Reply-To: <19980520011927.A17985@mu.org> from Paul Saab at "May 20, 98 01:19:27 am" To: paul@mu.org (Paul Saab) Date: Wed, 20 May 1998 00:22:17 -0600 (MDT) Cc: 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 Paul Saab wrote... > Kenneth D. Merry (ken@plutotech.com) wrote: > > > > That's bizarre. I'm glad you're happy with the rest of it, though. :) > > > > Are there any other stable/CAM users out there? Have you been able to use > > camcontrol? (remember you have to have device pass0 in your kernel config > > file and you need to make the xpt and pass devices in /dev) What I'm > > trying to determine is whether this is an isolated incident or whether it's > > a problem with the -stable port in general. > > I modified the GENERIC kernel -stable CAM and assumed that pass0 > was in the kernel file. It works as it should now. Ahh, okay. That makes sense now. What doesn't make sense is why the open of the passthrough device didn't fail. Hmm. 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 20 07:39:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11573 for freebsd-scsi-outgoing; Wed, 20 May 1998 07:39:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11568 for ; Wed, 20 May 1998 07:39:51 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id JAA11166; Wed, 20 May 1998 09:38:43 -0500 (CDT) From: "Greg Rowe" Message-Id: <9805201438.ZM11164@psv.oss.uswest.net> Date: Wed, 20 May 1998 14:38:43 +0000 X-Mailer: Z-Mail (3.2.1 10apr95) To: gibbs@narnia.plutotech.com Subject: CAM and Adaptec 2940UW Rev E Cc: scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin, We finally got a chance to test the Adaptec 2940UW Revision E cards with CAM and the problems still exist. Our configuration is a Tyan MB, 2 Adaptec 2940UW's , 3 - 4.4 Gig Seagate ST34572W drives. OS is 3.0 current as of 05/15 and CAM-980513. The revision D cards work with no problem, but running bonnie or iozone with the Rev E cards produce the following (and a system crash): May 19 15:11:13 test6 /kernel: SEQADDR == 0x115 May 19 15:11:13 test6 /kernel: SSTAT1 == 0x13 May 19 15:11:13 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x5f - timed out in dataout phase, SCSISIGI == 0xe6 May 19 15:11:13 test6 /kernel: SEQADDR == 0x115 May 19 15:11:13 test6 /kernel: SSTAT1 == 0x13 May 19 15:11:13 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x6 - timed out in dataout phase, SCSISIGI == 0xe6 May 19 15:11:13 test6 /kernel: SEQADDR == 0x115 May 19 15:11:13 test6 /kernel: SSTAT1 == 0x13 May 19 15:11:13 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x61 - timed out in dataout phase, SCSISIGI == 0xe6 May 19 15:11:14 test6 /kernel: SEQADDR == 0x115 May 19 15:11:14 test6 /kernel: SSTAT1 == 0x13 May 19 15:11:14 test6 /kernel: (da1:ahc1:0:0:0): no longer in timeout May 19 15:11:14 test6 /kernel: ahc1: Issued Channel A Bus Reset. 126 SCBs aborted May 19 15:11:14 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x43 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 dmesg ahc0: rev 0x01 int a irq 9 on pci0.13.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x01 int a irq 10 on pci0.14.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs adv1 not found npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number JK41469003FDWY da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number JK44171206N0R7 da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: Serial Number JK38948706N0R6 da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) CAM control pass0: generation: 4 index: 1 status: MORE da0: generation: 4 index: 2 status: LAST pass1: generation: 4 index: 1 status: MORE da1: generation: 4 index: 2 status: LAST pass2: generation: 4 index: 1 status: MORE da2: generation: 4 index: 2 status: LAST Greg -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 10:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05538 for freebsd-scsi-outgoing; Wed, 20 May 1998 10:18: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 KAA05465 for ; Wed, 20 May 1998 10:17:57 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 26199 invoked by uid 1000); 20 May 1998 18:19:06 -0000 Message-ID: X-Mailer: XFMail 1.3-beta-042198 [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: Wed, 20 May 1998 14:19:06 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Raul Zighelboim Subject: RE: DPT driver performance Cc: "n@nectar.com" , "scsi@freebsd.org" , Tom Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Apr-98 Raul Zighelboim wrote: > > I am running ONE drive on an AHC controller and ONE drive on a DPT > controller. No stripping, no raid. Just one drive. Both are formated > with 512b/s. > > No, I do not intend to run iozone as my main application. But it > bothers me that under the same conditions, the Adaptec controller can > write a large file twice as fast. > > You're saying that this is not relevant ? What you see is normal. Consider that the DPT has its own CPU, O/S, and SCSI controller chip. There are certain operations in which the latencies (as minute as they may be) introduced here are visible. The AHC controllers are directly attached to the system bus. If you intend to run only a single drive, on a desktop, I would say that a DPT is a costly and ineffective solution. If your needs are for RAID arrays, large disk farms, very heavy concurrent load, the DPT will serve you rather well. When testing/certifying a new driver release, I never use any of the standard benchmarks, for a reason; They are mostly geared towards sequential access to large files. Most of the DPTs are used in a heavily random seek environment or in a ``cannot fail'' environment. For these, I use my own mad testing procedure, which has been posted here more than once. I apologize for the late reply, but today is the second day since my move and the first in which I read email. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 10:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08265 for freebsd-scsi-outgoing; Wed, 20 May 1998 10:33:04 -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 KAA08256 for ; Wed, 20 May 1998 10:33:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (root@[209.54.254.2]) by ns.mauswerks.net (8.8.0/8.6.9) with ESMTP id KAA05734; Wed, 20 May 1998 10:35:06 -0700 Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id KAA30664; Wed, 20 May 1998 10:32:51 -0700 Message-ID: <356313C3.2C7A2762@feral.com> Date: Wed, 20 May 1998 10:32:51 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: "Kenneth D. Merry" CC: Cory Kempf , freebsd-scsi@FreeBSD.ORG Subject: Re: GENERIC kernel build broken? References: <199805200354.VAA25053@panzer.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 It's *almost* done. And it's a SCSI *and* SCSI-FC driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 10:45:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10298 for freebsd-scsi-outgoing; Wed, 20 May 1998 10:45:16 -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 KAA10292 for ; Wed, 20 May 1998 10:45:15 -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 LAA16065; Wed, 20 May 1998 11:45:13 -0600 (MDT) Message-Id: <199805201745.LAA16065@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: "Greg Rowe" cc: gibbs@plutotech.com, scsi@FreeBSD.ORG Subject: Re: CAM and Adaptec 2940UW Rev E In-reply-to: Your message of "Wed, 20 May 1998 14:38:43 -0000." <9805201438.ZM11164@psv.oss.uswest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 May 1998 11:41:02 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Justin, > > We finally got a chance to test the Adaptec 2940UW Revision E cards with CAM >and the problems still exist. Our configuration is a Tyan MB, 2 Adaptec >2940UW's , 3 - 4.4 Gig Seagate ST34572W drives. OS is 3.0 current as of 05/15 >and CAM-980513. The revision D cards work with no problem, but running bonnie >or iozone with the Rev E cards produce the following (and a system crash): I know about one system crash during recovery and have fixed that locally, but I'm working now to try and reproduce your error. I have to plead ignorance to what you mean by rev D and rev E cards. I have cards with both rev 0 and 1 aic7880s on them, but I don't know where you are getting the D and E letter. This is the card I'm going to work with: ahc0: rev 0x01 int a irq 9 on pci0.9.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs As you can see, it has a rev 1 aic7880. I have access to ultra-narrow versions of the 4gig Barracuda you're using (same firmware rev. even), but if this turns out to be a wide problem, I won't be able to reproduce it here. >From the debugging messages you've sent me, it's clear that the chip is hanging up attempting to turn off the DMA fifo, and I don't know why this is the case. It would be useful for you to add a printf in ahc_timeout() that give the contents of a register: printf("DFCNTRL = %x\n", ahc_inb(ahc, DFCNTRL)); Place it down near the printf for SEQADDR and friends. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 14:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05332 for freebsd-scsi-outgoing; Wed, 20 May 1998 14:46:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05291 for ; Wed, 20 May 1998 14:46:09 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id QAA12759; Wed, 20 May 1998 16:45:06 -0500 (CDT) From: "Greg Rowe" Message-Id: <9805202145.ZM12757@psv.oss.uswest.net> Date: Wed, 20 May 1998 21:45:06 +0000 In-Reply-To: "Justin T. Gibbs" "Re: CAM and Adaptec 2940UW Rev E" (May 20, 11:41am) References: <199805201745.LAA16065@pluto.plutotech.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: "Justin T. Gibbs" Subject: Re: CAM and Adaptec 2940UW Rev E Cc: scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin, The cards we are having problems with have a white barcode label over the 7880 chip and are marked: AHA-2940UW 945300-01 E (We have 50 or 60 marked "C" and a 150 or so marked "D") 9749 (We have a dozen or so marked "E" that all exhibit the problem) Under the label, the chip is marked: AIC-7880P BQWA740 740111 BC9564.1 We added the printf statement as you requested, built and installed a new kernel, and made a number of Iozone runs, but I don't think we ever recieved the debug message you were looking for. This is from the last run we did before the system crashed: File '/home/Bonnie.204', size: 1048576000 Writing with putc()...May 20 16:11:21 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x0 - timed out in data t phase, SCSISIGI == 0xe6 May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): BDR message in message buffer May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x0 - timed out in dataout phase, SCSISIGI == xf6 May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): no longer in timeout May 20 16:11:39 test6 /kernel: ahc1: Issued Channel A Bus Reset. 128 SCBs aborted May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, CSISIGI == 0x0 May 20 16:11:39 test6 /kernel: SEQADDR == 0x18b May 20 16:11:39 test6 /kernel: SSTAT1 == 0x0 May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, CSISIGI == 0x0 May 20 16:11:39 test6 /kernel: SEQADDR == 0x18b May 20 16:11:39 test6 /kernel: SSTAT1 == 0x0 May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): no longer in timeout May 20 16:11:39 test6 /kernel: ahc1: Issued Channel A Bus Reset. 65 SCBs aborted May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): WRITE(06). CDB: a 1e 85 10 80 0 May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,2 May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): Scsi bus reset occurred field replaceable unit: 2 May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): WRITE(06). CDB: a 1e 85 10 80 0 May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): UNIT ATTENTION asc:29,2 May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): Scsi bus reset occurred field replaceable unit: 2 done We can drop the transfer rate down to 10MBS in the card setup and we don't see any problems. Note that da1 and da2 are ccd devices, but we have similar errors on non-ccd devices. We can give you access to the system if that would help ? Thanks, Greg On May 20, 11:41am, Justin T. Gibbs wrote: > Subject: Re: CAM and Adaptec 2940UW Rev E > >Justin, > > > > We finally got a chance to test the Adaptec 2940UW Revision E cards with CAM > >and the problems still exist. Our configuration is a Tyan MB, 2 Adaptec > >2940UW's , 3 - 4.4 Gig Seagate ST34572W drives. OS is 3.0 current as of 05/15 > >and CAM-980513. The revision D cards work with no problem, but running bonnie > >or iozone with the Rev E cards produce the following (and a system crash): > > I know about one system crash during recovery and have fixed that locally, > but I'm working now to try and reproduce your error. I have to plead > ignorance to what you mean by rev D and rev E cards. I have cards with > both rev 0 and 1 aic7880s on them, but I don't know where you are getting > the D and E letter. > > This is the card I'm going to work with: > > ahc0: rev 0x01 int a irq 9 on pci0.9.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > As you can see, it has a rev 1 aic7880. > > I have access to ultra-narrow versions of the 4gig Barracuda you're using > (same firmware rev. even), but if this turns out to be a wide problem, I > won't be able to reproduce it here. > > >From the debugging messages you've sent me, it's clear that the chip is > hanging up attempting to turn off the DMA fifo, and I don't know why this > is the case. It would be useful for you to add a printf in ahc_timeout() > that give the contents of a register: > > printf("DFCNTRL = %x\n", ahc_inb(ahc, DFCNTRL)); > > Place it down near the printf for SEQADDR and friends. > > -- > Justin > >-- End of excerpt from Justin T. Gibbs -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 15:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07648 for freebsd-scsi-outgoing; Wed, 20 May 1998 15:00:21 -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 OAA07550 for ; Wed, 20 May 1998 14:59:52 -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 PAA29614; Wed, 20 May 1998 15:59:27 -0600 (MDT) Message-Id: <199805202159.PAA29614@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: "Greg Rowe" cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: CAM and Adaptec 2940UW Rev E In-reply-to: Your message of "Wed, 20 May 1998 21:45:06 -0000." <9805202145.ZM12757@psv.oss.uswest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 May 1998 15:55:16 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Justin, > >The cards we are having problems with have a white barcode label over the 7880 >chip and are marked: > AHA-2940UW > 945300-01 E (We have 50 or 60 marked "C" and a 150 or so marked "D") > 9749 (We have a dozen or so marked "E" that all exhibit the problem >) I have C and A cards, but no E's. Can you mail me one? It might be good to have one of the drives you have reproduced this with as well. Justin T. Gibbs Pluto Technologies International Inc. 2511 55th. St. Boulder CO, 80301 > We added the printf statement as you requested, built and installed a new >kernel, and made a number of Iozone runs, but I don't think we ever recieved >the debug message you were looking for. This is from the last run we did >before the system crashed: > >File '/home/Bonnie.204', size: 1048576000 >Writing with putc()...May 20 16:11:21 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x0 >- timed out in data >t phase, SCSISIGI == 0xe6 >May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 >May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 If you placed the printf right next to these guys, why didn't it print? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 20 17:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04145 for freebsd-scsi-outgoing; Wed, 20 May 1998 17:35:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04136 for ; Wed, 20 May 1998 17:35:40 -0700 (PDT) (envelope-from rzig@verio.net) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Wed, 20 May 1998 19:35:07 -0500 Message-ID: From: Raul Zighelboim To: "'Greg Rowe'" , "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: RE: CAM and Adaptec 2940UW Rev E Date: Wed, 20 May 1998 19:35:05 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Somewhere I read that revision E of the adaptec card had problems, and Adaptec reccomended flashing the card down to revision D of the bios.... > -----Original Message----- > From: Greg Rowe [SMTP:greg@uswest.net] > Sent: Wednesday, May 20, 1998 4:45 PM > To: Justin T. Gibbs > Cc: scsi@FreeBSD.ORG > Subject: Re: CAM and Adaptec 2940UW Rev E > > Justin, > > The cards we are having problems with have a white barcode label over > the 7880 > chip and are marked: > AHA-2940UW > 945300-01 E (We have 50 or 60 marked "C" and a 150 or so marked > "D") > 9749 (We have a dozen or so marked "E" that all exhibit the > problem) > > Under the label, the chip is marked: > AIC-7880P > BQWA740 > 740111 > BC9564.1 > > We added the printf statement as you requested, built and installed a > new > kernel, and made a number of Iozone runs, but I don't think we ever > recieved > the debug message you were looking for. This is from the last run we > did before > the system crashed: > > File '/home/Bonnie.204', size: 1048576000 > Writing with putc()...May 20 16:11:21 test6 /kernel: (da1:ahc1:0:0:0): > SCB 0x0 > - timed out in data > t phase, SCSISIGI == 0xe6 > May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 > May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): BDR message in > message buffer > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x0 - timed out > in dataout > phase, SCSISIGI == > xf6 > May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 > May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): no longer in timeout > May 20 16:11:39 test6 /kernel: ahc1: Issued Channel A Bus Reset. 128 > SCBs > aborted > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x0 - timed out > while > idle, LASTPHASE == 0x1, > CSISIGI == 0x0 > May 20 16:11:39 test6 /kernel: SEQADDR == 0x18b > May 20 16:11:39 test6 /kernel: SSTAT1 == 0x0 > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): SCB 0x0 - timed out > while > idle, LASTPHASE == 0x1, > CSISIGI == 0x0 > May 20 16:11:39 test6 /kernel: SEQADDR == 0x18b > May 20 16:11:39 test6 /kernel: SSTAT1 == 0x0 > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): no longer in timeout > May 20 16:11:39 test6 /kernel: ahc1: Issued Channel A Bus Reset. 65 > SCBs > aborted > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): WRITE(06). CDB: a 1e > 85 10 80 > 0 > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): UNIT ATTENTION > asc:29,2 > May 20 16:11:39 test6 /kernel: (da2:ahc1:0:1:0): Scsi bus reset > occurred field > replaceable unit: 2 > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): WRITE(06). CDB: a 1e > 85 10 80 > 0 > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): UNIT ATTENTION > asc:29,2 > May 20 16:11:39 test6 /kernel: (da1:ahc1:0:0:0): Scsi bus reset > occurred field > replaceable unit: 2 > done > > We can drop the transfer rate down to 10MBS in the card setup and we > don't see > any problems. Note that da1 and da2 are ccd devices, but we have > similar errors > on non-ccd devices. We can give you access to the system if that would > help ? > > Thanks, > Greg > > On May 20, 11:41am, Justin T. Gibbs wrote: > > Subject: Re: CAM and Adaptec 2940UW Rev E > > >Justin, > > > > > > We finally got a chance to test the Adaptec 2940UW Revision E > cards with > CAM > > >and the problems still exist. Our configuration is a Tyan MB, 2 > Adaptec > > >2940UW's , 3 - 4.4 Gig Seagate ST34572W drives. OS is 3.0 current > as of > 05/15 > > >and CAM-980513. The revision D cards work with no problem, but > running > bonnie > > >or iozone with the Rev E cards produce the following (and a system > crash): > > > > I know about one system crash during recovery and have fixed that > locally, > > but I'm working now to try and reproduce your error. I have to > plead > > ignorance to what you mean by rev D and rev E cards. I have cards > with > > both rev 0 and 1 aic7880s on them, but I don't know where you are > getting > > the D and E letter. > > > > This is the card I'm going to work with: > > > > ahc0: rev 0x01 int a irq 9 on > pci0.9.0 > > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > > > As you can see, it has a rev 1 aic7880. > > > > I have access to ultra-narrow versions of the 4gig Barracuda you're > using > > (same firmware rev. even), but if this turns out to be a wide > problem, I > > won't be able to reproduce it here. > > > > >From the debugging messages you've sent me, it's clear that the > chip is > > hanging up attempting to turn off the DMA fifo, and I don't know why > this > > is the case. It would be useful for you to add a printf in > ahc_timeout() > > that give the contents of a register: > > > > printf("DFCNTRL = %x\n", ahc_inb(ahc, DFCNTRL)); > > > > Place it down near the printf for SEQADDR and friends. > > > > -- > > Justin > > > >-- End of excerpt from Justin T. Gibbs > > > > -- > Greg Rowe US WEST - !NTERACT Internet Services > "To err is human, to really foul up requires the root password." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 02:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05581 for freebsd-scsi-outgoing; Thu, 21 May 1998 02:34:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05574 for ; Thu, 21 May 1998 02:34:32 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by keg.cs.vu.nl with smtp (Smail3.1.28.1 #48) id m0ycRk3-0007BxC; Thu, 21 May 98 11:34 +0200 Date: Thu, 21 May 1998 11:34:26 +0200 (MET DST) From: Guido Kollerie To: freebsd-scsi@FreeBSD.ORG Subject: CAM performance on -stable 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 To get an indication of the perfomance of CAM I have performed three make -j4 buildworld's. Once with the non-CAM kernel and twice with the CAM kernel. /usr was mounted async,noatime and I used -O -pipe -DCAM_OLD_TIMEOUT for CFLAGS, NOPROFILE was true To my surprise all the three buildworld times were nearly identical (3hr 9min +/- 1min). I had expected the CAM kernel to perform much better as it allows my BT-958 to use Command Tagged Queueing were as the non-CAM kernel did not. Has anyone else found similar results on a -stable system? -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 06:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07023 for freebsd-scsi-outgoing; Thu, 21 May 1998 06:24:53 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07018 for ; Thu, 21 May 1998 06:24:49 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by keg.cs.vu.nl with smtp (Smail3.1.28.1 #48) id m0ycVKv-0007CDC; Thu, 21 May 98 15:24 +0200 Date: Thu, 21 May 1998 15:24:45 +0200 (MET DST) From: Guido Kollerie To: freebsd-scsi@FreeBSD.ORG Subject: Defect list (camcontrol) 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 $ camcontrol -d -f phys Got 239 defects. This seems to be a little to much. I had expected a few remapped blocks but not 239! Is this something I should worry about? -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 07:04:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12789 for freebsd-scsi-outgoing; Thu, 21 May 1998 07:04:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12784 for ; Thu, 21 May 1998 07:04:14 -0700 (PDT) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.8.8/8.8.5) id JAA16095; Thu, 21 May 1998 09:03:12 -0500 (CDT) From: "Greg Rowe" Message-Id: <9805211403.ZM16093@psv.oss.uswest.net> Date: Thu, 21 May 1998 14:03:12 +0000 In-Reply-To: "Justin T. Gibbs" "Re: CAM and Adaptec 2940UW Rev E" (May 20, 3:55pm) References: <199805202159.PAA29614@pluto.plutotech.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: "Justin T. Gibbs" Subject: Re: CAM and Adaptec 2940UW Rev E Cc: scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll ship a card out to you today. Greg On May 20, 3:55pm, Justin T. Gibbs wrote: > Subject: Re: CAM and Adaptec 2940UW Rev E > >Justin, > > > >The cards we are having problems with have a white barcode label over the 7880 > >chip and are marked: > > AHA-2940UW > > 945300-01 E (We have 50 or 60 marked "C" and a 150 or so marked "D") > > 9749 (We have a dozen or so marked "E" that all exhibit the problem > >) > > I have C and A cards, but no E's. Can you mail me one? It might be > good to have one of the drives you have reproduced this with as well. > > Justin T. Gibbs > Pluto Technologies International Inc. > 2511 55th. St. > Boulder CO, 80301 > > > We added the printf statement as you requested, built and installed a new > >kernel, and made a number of Iozone runs, but I don't think we ever recieved > >the debug message you were looking for. This is from the last run we did > >before the system crashed: > > > >File '/home/Bonnie.204', size: 1048576000 > >Writing with putc()...May 20 16:11:21 test6 /kernel: (da1:ahc1:0:0:0): SCB 0x0 > >- timed out in data > >t phase, SCSISIGI == 0xe6 > >May 20 16:11:39 test6 /kernel: SEQADDR == 0x115 > >May 20 16:11:39 test6 /kernel: SSTAT1 == 0x13 > > If you placed the printf right next to these guys, why didn't it print? > > -- > Justin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >-- End of excerpt from Justin T. Gibbs -- Greg Rowe US WEST - !NTERACT Internet Services "To err is human, to really foul up requires the root password." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 07:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13539 for freebsd-scsi-outgoing; Thu, 21 May 1998 07:11:10 -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 HAA13534 for ; Thu, 21 May 1998 07:11:08 -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 HAA06843; Thu, 21 May 1998 07:13:07 -0700 Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id HAA00844; Thu, 21 May 1998 07:10:54 -0700 Date: Thu, 21 May 1998 07:10:54 -0700 From: Matthew Jacob Message-Id: <199805211410.HAA00844@feral.com> To: freebsd-scsi@FreeBSD.ORG, gkoller@cs.vu.nl Subject: Re: Defect list (camcontrol) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You didn't say how big the disk was. Used to be that a rule of thumb was at least 1-2% defective sectors. You do the math about how many sectors this actually turns out to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 07:32:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15985 for freebsd-scsi-outgoing; Thu, 21 May 1998 07:32:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA15954 for ; Thu, 21 May 1998 07:32:37 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 2283 invoked by uid 1001); 21 May 1998 14:32:34 +0000 (GMT) To: gkoller@cs.vu.nl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Defect list (camcontrol) In-Reply-To: Your message of "Thu, 21 May 1998 15:24:45 +0200 (MET DST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 21 May 1998 16:32:34 +0200 Message-ID: <2281.895761154@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > $ camcontrol -d -f phys > Got 239 defects. > > This seems to be a little to much. I had expected a few remapped blocks > but not 239! Is this something I should worry about? If these defects include the defects that came with the disk from the manufacturer, you shouldn't be surprised. I remember when working with SunOS and the format program there that it wasn't unusual to see a new disk with a "manufacturer's defect list" which contained between 50 and 200 defects, depending on the size of the disk. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 08:20:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23052 for freebsd-scsi-outgoing; Thu, 21 May 1998 08:20:35 -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 IAA23045 for ; Thu, 21 May 1998 08:20:33 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA04286; Thu, 21 May 1998 09:20:09 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805211520.JAA04286@panzer.plutotech.com> Subject: Re: Defect list (camcontrol) In-Reply-To: <2281.895761154@verdi.nethelp.no> from "sthaug@nethelp.no" at "May 21, 98 04:32:34 pm" To: sthaug@nethelp.no Date: Thu, 21 May 1998 09:20:09 -0600 (MDT) Cc: gkoller@cs.vu.nl, 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 sthaug@nethelp.no wrote... > > $ camcontrol -d -f phys > > Got 239 defects. > > > > This seems to be a little to much. I had expected a few remapped blocks > > but not 239! Is this something I should worry about? > > If these defects include the defects that came with the disk from the > manufacturer, you shouldn't be surprised. I remember when working with > SunOS and the format program there that it wasn't unusual to see a new > disk with a "manufacturer's defect list" which contained between 50 and > 200 defects, depending on the size of the disk. With the above arguments, camcontrol will give you a count of all defects, both PLIST and GLIST. The thing to watch is the GLIST, or grown defect list, since it can change. The PLIST is set at the factory, and doesn't change. One thing I've though of doing is setting up a cron job that runs nightly and looks at the GLIST to see if it is any different than it was the day before. That might be an interesting way to detect when a disk starts to go bad. To get just the GLIST, you'd do something like: camcontrol -dG -f block -u 2 That would get the grown defect list in block format (if block format is supported) for da2. If the specified format isn't supported, camcontrol will display whatever format the drive sends back. If you haven't already seen it, there is a little program (awre.c) that is on the ftp sites along with the CAM distribution that will show whether auto read and write reallocation are turned on for a given disk. You can then use it to turn on read and write reallocation if they aren't already on. I considered making it part of camcontrol, but I decided not to since I intend to eventually add the ability to edit and display arbitrary mode pages, like the current scsi(8) utility. 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 21 09:27:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03585 for freebsd-scsi-outgoing; Thu, 21 May 1998 09:27:56 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fly.HiWAAY.net (dkelly@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03570 for ; Thu, 21 May 1998 09:27:52 -0700 (PDT) (envelope-from dkelly@fly.HiWAAY.net) Received: (from dkelly@localhost) by fly.HiWAAY.net (8.8.8/8.8.6) id LAA26140; Thu, 21 May 1998 11:27:52 -0500 (CDT) Date: Thu, 21 May 1998 11:27:52 -0500 (CDT) From: David Kelly Message-Id: <199805211627.LAA26140@fly.HiWAAY.net> To: freebsd-scsi@FreeBSD.ORG, gkoller@cs.vu.nl Subject: Re: Defect list (camcontrol) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guido Kollerie writes: > > $ camcontrol -d -f phys > Got 239 defects. > > This seems to be a little to much. I had expected a few remapped blocks > but not 239! Is this something I should worry about? Not if they are factory defects. If they are grown defects then its time to worry. As a part of our standard procedures at work we print the defect list of each drive, by "manufacturer's" and "grown", prior to turning it over to users. 50 defects is normal-to-low. 200 is about average. 700 to 1000 is not unusual. All in the manufacturer's defect list. The exception was Conner SCSI HD's. Was convinced the firmware was lying because I never saw a Conner SCSI HD that would admit to having bad blocks from the factory. A quick check of systems shows 426 factory defects on the 4G IBM drive shipped OEM on the SGI O2 behind me. You know the drive maintains a bunch of spares? Am not sure how many. Remapped defects do not subtract from the drive's total capacity. At least not until the spares run out. And by then the drive is ready for the scrap pile. -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== 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 Thu May 21 10:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22012 for freebsd-scsi-outgoing; Thu, 21 May 1998 10:51:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22007; Thu, 21 May 1998 10:51:23 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0ycZ0T-0004HR-00; Thu, 21 May 1998 10:19:53 -0700 Date: Thu, 21 May 1998 10:19:53 -0700 (PDT) From: Tom To: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: DPT install problem 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 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? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 10:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22730 for freebsd-scsi-outgoing; Thu, 21 May 1998 10:55:17 -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 KAA22692 for ; Thu, 21 May 1998 10:55:00 -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 LAA18789 for ; Thu, 21 May 1998 11:54:57 -0600 (MDT) Message-Id: <199805211754.LAA18789@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG Subject: CAM 980520 snapshot now available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 May 1998 11:50:47 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The latest snapshot of the CAM SCSI layer is now available in the usual places: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam ftp://ftp.kdm.org/pub/FreeBSD/cam This snapshot is in tar file format which should ease the burden in applying it over a previous snapshot. >From the README: Changes for the 980520 Snapshot: - Systat/vmstat/iostat cleanup. Device statistic routines are now encapsulated in the devstat library. The devstat library and the utilities that use it handle device arrival and departure events dynamically. - rpc.rstatd now uses the devstat code. Not that rup and friends make use of the disk statistics anyway. - Fixed a few error recovery problems in the aic7xxx driver. - Fixed a bug in xpt_freeze_simq and xpt_freeze_devq that caused the BusLogic timeout routine to panic. - Added quirk support to supress the retreival of serial numbers from devices. This may be needed for some revisions of the Toshiba 3401. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 13:41:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23895 for freebsd-scsi-outgoing; Thu, 21 May 1998 13:41:47 -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 NAA23883 for ; Thu, 21 May 1998 13:41:40 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id OAA05585; Thu, 21 May 1998 14:41:30 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805212041.OAA05585@panzer.plutotech.com> Subject: Re: Tape driver - What do we really want? In-Reply-To: from Hans Huebner at "May 19, 98 09:29:18 am" To: hans@artcom.de (Hans Huebner) Date: Thu, 21 May 1998 14:41:29 -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 Hans Huebner wrote... [ sorry it took so long to reply. I'm including your entire message in my reply since I haven't seen it come across the scsi list yet ] > having thought about the tape subsystem for some time, I'm now trying to > make up my mind on the changes which would be desireable. I will add most > of the functionality suggested here to the CAM tape subsystem in the near > future. > > Please comment on or add to my list, if you feel the need: > > > * Fast locate support > > There should be a MTLOCATE operation in MTIOCOP which locates a given > block address with the SCSI LOCATE command. This raises the question on > how to interpret the data returned by the READ POSITION command (which > would be used in MTIOCGET). The SCSI-2 draft specifies a reply format > which is different from what the DLT and DDS2 drives I have support. The > specification says that block addresses are two bytes long, which is > obviously too short. Would we default to the modern format (four bytes > for block addresses), or would we want to have quirks for drives which do > not adhere to SCSI-2? Well, my copy of the SCSI-2 spec says that the block addresses are 4 bytes long. My guess is that you have the same copy of it, or something similar. Look carefully at the byte numbers in the left hand column of the read position data format diagram. The locate idea is a good one, though. > A new mt subcommand, say 'seek', will be needed to locate a block position > using the new MTIOCOP operation. Sure, that sounds like a good idea. > * Implement MTIOCGET fully > > In particular, the current position should be read and returned (as > discussed above). Yeah, sounds good. 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,t hough. > * Make 'mt status' print only the status > > Currently, 'mt status' prints the status and the permissible compression > modes. This is not quite what I'd expect. I'd want to make 'mt status' > output the current file number, block position (if available), > block size, compression mode and a description of the current position (at > BOT, at EOT, at File Mark, not at file mark). The current CAM mt command doesn't print out permissible compression modes, it prints out the current compression mode. It prints out either the compression algorithm (IDRC, DCLZ, etc.) in use, "disabled", or "unsupported". I would like to see 'mt status' continue to print out the density information. That can be useful at times. > As it has been discussed in freebsd-scsi, the block size of the tape can > only be determined by reading a block from the tape. Also, this number is > valid only for the current block, as the block size may change on tape. > Nevertheless, such a feature would be useful since most tapes are blocked > at a fixed block size, and all the user wants is to know what option to > specify to tar/cpio/restore/dd or whatever. Yes, that would be useful. > * 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. > While we are at it: I also think that having a more elaborate > configuration for individual tape drives' capabilities would be > desireable. As of now, FreeBSD/CAM is kind of 'naive' with respect to > SCSI tape drives, and uses only the least common denominator of the > capabilities individual tape drives have. What comes to mind are > > - Default block sizes for different types of drives > - List of supported SCSI features (LOCATE support, compression etc.) > - Timeouts for various operations (then again, maybe not) I'm not sure adjustable timeouts are entirely necessary. It could be done, but I'm not sure how often people run into the situation that the default timeout is too short. > * 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? > I'd strive for simplicity, of course. But then again, some features would > really be helpful. Keep in mind that I am working on the CAM driver, not > the old SCSI stuff. The locate and read position support would definitely be helpful. You may want to take a look at the NetBSD implementations of those. 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 21 17:08:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05319 for freebsd-scsi-outgoing; Thu, 21 May 1998 17:08:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from colossus.dyn.ml.org (199-170-160-140.la.inreach.net [199.107.160.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05221 for ; Thu, 21 May 1998 17:07:51 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id RAA00257; Thu, 21 May 1998 17:06:56 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.2.p0.FreeBSD:980521170655:29525=_" In-Reply-To: <35600E72.504CE9E4@elr346.ateng.az.honeywell.com> Date: Thu, 21 May 1998 17:06:55 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Emmanuel Gravel Subject: RE: Jaz or SyJet as backup drive Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format --_=XFMail.1.2.p0.FreeBSD:980521170655:29525=_ Content-Type: text/plain; charset=us-ascii -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 18-May-98, Emmanuel Gravel wrote: > Has anyone used a Jaz or SyJet drive as a backup device (instead of > a tape drive)? This is an option I'm considering, understanding the > lowering costs of both drive and media of these devices, and the > close-to-harddrive speeds they have. I'm wondering if the software > can use them effectively. I've been using a Jaz drive for a while as my backup media. It works pretty well. I've hacked together a custom backup script that I use, that does compressed backups using dump. I'm including it here (since it is fairly small) so that yourself (and others) may find some use for it. It shouldn't require much modification, and I believe that I put comments in to indicate where modification might be needed for your local setup. Feel free to contact me with any questions, and enjoy! - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWTBn/jpixuAwagxAQGsEwP/U51xbnHqeKAebiHjxP7hXbSncOgUzMnt qy6WrfMZmFaIsPoNbyjaZr78jzU97XAUGE7V5pWDuFgysfFNGTAaMmkgGGAeLZnh 3QnEzqmmiQ7HK1OdFTmew25nMotpDMBhyD5AevXbHmC3ViVDAeUT2A1K+S/NWKDl N1jlrrclfYM= =xhQJ -----END PGP SIGNATURE----- --_=XFMail.1.2.p0.FreeBSD:980521170655:29525=_ Content-Disposition: attachment; filename="dobackup" Content-Transfer-Encoding: 7bit Content-Description: my backup script Content-Type: text/plain; charset=us-ascii; name=dobackup; SizeOnDisk=2908 #!/bin/sh ### CONFIGURATION SECTION # Backup DOS files? BACKUPDOSFILES="NO" # What file(s)/dir(s) in the DOS partition do you want to backup? # (specify paths relative to /dos) # DFILES="config.sys autoexec.bat arcade local/*.bat progra~1/quicken/donald.* " DFILES="config.sys autoexec.bat local/*.bat" # Where do you want to put the backup file? It will be named # "dos.tar.gz" and will be located at this directory. DFILELOC="/usr" ### END OF CONFIGURATION SECTION if [ -f /tmp/dobackup.lock ] then echo -n "Hmm, another dobackup process seems to be running. " PID=`cat /tmp/dobackup.lock` echo "(pid=${PID})" echo "You can't run more than one at a time!" echo "(Note: if this is incorrect, rm the file /tmp/dobackup.lock)" exit 1 fi echo $$ > /tmp/dobackup.lock echo "Starting the weekly backup cycle." echo "" echo "NOTE: This will work better if you have the machine in single-user mode." echo " But this is not a requirement." echo "" if [ x"${BACKUPDOSFILES}" = x"YES" ] then if [ ! -d "${DFILELOC}" ] then echo "ERROR: ${DFILELOC} does not exist and can't be used as the" echo " location for the DOS backup files. Re-edit this script" echo " and take a look at the definition of DFILELOC, and be" echo " sure that that directory exists!" rm -f /tmp/dobackup.lock exit 1 fi echo -n "Backing up the DOS files..." cd /dos tar czf ${DFILELOC}/dos.tar.gz ${DFILES} > /tmp/dos-backup.log 2>&1 if [ $? -ne 0 ] then echo "ERROR" echo "" echo "ERROR: backup failed for some reason. Take a look at the log" echo " file /tmp/dos-backup.log for more details." rm -f /tmp/dobackup.lock exit 1 fi echo "done" echo "" rm -f /tmp/dos-backup.log else echo "Skipping backup of DOS files." echo "" fi if ! df | grep "\/jaz$" > /dev/null 2>&1 then echo "WARNING: The backup device is not mounted. Please mount it" echo " before proceeding." rm -f /tmp/dobackup.lock exit 1 fi echo -n "Removing old backups..." rm -f /jaz/*.dgz echo "done." echo "" for FSYS in / /usr /usr/local /var /var/news /home do if [ "X${FSYS}" = "X/" ] then BKUPFILE="root" else BKUPFILE="`echo ${FSYS} | sed 's/\///g'`" fi BKUPFILE="/jaz/${BKUPFILE}.dgz" echo "Now backing up ${FSYS} as ${BKUPFILE}..." DUMPCMD="dump -0au -f - ${FSYS}" echo "Running: ${DUMPCMD} | gzip -9 > ${BKUPFILE}" echo "" ${DUMPCMD} | gzip -9 > ${BKUPFILE} if [ $? -eq 0 ] then echo "" echo "Dump finished with NO errors." echo "" echo "Ready to proceed with next dump." echo "" else echo "" echo "*** THERE WAS (WERE) AN ERROR(S) IN THE DUMP!! ***" echo "PLEASE DO NOT PROCEED UNTIL ERRORS HAVE BEEN CORRECTED." echo "THIS SCRIPT WILL NOW TERMINATE." rm -f /tmp/dobackup.lock rm -f ${DFILELOC}/dos.tar.gz exit 1 fi done echo "All dumps are complete." echo "" echo "See you next week!" rm -f /tmp/dobackup.lock rm -f ${DFILELOC}/dos.tar.gz exit 0 --_=XFMail.1.2.p0.FreeBSD:980521170655:29525=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 17:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10317 for freebsd-scsi-outgoing; Thu, 21 May 1998 17:29:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10296 for ; Thu, 21 May 1998 17:29:26 -0700 (PDT) (envelope-from hans@artcom.de) Received: from transrapid.artcom.de by mail.artcom.de with smtp id m0ycfi2-00023xC; Fri, 22 May 1998 00:29:18 +0000 (GMT) Date: Fri, 22 May 1998 02:29:17 +0200 (CEST) From: Hans Huebner Reply-To: Hans Huebner To: "Kenneth D. Merry" cc: gibbs@pluto.plutotech.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver - What do we really want? In-Reply-To: <199805212041.OAA05585@panzer.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 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. > > * 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. > > * 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'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). This is off-topic anyway ;) -Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 22:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08187 for freebsd-scsi-outgoing; Thu, 21 May 1998 22:37:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08179 for ; Thu, 21 May 1998 22:37:37 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by keg.cs.vu.nl with smtp (Smail3.1.28.1 #48) id m0yckWJ-0007CRC; Fri, 22 May 98 07:37 +0200 Date: Fri, 22 May 1998 07:37:30 +0200 (MET DST) From: Guido Kollerie To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Defect list (camcontrol) In-Reply-To: <199805211520.JAA04286@panzer.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 On Thu, 21 May 1998, Kenneth D. Merry wrote: Thanks to everyone who responded. I didn't know all disks came with a preset defect list (except for Conner disks, that is ;-) > One thing I've though of doing is setting up a cron job that runs > nightly and looks at the GLIST to see if it is any different than it was > the day before. That might be an interesting way to detect when a disk > starts to go bad. To get just the GLIST, you'd do something like: > > camcontrol -dG -f block -u 2 substituting 0 for 2, I get: Got 1 defect: 1469561 That's a number I can live with. For those that were interested in what kind of a disk I was refering to: Fujitsu M-2954-QUA (fast-wide scsi, 2.3 GB) -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 22:50:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10889 for freebsd-scsi-outgoing; Thu, 21 May 1998 22:50:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10884 for ; Thu, 21 May 1998 22:50:50 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by keg.cs.vu.nl with smtp (Smail3.1.28.1 #48) id m0yckj4-0007CRC; Fri, 22 May 98 07:50 +0200 Date: Fri, 22 May 1998 07:50:42 +0200 (MET DST) From: Guido Kollerie To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Defect list (camcontrol) 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 Fri, 22 May 1998, Guido Kollerie wrote: > > camcontrol -dG -f block -u 2 > > substituting 0 for 2, I get: > Got 1 defect: > 1469561 > > That's a number I can live with. For those that were interested in what > kind of a disk I was refering to: Fujitsu M-2954-QUA (fast-wide scsi, 2.3 > GB) I meant M-2952-QUA. The M-2954-QUA is the 4.x GB version! ^ ^ -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 21 23:10:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14527 for freebsd-scsi-outgoing; Thu, 21 May 1998 23:10:08 -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 XAA14413 for ; Thu, 21 May 1998 23:10:00 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA10857; Fri, 22 May 1998 15:39:57 +0930 (CST) (envelope-from grog) Message-ID: <19980522153956.K27201@freebie.lemis.com> Date: Fri, 22 May 1998 15:39:56 +0930 From: Greg Lehey To: Guido Kollerie , freebsd-scsi@FreeBSD.ORG Subject: Re: CAM performance on -stable References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Guido Kollerie on Thu, May 21, 1998 at 11:34:26AM +0200 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, 21 May 1998 at 11:34:26 +0200, Guido Kollerie wrote: > To get an indication of the perfomance of CAM I have performed three make > -j4 buildworld's. Once with the non-CAM kernel and twice with the CAM > kernel. /usr was mounted async,noatime and I used -O -pipe > -DCAM_OLD_TIMEOUT for CFLAGS, NOPROFILE was true > > To my surprise all the three buildworld times were nearly identical (3hr > 9min +/- 1min). I had expected the CAM kernel to perform much better as it > allows my BT-958 to use Command Tagged Queueing were as the non-CAM kernel > did not. > > Has anyone else found similar results on a -stable system? No, but I'd expect it. Make world doesn't really stress the SCSI system, since it doesn't handle more than one process at a time (well, not in a UP system, anyway). You'll see a lot more improvement if you use soft updates or async. 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 Fri May 22 10:08:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26805 for freebsd-scsi-outgoing; Fri, 22 May 1998 10:08:29 -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 KAA26796 for ; Fri, 22 May 1998 10:08:27 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 28248 invoked by uid 1000); 22 May 1998 18:09:43 -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: Fri, 22 May 1998 14:09:43 -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-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 --- 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 22 11:13:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10477 for freebsd-scsi-outgoing; Fri, 22 May 1998 11:13:41 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10430; Fri, 22 May 1998 11:13:29 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0ycvpD-0005GX-00; Fri, 22 May 1998 10:41:47 -0700 Date: Fri, 22 May 1998 10:41:41 -0700 (PDT) From: Tom To: Simon Shapiro cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG 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 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. 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. > Simon Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 12:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27428 for freebsd-scsi-outgoing; Fri, 22 May 1998 12:30:42 -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 MAA27414; Fri, 22 May 1998 12:30:36 -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 LAA01141; Fri, 22 May 1998 11:24:54 -0700 (PDT) Message-Id: <199805221824.LAA01141@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: Simon Shapiro , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Fri, 22 May 1998 10:41:41 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 May 1998 11:24:54 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > 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. New users are less than likely to be presented with such a situation. 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. -- \\ 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 Fri May 22 12:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27606 for freebsd-scsi-outgoing; Fri, 22 May 1998 12:31:22 -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 MAA27579; Fri, 22 May 1998 12:31:18 -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 TAA29158; Fri, 22 May 1998 19:31:16 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA01841; Fri, 22 May 1998 21:31:12 +0200 (MET DST) Message-ID: <19980522213111.03467@follo.net> Date: Fri, 22 May 1998 21:31:11 +0200 From: Eivind Eklund To: Tom , Simon Shapiro Cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@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 Tom on Fri, May 22, 1998 at 10:41:41AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. 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. 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 22 12:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03019 for freebsd-scsi-outgoing; Fri, 22 May 1998 12:51:19 -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 MAA02972; Fri, 22 May 1998 12:51:01 -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 PAA21467; Fri, 22 May 1998 15:42:48 -0400 (EDT) Date: Fri, 22 May 1998 15:42:48 -0400 (EDT) From: Charles Owens To: Simon Shapiro cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG 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 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 From owner-freebsd-scsi Fri May 22 14:38:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23660 for freebsd-scsi-outgoing; Fri, 22 May 1998 14:38:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23477; Fri, 22 May 1998 14:38:00 -0700 (PDT) (envelope-from rzig@verio.net) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Fri, 22 May 1998 16:36:57 -0500 Message-ID: From: Raul Zighelboim To: "'Charles Owens'" , Simon Shapiro Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: RE: DPT install problem Date: Fri, 22 May 1998 16:36:56 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. 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). Thanks, Simon, for a job well done. ================================================== 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 16:22:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12437 for freebsd-scsi-outgoing; Fri, 22 May 1998 16:22:27 -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 QAA12432 for ; Fri, 22 May 1998 16:22:25 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4153 invoked by uid 1000); 23 May 1998 00:23:33 -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: <199805221824.LAA01141@dingo.cdrom.com> Date: Fri, 22 May 1998 20:23:33 -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 22-May-98 Mike Smith wrote: >> >> >> 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. > > New users are less than likely to be presented with such a situation. > > 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. I will add this sort of test to my regression testing. But, as I said, I mostly test on 3.0-current and do not see this problem there. 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: swapon -a if [ $1x = autobootx ]; then echo Automatic reboot in progress... + ulimit -t unlimited + ulimit -f unlimited + ulimit -d unlimited + ulimit -s unlimited + ulimit -c unlimited + ulimit -m unlimited + ulimit -l unlimited fsck -p This (or its equivalent) may remove the problem from sysinstall. 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 22 16:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12962 for freebsd-scsi-outgoing; Fri, 22 May 1998 16:24:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12826; Fri, 22 May 1998 16:24:24 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yd1AG-00034H-00; Fri, 22 May 1998 16:23:52 -0700 Date: Fri, 22 May 1998 16:23:48 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Raul Zighelboim cc: "'Charles Owens'" , Simon Shapiro , Tom , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG 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 Fri, 22 May 1998, 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. Yes. The DPT problem is related to sysinstall. If I newfs afterwards, everythings works ok. > 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). That would not be a good idea, as the controller caches by the stripe. So a 32MB stripe would allow you to cache only two stripes. It also depends on what RAID level you are using. You probably wouldn't see any benefit beyond 1MB stripes anyhow. > Thanks, Simon, for a job well done. > > ================================================== > Raul Zighelboim rzig@verio.net Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 16:27:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13472 for freebsd-scsi-outgoing; Fri, 22 May 1998 16:27:45 -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 QAA13405; Fri, 22 May 1998 16:27:26 -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 PAA02816; Fri, 22 May 1998 15:21:58 -0700 (PDT) Message-Id: <199805222221.PAA02816@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: Re: DPT install problem In-reply-to: Your message of "Fri, 22 May 1998 20:23:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 May 1998 15:21:57 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > 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? > 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? (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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 16:27:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13522 for freebsd-scsi-outgoing; Fri, 22 May 1998 16:27:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA13464; Fri, 22 May 1998 16:27:44 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yd0jL-0005Ui-00; Fri, 22 May 1998 15:56:03 -0700 Date: Fri, 22 May 1998 15:55:54 -0700 (PDT) From: Tom To: Charles Owens cc: Simon Shapiro , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG 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 Fri, 22 May 1998, Charles Owens wrote: > 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? It is a sysinstall problem. When bootstrapinng 2.2 onto your system, leave most of the array unallocated, and disklabel and newfs it later. > 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) Use good enclosures. > Thanks, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 16:36:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15868 for freebsd-scsi-outgoing; Fri, 22 May 1998 16:36:45 -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 QAA15814 for ; Fri, 22 May 1998 16:36:39 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4465 invoked by uid 1000); 23 May 1998 00:37: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: Fri, 22 May 1998 20:37: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: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-May-98 Charles Owens wrote: > 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? Relax. It is not so bad. Here is what you do: a. Install your core system, avoiding any single file system (slice) larger than about 4GB. b. Boot the system and use disklabel -e, etc. to create the really large filesystems. c. Modify /etc/rc as per my previous post. d. Call me if there are any more problems. > 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) Yes. Fsck on such a filesystem is a bit slower. Not too many people actually tested the filesystem code, overflowing 32bit addresses. Backup of such a partition may be interesting too. > > 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 > ------------------------------------------------------------------------- > --- 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 22 18:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04880 for freebsd-scsi-outgoing; Fri, 22 May 1998 18:13:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA04843; Fri, 22 May 1998 18:13:13 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yd2NP-0005a4-00; Fri, 22 May 1998 17:41:31 -0700 Date: Fri, 22 May 1998 17:41:23 -0700 (PDT) From: Tom To: Eivind Eklund cc: Simon Shapiro , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-Reply-To: <19980522213111.03467@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 22 19:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17730 for freebsd-scsi-outgoing; Fri, 22 May 1998 19:41:41 -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 TAA17699; Fri, 22 May 1998 19:41:36 -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 CAA09295; Sat, 23 May 1998 02:41:31 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id EAA08195; Sat, 23 May 1998 04:41:24 +0200 (MET DST) Message-ID: <19980523044124.39393@follo.net> Date: Sat, 23 May 1998 04:41:24 +0200 From: Eivind Eklund To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: DPT install problem References: <199805222221.PAA02816@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805222221.PAA02816@dingo.cdrom.com>; from Mike Smith on Fri, May 22, 1998 at 03:21:57PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 22, 1998 at 03:21:57PM -0700, Mike Smith wrote: > > 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? My feedback is mainly that I don't have 20GB of diskspace, and (probably) won't have for quite some time. I'll be glad to do testing when I have. However, it is more likely that I can put together a truckload of IDE disks as a RAID-0 than a 20GB DPT array; I have exactly two wide SCSI-II disks (the ones I got with the DPT from Simon, to be able to do local 'make release' instead of occupying his machine). 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). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 23 08:00:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25439 for freebsd-scsi-outgoing; Sat, 23 May 1998 08:00:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles219.castles.com [208.214.165.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25375; Sat, 23 May 1998 07:59:57 -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 GAA00401; Sat, 23 May 1998 06:55:46 -0700 (PDT) Message-Id: <199805231355.GAA00401@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: Eivind Eklund , Simon Shapiro , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-reply-to: Your message of "Fri, 22 May 1998 17:41:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 May 1998 06:55:45 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > 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. ftp://releng22.freebsd.org/pub/FreeBSD/2.2-980511-SNAP > 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. What's on the debug console? Have you wound the debugging up? -- \\ 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