From owner-freebsd-scsi Sun Jun 28 20:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28597 for freebsd-scsi-outgoing; Sun, 28 Jun 1998 20:39:08 -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 UAA28590 for ; Sun, 28 Jun 1998 20:39:06 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id VAA17195 for scsi@freebsd.org; Sun, 28 Jun 1998 21:39:04 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199806290339.VAA17195@panzer.plutotech.com> Subject: xmcd-2.3 patches/port for CAM To: scsi@FreeBSD.ORG Date: Sun, 28 Jun 1998 21:39:04 -0600 (MDT) 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 For those CAM users who are interested, I have ported XMCD 2.3 to CAM. Right now, I have just made a port and a patch available. If anyone is interested (i.e. people without Motif), I can upload a version of it with the binaries statically linked with the Motif when the next CAM snapshot comes out. (I don't want to do it now, just in case any subtle incompatibilities, like the change in the definition of the ioctl syscall, cause it to break for the current CAM snapshot.) Anyway, here are the URLs: This is the port: ftp://ftp.kdm.org/pub/FreeBSD/cam/xmcd-2.3.cam-port.980628.tar.gz This is the patch: ftp://ftp.kdm.org/pub/FreeBSD/cam/xmcd-2.3.cam_patch.980628 The port basically consists of the xmcd port from -current with the above patch copied into the patches directory as 'patch-ad'. The patch makes the xmcd build/configure process automatically detect a CAM system and configure itself accordingly. (it detects a "CAM" system by looking for /usr/include/camlib.h) If anyone has any questions, problems, comments, etc., let me know. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 29 01:37:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03789 for freebsd-scsi-outgoing; Mon, 29 Jun 1998 01:37:26 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03771; Mon, 29 Jun 1998 01:37:13 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id JAA27562; Mon, 29 Jun 1998 09:36:52 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id JAA05111; Mon, 29 Jun 1998 09:36:31 +0100 (BST) Message-ID: <19980629093631.60284@iii.co.uk> Date: Mon, 29 Jun 1998 09:36:31 +0100 To: Stefan Esser Cc: Doug Russell , stable@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Make world failures (ncr wierdness?) References: <19980627151834.05015@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <19980627151834.05015@mi.uni-koeln.de>; from Stefan Esser on Sat, Jun 27, 1998 at 03:18:34PM +0200 Organization: interactive investor Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ cc'd to -scsi ] On Sat, Jun 27, 1998 at 03:18:34PM +0200, Stefan Esser wrote: > > Jun 26 10:19:46 doug /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > > Jun 26 10:19:46 doug /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f05a9800. > > This is your drive complaining about too many simultanous commands. > Some drives support varying numbers of tags depending on parameters > we have no control over, some have firmware bugs and can't even deal > with 2 tagged commands at times. IIRC, then the LXY4 revision of the > Quantum Atlas II firmware is known to cause such problems. You may > want to upgrade to a later revision (available from the Quantum FTP > server at ftp://ftp.qntm.com/pub/support/Firmware). The upgrade can > be performed from a DOS floppy with ASPI drivers for SDMS (came with > your NCR card). Not having easy access to a machine running DOS, this is a bit tricky for me to do. Would anyone be kind enough to build a floppy image with the right files on and make it available for FTP? N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 29 10:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00542 for freebsd-scsi-outgoing; Mon, 29 Jun 1998 10:52:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00452 for ; Mon, 29 Jun 1998 10:52:15 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (rtc103.reseau.uvsq.fr [193.51.24.19]) by soleil.uvsq.fr (8.8.8/jtpda-5.3) with ESMTP id TAA01167 for ; Mon, 29 Jun 1998 19:52:06 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.8/8.8.5) id TAA09055; Fri, 26 Jun 1998 19:34:07 GMT Message-ID: <19980626193021.49222@breizh.prism.uvsq.fr> Date: Fri, 26 Jun 1998 19:30:21 +0000 From: Nicolas Souchu To: freebsd-scsi@FreeBSD.ORG Subject: scsi errors (7880 + IBM DCAS32160) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi scsi team, Errors occured on my -current box (from 98.06.16)... The context: compiling kde with cpp1plus, netscape running, swaping (25%) I had no seach errors with CAM from 98.04.13. Now the SCSI stack is the old SCSI2 dated Jun 16 (needed for ppbus and ZIP support). The SCSI controller is configured "Wide disabled, 10MHz sync for the IBM disk" The problems seem to appear only under heavy load. Any test I could do to help? Thanks in advance. Here is the config: Jun 22 18:44:15 breizh /kernel: Probing for devices on PCI bus 0: Jun 22 18:44:15 breizh /kernel: chip0: rev 0x02 on pci0.0.0 Jun 22 18:44:15 breizh /kernel: chip1: rev 0x0 1 on pci0.7.0 Jun 22 18:44:15 breizh /kernel: ide_pci0: rev 0x00 on pci0.7.1 Jun 22 18:44:15 breizh /kernel: ahc0: rev 0x00 int a irq 9 on pci0.9.0 Jun 22 18:44:15 breizh /kernel: ahc0: Using left over BIOS settings Jun 22 18:44:15 breizh /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs Jun 22 18:44:15 breizh /kernel: ahc0: waiting for scsi devices to settle Jun 22 18:44:15 breizh /kernel: scbus0 at ahc0 bus 0 Jun 22 18:44:15 breizh /kernel: sd0 at scbus0 target 6 lun 0 Jun 22 18:44:15 breizh /kernel: sd0: type 0 fixed SCSI 2 Jun 22 18:44:15 breizh /kernel: sd0: Direct-Access 2063MB (4226725 512 byte sect ors) Here are the errors: sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x121 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: abort message in message buffer sd0: SCB 0x1 timedout while recovery in progress sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x122 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 sd0: SCB 0x1 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x122 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: abort message in message buffer sd0: SCB 0x0 timedout while recovery in progress sd0: SCB 0x1 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x121 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x121 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: abort message in message buffer sd0: SCB 0x1 timedout while recovery in progress sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x121 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 swap_pager: indefinite wait buffer: device: 0x20401, blkno: 59008, size: 65536 sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x121 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: abort message in message buffer sd0: SCB 0x1 timedout while recovery in progress sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x122 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:1 sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x122 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: abort message in message buffer sd0: SCB 0x1 timedout while recovery in progress sd0: SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x122 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x3 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted swap_pager: I/O error - pagein failed; blkno 59008, size 65536, error 5 vm_fault: pager input (probably hardware) error, PID 1043 failure sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:4 -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 30 01:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03060 for freebsd-scsi-outgoing; Tue, 30 Jun 1998 01:29:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from casimir.easynet.fr (casimir.easynet.fr [195.114.64.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03053 for ; Tue, 30 Jun 1998 01:29:19 -0700 (PDT) (envelope-from rama@casimir.easynet.fr) Received: (from rama@localhost) by casimir.easynet.fr (8.8.8/8.8.8) id KAA03294; Tue, 30 Jun 1998 10:28:04 +0200 (CEST) (envelope-from rama) Message-ID: <19980630102804.A3257@easynet.fr> Date: Tue, 30 Jun 1998 10:28:04 +0200 From: David Ramahefason To: shimon@simon-shapiro.org, FreeBSD-SCSI@FreeBSD.ORG Subject: DPT Install big problem Reply-To: David Ramahefason References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8 In-Reply-To: ; from Simon Shapiro on Wed, Jun 24, 1998 at 11:55:07AM -0400 Organization: Systems Team Easynet France SA X-Operating-System: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. The dptmgr create all the array without any problem... But when we start to install FreeBSD, the card hangs during the filesystem creation.... with LED 1 on... I've called DPT to have some advice... but the only thing they told me was to lower the xfer rate on the SCSI bios. I've lowered it to 5Mhz.. it didn't change anything. We've tryied to install Redhat, and it worked... Do we have to do special things to have the DPT system working under FreeBSD (which is want we really want) Thanks -- /David Ramahefason Administrateur Systeme/Reseau/ /rama@easynet.fr Easynet France SA / /0144547031 ICQ: 14292822 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 30 08:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13461 for freebsd-scsi-outgoing; Tue, 30 Jun 1998 08:59:19 -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 IAA13455 for ; Tue, 30 Jun 1998 08:59:14 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yr2IJ-0006v5-00; Tue, 30 Jun 1998 08:26:07 -0700 Date: Tue, 30 Jun 1998 08:25:58 -0700 (PDT) From: Tom To: David Ramahefason cc: shimon@simon-shapiro.org, FreeBSD-SCSI@FreeBSD.ORG Subject: Re: DPT Install big problem In-Reply-To: <19980630102804.A3257@easynet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 30 Jun 1998, David Ramahefason wrote: > Hi, > > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. > The dptmgr create all the array without any problem... > But when we start to install FreeBSD, the card hangs during > the filesystem creation.... with LED 1 on... Old problem. Discussed here before, many times. sysinstall/newfs is a bit broken. Leave most of the array unallocated, and sysinstall will complete ok. newfs it later. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 30 09:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20224 for freebsd-scsi-outgoing; Tue, 30 Jun 1998 09:44:27 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from casimir.easynet.fr (casimir.easynet.fr [195.114.64.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20218 for ; Tue, 30 Jun 1998 09:44:24 -0700 (PDT) (envelope-from rama@casimir.easynet.fr) Received: (from rama@localhost) by casimir.easynet.fr (8.8.8/8.8.8) id SAA07991; Tue, 30 Jun 1998 18:43:28 +0200 (CEST) (envelope-from rama) Message-ID: <19980630184328.A7822@easynet.fr> Date: Tue, 30 Jun 1998 18:43:28 +0200 From: David Ramahefason To: Tom Cc: shimon@simon-shapiro.org, FreeBSD-SCSI@FreeBSD.ORG Subject: Re: DPT Install big problem Reply-To: David Ramahefason References: <19980630102804.A3257@easynet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8 In-Reply-To: ; from Tom on Tue, Jun 30, 1998 at 08:25:58AM -0700 Organization: Systems Team Easynet France SA X-Operating-System: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 30, 1998 at 08:25:58AM -0700, Tom wrote: > > On Tue, 30 Jun 1998, David Ramahefason wrote: > > > Hi, > > > > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. > > The dptmgr create all the array without any problem... > > But when we start to install FreeBSD, the card hangs during > > the filesystem creation.... with LED 1 on... > > Old problem. Discussed here before, many times. sysinstall/newfs is a > bit broken. Leave most of the array unallocated, and sysinstall will > complete ok. newfs it later. Yep but it fails even with a 300M partition.... What are the partition I need to make ?? > > Tom > ---end quoted text--- -- /David Ramahefason Administrateur Systeme/Reseau/ /rama@easynet.fr Easynet France SA / /0144547031 ICQ: 14292822 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 30 09:47:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20581 for freebsd-scsi-outgoing; Tue, 30 Jun 1998 09:47:13 -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 JAA20565 for ; Tue, 30 Jun 1998 09:47:04 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yr32a-0006wb-00; Tue, 30 Jun 1998 09:13:56 -0700 Date: Tue, 30 Jun 1998 09:13:56 -0700 (PDT) From: Tom To: David Ramahefason cc: shimon@simon-shapiro.org, FreeBSD-SCSI@FreeBSD.ORG Subject: Re: DPT Install big problem In-Reply-To: <19980630184328.A7822@easynet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 30 Jun 1998, David Ramahefason wrote: > On Tue, Jun 30, 1998 at 08:25:58AM -0700, Tom wrote: > > > > On Tue, 30 Jun 1998, David Ramahefason wrote: > > > > > Hi, > > > > > > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. > > > The dptmgr create all the array without any problem... > > > But when we start to install FreeBSD, the card hangs during > > > the filesystem creation.... with LED 1 on... > > > > Old problem. Discussed here before, many times. sysinstall/newfs is a > > bit broken. Leave most of the array unallocated, and sysinstall will > > complete ok. newfs it later. > > Yep but it fails even with a 300M partition.... > What are the partition I need to make ?? A 50 /, a 150M /usr should work ok (does here anyhow). Are you sure you are leaving most the the array unallocated? That is the key. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 30 20:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10981 for freebsd-scsi-outgoing; Tue, 30 Jun 1998 20:30:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA10905 for ; Tue, 30 Jun 1998 20:29:59 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 21830 invoked by uid 1000); 1 Jul 1998 03:30:41 -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: <19980630102804.A3257@easynet.fr> Date: Tue, 30 Jun 1998 23:30:41 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: David Ramahefason Subject: RE: DPT Install big problem Cc: FreeBSD-SCSI@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Jun-98 David Ramahefason wrote: > Hi, > > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. > The dptmgr create all the array without any problem... > But when we start to install FreeBSD, the card hangs during > the filesystem creation.... with LED 1 on... > I've called DPT to have some advice... but the only thing > they told me was to lower the xfer rate on the SCSI bios. > I've lowered it to 5Mhz.. it didn't change anything. > We've tryied to install Redhat, and it worked... > Do we have to do special things to have the DPT system > working under FreeBSD (which is want we really want) LED 1 stuck on means the PCI bus is hung, or the DPT is hung on the bus. I need a bit more data: Exact kernel configuration and version Motherboard details DPT firmware and BIOS versions - not the same! Any kernel messages that show during the hang There are some special options to compile for kernels that tax the PCI bus, but let's see what you have first. Simon ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 04:56:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06991 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 04:56:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from casimir.easynet.fr (casimir.easynet.fr [195.114.64.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06978 for ; Wed, 1 Jul 1998 04:56:10 -0700 (PDT) (envelope-from rama@casimir.easynet.fr) Received: (from rama@localhost) by casimir.easynet.fr (8.8.8/8.8.8) id NAA19498; Wed, 1 Jul 1998 13:55:09 +0200 (CEST) (envelope-from rama) Message-ID: <19980701135509.D19385@easynet.fr> Date: Wed, 1 Jul 1998 13:55:09 +0200 From: David Ramahefason To: shimon@simon-shapiro.org Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: DPT Install big problem Reply-To: David Ramahefason References: <19980630102804.A3257@easynet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8 In-Reply-To: ; from Simon Shapiro on Tue, Jun 30, 1998 at 11:30:41PM -0400 Organization: Systems Team Easynet France SA X-Operating-System: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 30, 1998 at 11:30:41PM -0400, Simon Shapiro wrote: > > On 30-Jun-98 David Ramahefason wrote: > > Hi, > > > > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. > > The dptmgr create all the array without any problem... > > But when we start to install FreeBSD, the card hangs during > > the filesystem creation.... with LED 1 on... > > I've called DPT to have some advice... but the only thing > > they told me was to lower the xfer rate on the SCSI bios. > > I've lowered it to 5Mhz.. it didn't change anything. > > We've tryied to install Redhat, and it worked... > > Do we have to do special things to have the DPT system > > working under FreeBSD (which is want we really want) > > LED 1 stuck on means the PCI bus is hung, or the DPT is hung on the bus. > I need a bit more data: > > Exact kernel configuration and version It's the generic kernel with all the DPT options enabled (version 2.2.6) > Motherboard details It's an ASUS P2B-DS > DPT firmware and BIOS versions - not the same! Firmware is 07L0 uhhh the bios... dunno... > Any kernel messages that show during the hang mmm... don't remember exactly... I'll mail when I'll have them > > There are some special options to compile for kernels that tax the PCI bus, > but let's see what you have first. Don't have any options concerning the PCI bus... > > Simon > > ---------- > > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG Voice: 770.265.7340 ---end quoted text--- -- /David Ramahefason Administrateur Systeme/Reseau/ /rama@easynet.fr Easynet France SA / /0144547031 ICQ: 14292822 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 07:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20408 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 07:04:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from casimir.easynet.fr (casimir.easynet.fr [195.114.64.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20402 for ; Wed, 1 Jul 1998 07:04:03 -0700 (PDT) (envelope-from rama@casimir.easynet.fr) Received: (from rama@localhost) by casimir.easynet.fr (8.8.8/8.8.8) id QAA20857; Wed, 1 Jul 1998 16:03:08 +0200 (CEST) (envelope-from rama) Message-ID: <19980701160308.A20825@easynet.fr> Date: Wed, 1 Jul 1998 16:03:08 +0200 From: David Ramahefason To: shimon@simon-shapiro.org Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: DPT Install big problem Reply-To: David Ramahefason References: <19980630102804.A3257@easynet.fr> <19980701135509.D19385@easynet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8 In-Reply-To: <19980701135509.D19385@easynet.fr>; from David Ramahefason on Wed, Jul 01, 1998 at 01:55:09PM +0200 Organization: Systems Team Easynet France SA X-Operating-System: FreeBSD Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > LED 1 stuck on means the PCI bus is hung, or the DPT is hung on the bus. > > I need a bit more data: > > > > Exact kernel configuration and version > > It's the generic kernel with all the DPT options enabled (version 2.2.6) > > > Motherboard details > It's an ASUS P2B-DS > > > DPT firmware and BIOS versions - not the same! > Firmware is 07L0 uhhh the bios... dunno... Bios is 3.E7 > > Any kernel messages that show during the hang > mmm... don't remember exactly... I'll mail when I'll have them Well no it hangs at the fsck... during the boot... no message.. ---end quoted text--- Cheers -- /David Ramahefason Administrateur Systeme/Reseau/ /rama@easynet.fr Easynet France SA / /0144547031 ICQ: 14292822 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 12:52:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09917 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 12:52:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA09906 for ; Wed, 1 Jul 1998 12:52:07 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 8955 invoked by uid 1000); 1 Jul 1998 19:52:42 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980701135509.D19385@easynet.fr> Date: Wed, 01 Jul 1998 15:52:41 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: David Ramahefason Subject: Re: DPT Install big problem Cc: FreeBSD-SCSI@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-Jul-98 David Ramahefason wrote: > On Tue, Jun 30, 1998 at 11:30:41PM -0400, Simon Shapiro wrote: >> >> On 30-Jun-98 David Ramahefason wrote: >> > Hi, >> > >> > We have a 3334UW plus a 7 slot DPT cabinet with hot plus HD. >> > The dptmgr create all the array without any problem... >> > But when we start to install FreeBSD, the card hangs during >> > the filesystem creation.... with LED 1 on... >> > I've called DPT to have some advice... but the only thing >> > they told me was to lower the xfer rate on the SCSI bios. >> > I've lowered it to 5Mhz.. it didn't change anything. >> > We've tryied to install Redhat, and it worked... >> > Do we have to do special things to have the DPT system >> > working under FreeBSD (which is want we really want) >> >> LED 1 stuck on means the PCI bus is hung, or the DPT is hung on the bus. >> I need a bit more data: >> >> Exact kernel configuration and version > > It's the generic kernel with all the DPT options enabled (version 2.2.6) > >> Motherboard details > It's an ASUS P2B-DS > >> DPT firmware and BIOS versions - not the same! > Firmware is 07L0 uhhh the bios... dunno... > >> Any kernel messages that show during the hang > mmm... don't remember exactly... I'll mail when I'll have them >> >> There are some special options to compile for kernels that tax the PCI >> bus, >> but let's see what you have first. > > Don't have any options concerning the PCI bus... Make sure the kernel is compiled with: options DPT_VERIFY_HINTR options DPT_HANDLE_TIMEOUTS options "DPT_TIMEOUT_FACTOR=5" These will make sure that even if there are severe bus problems, the driver will eiher recover or say where the problem is. These options are BAD for heavy laod and intense computing. They do nothing good for perfromance either. Do NOT use, except for debugging. To see what the driver does, enable debugging options, as per sys/sys/dpt.h The kernel should always be compiled with: options DPT_MEASURE_PERFORMANCE options DPT_LOST_IRQ options DDB options KTRACE ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 12:53:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10094 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 12:53:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA10085 for ; Wed, 1 Jul 1998 12:53:23 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 8977 invoked by uid 1000); 1 Jul 1998 19:54:04 -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: <19980701160308.A20825@easynet.fr> Date: Wed, 01 Jul 1998 15:54:04 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: David Ramahefason Subject: Re: DPT Install big problem Cc: FreeBSD-SCSI@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-Jul-98 David Ramahefason wrote: >> > >> > LED 1 stuck on means the PCI bus is hung, or the DPT is hung on the >> > bus. >> > I need a bit more data: >> > >> > Exact kernel configuration and version >> >> It's the generic kernel with all the DPT options enabled (version 2.2.6) >> >> > Motherboard details >> It's an ASUS P2B-DS >> >> > DPT firmware and BIOS versions - not the same! >> Firmware is 07L0 uhhh the bios... dunno... > > Bios is 3.E7 > >> > Any kernel messages that show during the hang >> mmm... don't remember exactly... I'll mail when I'll have them > > Well no it hangs at the fsck... during the boot... no message.. Try ctl-alt-esc and then trace command to see what the kernel is up to when appears to be hung. > ---end quoted text--- > > Cheers > > -- > /David Ramahefason Administrateur Systeme/Reseau/ > /rama@easynet.fr Easynet France SA / > /0144547031 ICQ: 14292822 / > ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 18:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07358 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 18:39:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr ([210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07276 for ; Wed, 1 Jul 1998 18:38:19 -0700 (PDT) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id KAA29020 for freebsd-scsi@freebsd.org; Thu, 2 Jul 1998 10:38:06 +0900 (KST) Date: Thu, 2 Jul 1998 10:38:06 +0900 (KST) From: swjeong Message-Id: <199807020138.KAA29020@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: [Q] double-ending SCSI RESET problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org # Environment: - I am using CAM ('3.0-980520-SNAP + CAM-980520') as follows. AHA3940UW AHA3940UW SCSC-adapter HDD HDD HDD .... HDD SCSI-adapter | | | | | | +------+----------------+------+------+---------+----------+--------+ | | Term. Term. - kernel configuration file contains belows. controller ahc0 controller scbus0 at ahc0 bus 0 controller scbus1 at ahc0 bus 1 disk da0 at scbus0 target 0 disk da1 at scbus1 target 4 disk da2 at scbus1 target 5 disk da3 at scbus1 target 6 disk da4 at scbus1 target 7 disk da5 at scbus1 target 8 disk da6 at scbus1 target 9 disk da7 at scbus1 target 10 disk da8 at scbus1 target 11 # Question: After machine A boot, I booted machine B. In the middle of kernel-autoconfiguration-stage, many 'Someone reset channel A' messages occurs on machine A. Then A panics, if with luck, A remains alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 19:51:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15847 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 19:51:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA15838 for ; Wed, 1 Jul 1998 19:51:35 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yrYqZ-0000Tx-00; Wed, 1 Jul 1998 19:11:39 -0700 Date: Wed, 1 Jul 1998 19:11:37 -0700 (PDT) From: Tom To: swjeong cc: freebsd-scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem In-Reply-To: <199807020138.KAA29020@net.kitel.co.kr> 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, 2 Jul 1998, swjeong wrote: > > After machine A boot, I booted machine B. > In the middle of kernel-autoconfiguration-stage, > many 'Someone reset channel A' messages occurs on machine A. > Then A panics, if with luck, A remains alive. Yes, because there is no support for multiple hosts on the same bus. Host B resets the bus, interupting stuff that host A is doing. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 20:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18309 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 20:12:32 -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 UAA18304 for ; Wed, 1 Jul 1998 20:12:30 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA22965; Wed, 1 Jul 1998 21:07:29 -0600 (MDT) Date: Wed, 1 Jul 1998 21:07:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807020307.VAA22965@narnia.plutotech.com> To: swjeong cc: scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem Newsgroups: pluto.freebsd.scsi In-Reply-To: <199807020138.KAA29020@net.kitel.co.kr> 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 <199807020138.KAA29020@net.kitel.co.kr> you wrote: > # Question: > > After machine A boot, I booted machine B. > In the middle of kernel-autoconfiguration-stage, > many 'Someone reset channel A' messages occurs on machine A. > Then A panics, if with luck, A remains alive. Well, it used to work. I'll link two cards together and see if I can reproduce the panic. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 1 20:14:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18638 for freebsd-scsi-outgoing; Wed, 1 Jul 1998 20:14:32 -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 UAA18630 for ; Wed, 1 Jul 1998 20:14:29 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA22978; Wed, 1 Jul 1998 21:09:32 -0600 (MDT) Date: Wed, 1 Jul 1998 21:09:32 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807020309.VAA22978@narnia.plutotech.com> To: Tom cc: scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem 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 Thu, 2 Jul 1998, swjeong wrote: > >> >> After machine A boot, I booted machine B. >> In the middle of kernel-autoconfiguration-stage, >> many 'Someone reset channel A' messages occurs on machine A. >> Then A panics, if with luck, A remains alive. > > Yes, because there is no support for multiple hosts on the same bus. > Host B resets the bus, interupting stuff that host A is doing. > > Tom This is not true. The aic7xxx driver and CAM are supposed to be able to handle spurious resets. Satoshi had a setup like this running for some time with success using the -stable driver, but I must have broken something in the CAM version of the driver. Exact error messages will help me track this down. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 01:48:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08666 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 01:48:02 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr ([210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08609 for ; Thu, 2 Jul 1998 01:47:59 -0700 (PDT) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id RAA04249 for freebsd-scsi@freebsd.org; Thu, 2 Jul 1998 17:47:52 +0900 (KST) Date: Thu, 2 Jul 1998 17:47:52 +0900 (KST) From: swjeong Message-Id: <199807020847.RAA04249@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > On Thu, 2 Jul 1998, swjeong wrote: > > > >> > >> After machine A boot, I booted machine B. > >> In the middle of kernel-autoconfiguration-stage, > >> many 'Someone reset channel A' messages occurs on machine A. > >> Then A panics, if with luck, A remains alive. > > > > Yes, because there is no support for multiple hosts on the same bus. > > Host B resets the bus, interupting stuff that host A is doing. > > > > Tom > > This is not true. The aic7xxx driver and CAM are supposed to be > able to handle spurious resets. Satoshi had a setup like this > running for some time with success using the -stable driver, but > I must have broken something in the CAM version of the driver. > > Exact error messages will help me track this down. > Sorry, I made some mistake. Exact Description is After machine A boot, I booted machine B. In the middle of kernel-autoconfiguration-stage, many 'Someone reset channel A' messages occurs on machine A. Then B panics, if with luck, B remains alive. ~~~~~~ ~~~~~~ Error message is ahc0: ahc_intr - referenced scb not valid during SELTD scb (255,15) Disconnected List Inconsistency. SCB index == 255, yet numscbs == 15. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 02:15:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12713 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 02:15:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr ([210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12701 for ; Thu, 2 Jul 1998 02:15:25 -0700 (PDT) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id SAA05944 for freebsd-scsi@freebsd.org; Thu, 2 Jul 1998 18:15:16 +0900 (KST) Date: Thu, 2 Jul 1998 18:15:16 +0900 (KST) From: swjeong Message-Id: <199807020915.SAA05944@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here is another error message when 'machine B' alive. ~~~~~ (probe0:ahc0:0:0:0): nolonger in timeout, status = 34b ahc0: Bus Device Reset Sent. 1 SCBs aborted. (probe17:ahc1:0:4:0) Sending SDTR ! (probe18:ahc1:0:4:0) Sending SDTR ! (probe19:ahc1:0:4:0) Sending SDTR ! (probe20:ahc1:0:4:0) Sending SDTR ! (probe21:ahc1:0:4:0) Sending SDTR ! (probe22:ahc1:0:4:0) Sending SDTR ! (probe23:ahc1:0:4:0) Sending SDTR ! (probe24:ahc1:0:4:0) Sending SDTR ! And after 2-3 minutes, it continues with da1 at ahc1 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number RE089844 da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 64H 32S/T 8715C) ...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 04:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06040 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 04:48:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06034 for ; Thu, 2 Jul 1998 04:48:27 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id NAA09815 for ; Thu, 2 Jul 1998 13:48:27 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id NAA23248 for scsi@freebsd.org; Thu, 2 Jul 1998 13:48:27 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807021148.NAA23248@surf.IAE.nl> Subject: Using a DPT controller, pros and cons To: scsi@FreeBSD.ORG Date: Thu, 2 Jul 1998 13:48:26 +0200 (MET DST) Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (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 Hi, We're and ISP with way to many disks..... So once in a while we have some crashes, nothing new. To overcome the trouble with replacing disks, we monitor the amount of entries in the reallocation tables in the disks. This doesn't always work, but if the number starts growing you'd better replace the disk. The other solution we want to migrate to is RAID, since it'll reduce the downtime in case of a fatal crash where we'd need to replace a disk and restore the data. (Which takes forever, if customers are calling avery 5 minutes) The remainder of the story below is waht is preventing us to go to the DPT solution, and I'd like to hear other peoples experience with this. So we have a hardware RAID-box (DTC controller) which we are testing here at work with 12*4Gb in 2 RAID-5's. At home I have a DPT-controller which at the has: RAID-5 with 3*2Gb with 2GB hotswap, on a narrow bus. on the wide bus: RAID-5 with 4*4Gb RAID-1 with 2*4Gb 1*4Gb hotswap I finally got this to work at 5 Mhz, but that'll due to the cableing. That is currently not the most important issue. During the creation of these arrays, not everything went smoothly. And thus rebuilds were fequent. My main problem is that once there is the slightes hickup, the RAID is invalidated. And you have no chance of telling the box that it was your failure. Now there are some DOS tools, but you'd have to remember that we wanted RAID's to prevent downtimes in the first place. [[ One thing I'd have to say: I never had FreeBSD-stable crash while booting when there was a rebuild. Note that I have the bootdisk on a measly IDE. ]] BUT what I really missed are any applications to be able to figure out what the RAID is doing. ALL I see is that the controller and the drive LEDs are on. Other than that: nothing is known. Simon has promissed that ASAP he'll make some applications which will allow us to get more control over our RAID's Would any pressure from clients persuade DPT to at least release some code which would give us some dptmgr functionality???? The other issue: I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the system. 2 go to the DPT RAID-1 and RAID-5 1 goes to a seperate MICROPOLIS on the onboard ahc0 contoller. Now the MICROPOLIS get a sustained write stream of something like 2.7 Mb/sec. The two RAID's do not stream the data at all. There's seconds of time where either of the disks doesn't take any data. Then one disk has, like 5Mb/sec, and the other 0-4 blocks/sec. (And this get worse if rebuild are on the way) All in all something I would not expect. the DPT contoller: 3334UW with 32Mb firmware 07L0 other hardware: ASUS 55TP4S bootdisk conner IDE 540 Mb on ahc0: cdrom, dat-tape, mo, micropolis 4.3 Gb DEC de0 10Mb ethernet ATI Mach 2Mb video and in the logs I find things like: dpt0 ERROR: Marking 246407 (Write (10) [6.1.18]) on c0b0t12u0 as late after 17711004usec dpt0 ERROR: Marking 246409 (Write (10) [6.1.18]) on c0b0t12u0 as late after 17739244usec dpt0: Salvaging Tx 246378 from the jaws of destruction (10000/18149777) dpt0: Salvaging Tx 246380 from the jaws of destruction (10000/18205091) --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 06:45:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23432 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 06:45:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23427 for ; Thu, 2 Jul 1998 06:45:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id JAA02805 for ; Thu, 2 Jul 1998 09:45:02 -0400 (EDT) Date: Thu, 2 Jul 1998 09:45:02 -0400 (EDT) From: The Hermit Hacker To: scsi@FreeBSD.ORG Subject: Drive blew up... 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 Morning... This morning, I came into alot of SCSI errors, and a bad hard drive...I'm just curious as to whether I might be mis-diagnosing, since there was nothing to indicate a problem...it just died. Basically, is it possible its the controller and not the drive, or definitively just the drive? Thanks... Here is what is in my current dmesg, or part of it: (da2:ahc1:0:1:0): Queuing a BDR SCB (da2:ahc1:0:1:0): Bus Device Reset Message Sent (da2:ahc1:0:1:0): no longer in timeout, status = 34b ahc1: Bus Device Reset Sent. 1 SCBs aborted (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 40 70 0 (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,3 (da2:ahc1:0:1:0): Bus device reset function occurred (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 75 1 0 (da2:ahc1:0:1:0): MEDIUM ERROR info:75 csi:0,2c,0,76 asc:15,2 (da2:ahc1:0:1:0): Positioning error detected by read of medium sks:80,80 (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 79 1 0 (da2:ahc1:0:1:0): MEDIUM ERROR info:79 csi:0,2c,0,7a asc:15,2 (da2:ahc1:0:1:0): Positioning error detected by read of medium sks:80,80 (da2:ahc1:0:1:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0xb SSTAT1 == 0xa (da2:ahc1:0:1:0): Queuing a BDR SCB (da2:ahc1:0:1:0): Bus Device Reset Message Sent (da2:ahc1:0:1:0): no longer in timeout, status = 34b ahc1: Bus Device Reset Sent. 1 SCBs aborted (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 b0 70 0 (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,3 (da2:ahc1:0:1:0): Bus device reset function occurred (da2:ahc1:0:1:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x8 SSTAT1 == 0xa (da2:ahc1:0:1:0): Queuing a BDR SCB (da2:ahc1:0:1:0): Bus Device Reset Message Sent (da2:ahc1:0:1:0): SCB 0x7 - timed out in message out phase, SCSISIGI == 0xa4 SEQADDR == 0x154 SSTAT1 == 0x2 (da2:ahc1:0:1:0): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 1 SCBs aborted (da1:ahc1:0:0:0): WRITE(10). CDB: 2a 0 0 27 40 e0 0 0 10 0 (da1:ahc1:0:0:0): UNIT ATTENTION asc:29,2 (da1:ahc1:0:0:0): Scsi bus reset occurred (da2:ahc1:0:1:0): READ(06). CDB: 8 0 1 12 1 0 (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,2 (da2:ahc1:0:1:0): Scsi bus reset occurred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 09:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21613 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 09:20:59 -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 JAA21589 for ; Thu, 2 Jul 1998 09:20:49 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA03869; Thu, 2 Jul 1998 10:15:43 -0600 (MDT) Date: Thu, 2 Jul 1998 10:15:43 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807021615.KAA03869@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: Drive blew up... 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: > > Morning... > > This morning, I came into alot of SCSI errors, and a bad hard drive...I'm > just curious as to whether I might be mis-diagnosing, since there was > nothing to indicate a problem...it just died. > > Basically, is it possible its the controller and not the drive, or > definitively just the drive? There is no code in CAM or the aic7xxx driver to make up media errors. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 09:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24882 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 09:38:42 -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 JAA24875 for ; Thu, 2 Jul 1998 09:38:31 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA05134; Thu, 2 Jul 1998 10:33:19 -0600 (MDT) Date: Thu, 2 Jul 1998 10:33:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807021633.KAA05134@narnia.plutotech.com> To: swjeong cc: scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem Newsgroups: pluto.freebsd.scsi In-Reply-To: <199807020138.KAA29020@net.kitel.co.kr> 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 <199807020138.KAA29020@net.kitel.co.kr> you wrote: I just noticed a problem in your hard wiring. > # Environment: > > - I am using CAM ('3.0-980520-SNAP + CAM-980520') as follows. > > AHA3940UW AHA3940UW > SCSC-adapter HDD HDD HDD .... HDD SCSI-adapter > | | | | | | > +------+----------------+------+------+---------+----------+--------+ > | | > Term. Term. > > > - kernel configuration file contains belows. > > controller ahc0 > controller scbus0 at ahc0 bus 0 > controller scbus1 at ahc0 bus 1 The 3940 does not export two busses hanging off one controller. It exports two controllers. The correct hard wiring should look like: controller ahc0 controller ahc1 controller scbus0 at ahc0 controller scbus1 at ahc1 -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 09:51:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26443 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 09:51:28 -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 JAA26433 for ; Thu, 2 Jul 1998 09:51:26 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA05254; Thu, 2 Jul 1998 10:46:25 -0600 (MDT) Date: Thu, 2 Jul 1998 10:46:25 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807021646.KAA05254@narnia.plutotech.com> To: swjeong cc: scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem In-Reply-To: <199807020915.SAA05944@net.kitel.co.kr> 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 The next snapshot will have a fix for this particular bug. > Here is another error message when 'machine B' alive. > ~~~~~ > > (probe0:ahc0:0:0:0): nolonger in timeout, status = 34b > ahc0: Bus Device Reset Sent. 1 SCBs aborted. > (probe17:ahc1:0:4:0) Sending SDTR ! > (probe18:ahc1:0:4:0) Sending SDTR ! > (probe19:ahc1:0:4:0) Sending SDTR ! > (probe20:ahc1:0:4:0) Sending SDTR ! > (probe21:ahc1:0:4:0) Sending SDTR ! > (probe22:ahc1:0:4:0) Sending SDTR ! > (probe23:ahc1:0:4:0) Sending SDTR ! > (probe24:ahc1:0:4:0) Sending SDTR ! > > > And after 2-3 minutes, it continues with > > da1 at ahc1 bus 0 target 4 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: Serial Number RE089844 > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 8715MB (17850000 512 byte sectors: 64H 32S/T 8715C) > > ...... -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 10:08:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28389 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 10:08:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA28359 for ; Thu, 2 Jul 1998 10:08:13 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yrmK5-00012B-00; Thu, 2 Jul 1998 09:35:01 -0700 Date: Thu, 2 Jul 1998 09:34:52 -0700 (PDT) From: Tom To: wjw@IAEhv.nl cc: scsi@FreeBSD.ORG Subject: Re: Using a DPT controller, pros and cons In-Reply-To: <199807021148.NAA23248@surf.IAE.nl> 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, 2 Jul 1998, Willem Jan Withagen wrote: > The other issue: > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the What blocksize? > system. > > 2 go to the DPT RAID-1 and RAID-5 > 1 goes to a seperate MICROPOLIS on the onboard ahc0 contoller. > > Now the MICROPOLIS get a sustained write stream of something like 2.7 > Mb/sec. The two RAID's do not stream the data at all. There's seconds of > time where either of the disks doesn't take any data. Then one disk has, > like 5Mb/sec, and the other 0-4 blocks/sec. > (And this get worse if rebuild are on the way) Well, you are operating the DPT with only narrow drives at 5mhz, so that is going to hurt. Also, the DPT controller is optimized for random access, not sequentional access. If "dd" writing represents a typical function of your system, you should probably disable the write cache completely. > and in the logs I find things like: > dpt0 ERROR: Marking 246407 (Write (10) [6.1.18]) on c0b0t12u0 > as late after 17711004usec > dpt0 ERROR: Marking 246409 (Write (10) [6.1.18]) on c0b0t12u0 > as late after 17739244usec > dpt0: Salvaging Tx 246378 from the jaws of destruction (10000/18149777) > dpt0: Salvaging Tx 246380 from the jaws of destruction (10000/18205091) You've got some real problems with your hardware. You shouldn't see any such warnings. > --WjW > > -- > Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 > P.O. 928, 5600 AX Eindhoven, The Netherlands > Full Internet connectivity for only fl 12.95 a month. > Call now, and login as 'new'. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 13:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29269 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 13:12:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA29250 for ; Thu, 2 Jul 1998 13:12:40 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 19400 invoked by uid 1000); 2 Jul 1998 20:13:14 -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: <199807021148.NAA23248@surf.IAE.nl> Date: Thu, 02 Jul 1998 16:13:14 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: wjw@IAEhv.nl Subject: RE: Using a DPT controller, pros and cons Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 02-Jul-98 Willem Jan Withagen wrote: ... > I finally got this to work at 5 Mhz, but that'll due to the cableing. > That > is currently not the most important issue. > During the creation of these arrays, not everything went smoothly. And > thus > rebuilds were fequent. My main problem is that once there is the slightes > hickup, the RAID is invalidated. And you have no chance of telling the > box > that it was your failure. Now there are some DOS tools, but you'd have to > remember that we wanted RAID's to prevent downtimes in the first place. this is truely the downside of the DPT system; The interconnect between the controller and its disks is under user control. this means that bad disks, bad canisters, bad enclosures, bad cables, bad power supplies, can all cause disruption. It is also true that if the DPT ``looses'' a device on the bus, and the device ``re-appears'' after a boot, the DPT still marks it red-flag. But what is the alternative? To blindly take a device that previously FAILED and make it good? Automatically? I agree that we could have the optimal utility ported, but frankly I was convinced by my technical contacts at DPT that this is not a good idea. If you had a failure, then you should explicitly override the failure tag. BTW, I said it before, and I'll say it again; All my problems of this nature have disappeared once I switched to DPT supplied disks, canisters, enclosures and cables. I also, without fail, use ECC memory supplied by DPT. Yes, it is expensive, but so is downntime. The RAID boxes do not give you a choice. they insist that not only they supply everything except for a host, most of them will not allow you to swap a disk yourself! > [[ One thing I'd have to say: > I never had FreeBSD-stable crash while booting when there was a > rebuild. Note that I have the bootdisk on a measly IDE. > ]] This is understandable. The I/O load associated with booting was not put on the array being built. There is a firmware bug/weakness regarding heavy disk loads during a rebuild. I belive the proper people at DPT are aware of it. I will post a new firmware when one is available. In the meantime, use 7L0, NOT 7M0. If you insist on 7M0, have 7L0 available to re-load to the controller. > BUT what I really missed are any applications to be able to figure out > what > the RAID is doing. ALL I see is that the controller and the drive LEDs > are > on. Other than that: nothing is known. > Simon has promissed that ASAP he'll make some applications which will > allow > us to get more control over our RAID's 3.0-current has certain utilities. I will provide more once the migration to CAM and the initial release of the 5th generation controllers is out. > Would any pressure from clients persuade DPT to at least release some > code > which would give us some dptmgr functionality???? I have some code samples already. I will port them to FreeBSD as time permits. > The other issue: > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the > system. > 2 go to the DPT RAID-1 and RAID-5 > 1 goes to a seperate MICROPOLIS on the onboard ahc0 contoller. > > Now the MICROPOLIS get a sustained write stream of something like 2.7 > Mb/sec. The two RAID's do not stream the data at all. There's seconds of > time where either of the disks doesn't take any data. Then one disk has, > like 5Mb/sec, and the other 0-4 blocks/sec. > (And this get worse if rebuild are on the way) Forward this to DPT. The FreeBSD code has nothing to do with such things :-( You can try and run dptcntl to see the data and transaction rates, the longest delay and a host of other metrics. >From experience, you will not cause the DPt to ``stream'' before you have around 64 dd's. > All in all something I would not expect. > the DPT contoller: 3334UW with 32Mb firmware 07L0 > other hardware: > ASUS 55TP4S > bootdisk conner IDE 540 Mb > on ahc0: cdrom, dat-tape, mo, micropolis 4.3 Gb > DEC de0 10Mb ethernet > ATI Mach 2Mb video > > and in the logs I find things like: > dpt0 ERROR: Marking 246407 (Write (10) [6.1.18]) on c0b0t12u0 > as late after 17711004usec > dpt0 ERROR: Marking 246409 (Write (10) [6.1.18]) on c0b0t12u0 > as late after 17739244usec > dpt0: Salvaging Tx 246378 from the jaws of destruction (10000/18149777) > dpt0: Salvaging Tx 246380 from the jaws of destruction (10000/18205091) Ah! Thanx! Explanation: when the SCSi abstraction layer (in the FreeBSD kernel, probably sys/scsi/sd.c) sent that command, it marked it to be timed out in 10 seconds (10,000ms. After 17 seconds (17,710,004us, about 17,000ms), I mark the transaction as ``probably lost, should be aborted'', but, from experience, I know better and wait a little longer (other activitiy continues!). Indeed, after one more second (for a total of about 18 seconds or more) the transaction completes and re-appears. This is where the ``Salvaging...'' message tells you that and completes the transaction as if all was well. A comment: * If you get these message to go away (more on that later), remove these kernel options that enable this code. They are slow, invasive and ugly. they should be used only for debugging. What can cause a transaction to take 18 seconds to complete, while others complete much faster? The best I can tell is either of these scenarios: * There is a soft error somewhere between the disk and the controller. Lots of re-tries, etc. * The disk is starving the transaction. This happens a lot with certain disk drives. I had a horrible time with some Micropolis disks. Here is what happens: The DPT sends I/O request for sectors 10, 10000, 5, and 30. Very shortly afterwards, it sends more requests, all for sectors in the (example!) 0-500 range. The drive employs an elevator sort to optimize seeks. As a result of a subtle bug in the firmware, the drive never gets to the sector 10000. It is very busy in the 0-500 range. Result: The ``far-out'' sector does not get served. Why is it happening on the DPT more than normal controllers? The DPT, especially when writing to RAID arrays, write in fairly large stripes (128KB to 1MB are not uncommon). this makes the I/O bursty. In RAID-5 it is even worse as the DPT reads/writes to several drives, in quick bursts when executing a WRITE request. Also, the way caching works is to hold back writes until the pages age. Then they are burst written to disk. The access profile is dramatically different from ``normal'' drive attached to ``normal'' controller. * Soft errors during transfer phases. Marginal cables, enclosures, backplanes, etc. can aggravate the reliability problem, inducing many resets, re-tries, etc. Solution? Smaller stripes, more cache memory on the DPT, ECC memory on the controller, ECC disks, good packaging, cabling, etc. BTW, 2.5MB/Sec is slow, but do not expect RAID-5 to run as fast as RAID-0, nor should you expect sequential access to be as fast on a RAID array as on a single disk. You need lots of cache for read-ahead to get that. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 14:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15778 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 14:50:12 -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 OAA15697 for ; Thu, 2 Jul 1998 14:49:56 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA21791 (5.67b/IDA-1.5); Thu, 2 Jul 1998 23:03:48 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA02314; Thu, 2 Jul 1998 20:40:43 +0200 (CEST) From: Wilko Bulte Message-Id: <199807021840.UAA02314@yedi.iaf.nl> Subject: Re: Drive blew up... In-Reply-To: from The Hermit Hacker at "Jul 2, 98 09:45:02 am" To: scrappy@hub.org (The Hermit Hacker) Date: Thu, 2 Jul 1998 20:40:43 +0200 (CEST) Cc: 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+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As The Hermit Hacker wrote... > > Morning... > > This morning, I came into alot of SCSI errors, and a bad hard drive...I'm > just curious as to whether I might be mis-diagnosing, since there was > nothing to indicate a problem...it just died. > > Basically, is it possible its the controller and not the drive, or > definitively just the drive? > > Thanks... > > > Here is what is in my current dmesg, or part of it: > > (da2:ahc1:0:1:0): Queuing a BDR SCB > (da2:ahc1:0:1:0): Bus Device Reset Message Sent > (da2:ahc1:0:1:0): no longer in timeout, status = 34b > ahc1: Bus Device Reset Sent. 1 SCBs aborted > (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 40 70 0 > (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,3 > (da2:ahc1:0:1:0): Bus device reset function occurred > (da2:ahc1:0:1:0): READ(06). CDB: 8 0 0 75 1 0 > (da2:ahc1:0:1:0): MEDIUM ERROR info:75 csi:0,2c,0,76 asc:15,2 > (da2:ahc1:0:1:0): Positioning error detected by read of medium sks:80,80 Really sounds like a track following problem. Servo head or servo amplifier or dying positioner or.. But the drive alright. Make backups fast... 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 Thu Jul 2 14:52:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16327 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 14:52:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16243 for ; Thu, 2 Jul 1998 14:52:29 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id XAA28642; Thu, 2 Jul 1998 23:52:21 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id XAA26473; Thu, 2 Jul 1998 23:52:20 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807022152.XAA26473@surf.IAE.nl> Subject: Re: Using a DPT controller, pros and cons In-Reply-To: from Simon Shapiro at "Jul 2, 98 04:13:14 pm" To: shimon@simon-shapiro.org Date: Thu, 2 Jul 1998 23:52:20 +0200 (MET DST) Cc: wjw@IAEhv.nl, scsi@FreeBSD.ORG Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (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 You ( Simon Shapiro ) write: [ about DPT-raid's needing (M$)-DOS for configuration, and that it is relatively easy to disrupt a GOOD raid. ] => disks, bad canisters, bad enclosures, bad cables, bad power supplies, can => all cause disruption. => => It is also true that if the DPT ``looses'' a device on the bus, and the => device ``re-appears'' after a boot, the DPT still marks it red-flag. But => what is the alternative? To blindly take a device that previously FAILED => and make it good? Automatically? Nope, Your next point is more than true. Downtime is the most expensive problem you can have. It only problem is that it is hardly counted for in hard currency. Unless you go for a contract with penalty clause. => I agree that we could have the optimal utility ported, but frankly I was => convinced by my technical contacts at DPT that this is not a good idea. => If you had a failure, then you should explicitly override the failure tag. Well, als long as I decide that I've messed with my system, and I'm relatively shure that I never got to the writing stage of my OS. Then I see no problem. Remember that I once was saved by optimal.exe because I had a wire crossed and ended up with 2 clients for ID 6: tape and disk. Otherwise I would have lost the data that I wanted to backup in the first place. => BTW, I said it before, and I'll say it again; All my problems of this => nature have disappeared once I switched to DPT supplied disks, canisters, => enclosures and cables. I also, without fail, use ECC memory supplied by => DPT. Yes, it is expensive, but so is downntime. I know, but you have to realise that we have a different approach as to how we architecture our setup. EG. we have atleast 5 systems with modest storage requirements <20Gb. So that would require atleast US$25.000 for disks, controllers and cabinets. And those are the "cheap" home-brew cabinets. Note that most of the data is local to those systems, and we do not want to have 1 large NFS server with all the data. (Or we are seriously trying to avoid that) Just out of curiosity I would be interested in what a DPT set would cost: controller cabinet for 5 disks 4*4Gb disks in canister cables => There is a firmware bug/weakness regarding heavy => disk loads during a rebuild. I belive the proper people at DPT are aware => of it. I will post a new firmware when one is available. In the meantime, => use 7L0, NOT 7M0. If you insist on 7M0, have 7L0 available to re-load to => the controller. We've had this discussion when I was still running 7h0 => > BUT what I really missed are any applications to be able to figure out => > what the RAID is doing. ALL I see is that the controller and the drive => > LEDs are on. Other than that: nothing is known. Simon has promissed => > that ASAP he'll make some applications which will allow us to get more => > control over our RAID's => => 3.0-current has certain utilities. I will provide more once the migration => to CAM and the initial release of the 5th generation controllers is out. Is it possible to back-port these to 2.2-STABLE? Or does it require too much changes to the way you interface with the card? => > The other issue: => > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the => > system. => > 2 go to the DPT RAID-1 and RAID-5 => > 1 goes to a seperate MICROPOLIS on the onboard ahc0 contoller. => > => > Now the MICROPOLIS get a sustained write stream of something like 2.7 => > Mb/sec. The two RAID's do not stream the data at all. There's seconds of => > time where either of the disks doesn't take any data. Then one disk has, => > like 5Mb/sec, and the other 0-4 blocks/sec. => > (And this get worse if rebuild are on the way) => => Forward this to DPT. The FreeBSD code has nothing to do with such things => :-( You can try and run dptcntl to see the data and transaction rates, the => longest delay and a host of other metrics. I have some stuff in a DPT/tools directory, but they do not seem to work. First I had to change from major devno 130 to devno 88, but still no go. I'm starting to wonder if my mirror of your DPT directory is still operational? Where do you currently keep your FreeBSD work? The performance issue, I'll get to in another thread. thanx, --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 15:06:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18114 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 15:06:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18105 for ; Thu, 2 Jul 1998 15:06:22 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id SAA13985; Thu, 2 Jul 1998 18:06:08 -0400 (EDT) Date: Thu, 2 Jul 1998 18:06:08 -0400 (EDT) From: The Hermit Hacker To: Wilko Bulte cc: scsi@FreeBSD.ORG Subject: Re: Drive blew up... In-Reply-To: <199807021840.UAA02314@yedi.iaf.nl> 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, 2 Jul 1998, Wilko Bulte wrote: > Really sounds like a track following problem. Servo head or servo amplifier > or dying positioner or.. But the drive alright. Make backups fast... Drive being replaced tomorrow...I *hoped* that it was something less painful, but...*shrug* Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 15:10:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18821 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 15:10:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA18743 for ; Thu, 2 Jul 1998 15:10:09 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 21179 invoked by uid 1000); 2 Jul 1998 22:10:44 -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: <199807022152.XAA26473@surf.IAE.nl> Date: Thu, 02 Jul 1998 18:10:44 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: wjw@IAEhv.nl Subject: Re: Using a DPT controller, pros and cons Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 02-Jul-98 Willem Jan Withagen wrote: ... > Well, als long as I decide that I've messed with my system, and I'm > relatively shure that I never got to the writing stage of my OS. Then > I see no problem. Remember that I once was saved by optimal.exe because I > had a wire crossed and ended up with 2 clients for ID 6: tape and disk. > Otherwise I would have lost the data that I wanted to backup in the first > place. I did not say optimal.exe is useless. I used it more than once! BTW, it is broken, as it only works in certain MB, DPT, firmware combinations. I am going to add it to the DPt driver. Then it will be an option in dptcntl. ... > Just out of curiosity I would be interested in what a DPT set would cost: > controller > cabinet for 5 disks > 4*4Gb disks in canister > cables I belive the shelf for 8 disks is about $2,300, the disks 9in a canister are about $100 over mail order prices. The shelf comes with one cable and two powersupplies, and two fans and an automatic differential/SE interface and two terminators. But I may be wrong a bit. > We've had this discussion when I was still running 7h0 7H0 was sick in this depratment and several others. > => 3.0-current has certain utilities. I will provide more once the > migration > => to CAM and the initial release of the 5th generation controllers is > out. > > Is it possible to back-port these to 2.2-STABLE? Or does it require too > much > changes to the way you interface with the card? The changes are rather streightforward. The card interface is essentially identical. The difficulty arises from the close ties /dev/dpt has to the HAS work I am working on. Even worse is the certification process. Before I will release this code, I need to spend several weeks in regression testing. I simply do not have the time right now. There is pressure to move the DPT driver to CAM, and to continue with the HAS work. ... > I have some stuff in a DPT/tools directory, but they do not seem to work. > First I had to change from major devno 130 to devno 88, but still no go. > I'm starting to wonder if my mirror of your DPT directory is still > operational? Where do you currently keep your FreeBSD work? The major number is a NOP. The latest work is in ftp://simon-shapiro.org/crash. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 15:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19914 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 15:16:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19851 for ; Thu, 2 Jul 1998 15:16:26 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id AAA04589; Fri, 3 Jul 1998 00:16:25 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id AAA00878; Fri, 3 Jul 1998 00:16:25 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807022216.AAA00878@surf.IAE.nl> Subject: Re: Using a DPT controller, pros and cons In-Reply-To: from Simon Shapiro at "Jul 2, 98 06:10:44 pm" To: shimon@simon-shapiro.org Date: Fri, 3 Jul 1998 00:16:24 +0200 (MET DST) Cc: wjw@IAEhv.nl, scsi@FreeBSD.ORG Reply-To: wjw@IAEhv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (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 You ( Simon Shapiro ) write: => I belive the shelf for 8 disks is about $2,300, the disks 9in a canister => are about $100 over mail order prices. The shelf comes with one cable and => two powersupplies, and two fans and an automatic differential/SE interface => and two terminators. But I may be wrong a bit. The most likely risk is that the US DPT department will redirect me to the European distributers. So whre do you get your stuff, or can you give a name of a person to get a quote. => > Is it possible to back-port these to 2.2-STABLE? Or does it require too => > much => > changes to the way you interface with the card? => => The changes are rather streightforward. The card interface is essentially => identical. The difficulty arises from the close ties /dev/dpt has to the => HAS work I am working on. Even worse is the certification process. Before => I will release this code, I need to spend several weeks in regression => testing. I simply do not have the time right now. There is pressure to => move the DPT driver to CAM, and to continue with the HAS work. So going CAM on 2.2-STABLE would be our direction in future as well?? --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 15:49:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25105 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 15:49:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25100 for ; Thu, 2 Jul 1998 15:49:56 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id AAA11754; Fri, 3 Jul 1998 00:49:57 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id AAA06671; Fri, 3 Jul 1998 00:49:56 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807022249.AAA06671@surf.IAE.nl> Subject: Re: Using a DPT controller, pros and cons In-Reply-To: from Tom at "Jul 2, 98 09:34:52 am" To: tom@sdf.com (Tom) Date: Fri, 3 Jul 1998 00:49:56 +0200 (MET DST) Cc: wjw@iaehv.nl, scsi@FreeBSD.ORG Reply-To: wjw@iaehv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (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 You ( Tom ) write: => => On Thu, 2 Jul 1998, Willem Jan Withagen wrote: => => > The other issue: => > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the => => What blocksize? Just the dd-default. Would that matter in what I observe? I was just trying to see if I understand this box. :-) => Well, you are operating the DPT with only narrow drives at 5mhz, so that => is going to hurt. Also, the DPT controller is optimized for random => access, not sequentional access. If "dd" writing represents a typical => function of your system, you should probably disable the write cache => completely. No, just trying to see if things work. It be used as: mail-server web-server news-server home-directories for +10.000 users ...... => You've got some real problems with your hardware. You shouldn't see => any such warnings. :-{ --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 18:00:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09663 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 18:00:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA09645 for ; Thu, 2 Jul 1998 18:00:05 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yrtgi-0001La-00; Thu, 2 Jul 1998 17:26:52 -0700 Date: Thu, 2 Jul 1998 17:26:52 -0700 (PDT) From: Tom To: wjw@iaehv.nl cc: scsi@FreeBSD.ORG Subject: Re: Using a DPT controller, pros and cons In-Reply-To: <199807022249.AAA06671@surf.IAE.nl> 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, 3 Jul 1998, Willem Jan Withagen wrote: > You ( Tom ) write: > => > => On Thu, 2 Jul 1998, Willem Jan Withagen wrote: > => > => > The other issue: > => > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the > => > => What blocksize? > > Just the dd-default. Would that matter in what I observe? I was just trying > to see if I understand this box. :-) A small block size can mean lots of extra SCSI commands (one per block), which adds a lot of extra overhead, and since your bus is only operating at 5mhz, that can be pretty bad. Try "bs=64k". Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 18:53:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16948 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 18:53:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16935; Thu, 2 Jul 1998 18:53:38 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id TAA15629; Thu, 2 Jul 1998 19:52:56 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Thu, 2 Jul 1998 19:52:56 -0600 (MDT) From: Brett Taylor To: freebsd-questions@FreeBSD.ORG cc: freebsd-scsi@FreeBSD.ORG Subject: Buslogic 948 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 Hi, I'm trying to install FreeBSD on a former Linux box. It's got one of the silly Flashpoint cards which we don't have support for. We're going to be buying, if it's supported, a 948C. It APPEARS from the mailing list archive that the 948 is supported, but I wanted to be absolutely sure before we put in the purchase order. Thanks, Brett *********************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ How many Microsoft employees does it take to change a light bulb? Zero. They declared Darkness[tm] the standard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 2 22:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16596 for freebsd-scsi-outgoing; Thu, 2 Jul 1998 22:28:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pcpsj.pfcs.com (K+GDLaIUzaYKUzdWFyVtUhC7KWnQ90Vy@harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16585 for ; Thu, 2 Jul 1998 22:28:06 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Fri, 3 Jul 1998 01:27:39 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 2 Jul 1998 22:27:37 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Fri, 3 Jul 1998 01:27:36 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: dc-sage@dc-sage.org, scsi@FreeBSD.ORG, amanda-users@cs.umd.edu Subject: DDS/2 tape specs X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jul 1998 01:27:35 -0400 Message-ID: <596.899443655@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wanted to see how much data could be written to a DDS-2 120M 4mm tape. I have an ARCHIVE Python 28388-XXX 4.98 drive on ID5, and: bt0 rev 0 int a irq 11 on pci0:11:0 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs ... bt0: targ 5 sync rate= 5.00MB/s(200ns), offset=15 I wrote 8k blocks. My first test did a "dd" copy of /dev/urandom to the drive: % dd bs=8k if=/dev/urandom of=/dev/rst0 dd: /dev/rst0: Input/output error 413953+0 records in 413952+0 records out 3391094784 bytes transferred in 18181.953012 secs (186509 bytes/sec) My second test took 8191 `y' characters followed by a newline: % yes `cat 8ky` | dd bs=8k of=/dev/rst0 and I eventually killed after over 24 hours' elapsed time. When I killed it, I think it claimed to have written nearly 10G to the tape. My third test copied 2 4G (reasonably full) filesystems to the drive: % cat /dev/sd1c /dev/sd2c | dd bs=8k of=/dev/rst0 dd: /dev/rst0: Input/output error 797354+0 records in 797353+0 records out 6531915776 bytes transferred in 15816.188468 secs (412989 bytes/sec) Just for grins... % tcopy file 0: block size 8192: tcopy: read error, file 0, record 797349: Input/output error I then rewound the tape, did a "mt fsr 787349" followed by "mt weof 100000", but the "weof" part finished Immediately and without error, so I didn't believe it. For my last test, I did: % while ( dd bs=$size if=/dev/sd1c of=$mt count=3 && mt weof 3 ) ... 3+0 records in 3+0 records out 24576 bytes transferred in 0.053951 secs (455525 bytes/sec) mt: /dev/nrst0: weof: Input/output error Did 249699 reps... (the "while" loop had a counter in it) so 249699*3=749097 8k blocks... Assuming the same density for the previous case, which did 797353 8k blocks... or .93947975 is data, which means that .06052024 is "tape mark space". This means that: .06052024 * 6531915776 bytes / 797353 tape marks or 528 bytes/tape mark is "tape mark space". Summarizing: The tape drive can write at about 400k/sec A 120M 4mm tape can hold about 3.3G of random (compressed) data, or 6.3G of normal filesystem stuff A tape mark uses about 600 bytes of space. Am I missing anything? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 00:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27855 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 00:03:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gatekeeper.falcon.com (appp8.sysnet.net [206.142.16.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27843 for ; Fri, 3 Jul 1998 00:03:35 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id CAA04324 for ; Fri, 3 Jul 1998 02:55:13 -0400 (EDT) X-Sender: patton@mail.sysnet.net (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 2 Jul 1998 02:55:25 -0400 To: freebsd-scsi@FreeBSD.ORG From: Matthew Patton Subject: ZIP support in 2.2.6 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I looked thru the recent archives and I haven't seen much in they way of dealing with ZIP drives. My external SCSI version shows up as an "sd" device. So is software eject supported? What's the command to use? There doesn't seem to be any flags for "umount" or an "eject" command for that matter. Please respond directly, I'm not subscribed to the list just yet. Thanks. -------- It is by caffeine alone I set my mind in motion, it is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning, it is by caffeine alone I set my mind in motion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 00:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03629 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 00:40:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03624 for ; Fri, 3 Jul 1998 00:40:22 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id JAA01531; Fri, 3 Jul 1998 09:40:22 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id JAA04676; Fri, 3 Jul 1998 09:40:21 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807030740.JAA04676@surf.IAE.nl> Subject: Re: Using a DPT controller, pros and cons In-Reply-To: from Tom at "Jul 2, 98 05:26:52 pm" To: tom@sdf.com (Tom) Date: Fri, 3 Jul 1998 09:40:21 +0200 (MET DST) Cc: wjw@iaehv.nl, scsi@FreeBSD.ORG Reply-To: wjw@iaehv.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (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 You ( Tom ) write: => => On Fri, 3 Jul 1998, Willem Jan Withagen wrote: => => > You ( Tom ) write: => > => => > => On Thu, 2 Jul 1998, Willem Jan Withagen wrote: => > => => > => > The other issue: => > => > I've done 3 'dd if=/dev/zero of=/mnt?/bar' in parallel on the => > => => > => What blocksize? => > => > Just the dd-default. Would that matter in what I observe? I was just trying => > to see if I understand this box. :-) => => A small block size can mean lots of extra SCSI commands (one per block), => which adds a lot of extra overhead, and since your bus is only operating => at 5mhz, that can be pretty bad. Try "bs=64k". I get your point, but as I'm trying to get this system worked out. Your remarks lead me to keep it at default blocks. :-) It keeps the system more in stressed state, and thus errors show up more easily. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 01:46:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14224 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 01:46:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr ([210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14219 for ; Fri, 3 Jul 1998 01:46:05 -0700 (PDT) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id RAA15364 for freebsd-scsi@freebsd.org; Fri, 3 Jul 1998 17:45:50 +0900 (KST) Date: Fri, 3 Jul 1998 17:45:50 +0900 (KST) From: swjeong Message-Id: <199807030845.RAA15364@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: Re: [Q] double-ending SCSI RESET problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org # Environment - I am using CAM ('3.0-980520-SNAP + CAM-980520') as follows. AHA3940UW AHA3940UW SCSC-adapter HDD HDD HDD .... HDD SCSI-adapter | | | | | | +------+----------------+------+------+---------+----------+--------+ | | Term. Term. (3940's Termination is disabled and scsi bus is connected on internal channel B, channel A is used for boot disk) # Problem discussed up to now. After machine A boot, I booted machine B. In the middle of kernel-autoconfiguration-stage, many many 'Someone reset channel A' messages occurs on machine A and B. Tt lasts from few seconds to forever. Then B panics, if with luck, B remains alive. And made kernel configuration file correct as "Justin T. Gibbs" said. > controller ahc0 > controller ahc1 > controller scbus0 at ahc0 > controller scbus1 at ahc1 But, the problem persisted. # Question. I applied following two awkward patch to escape above problem. aic7xxx.c patch makes ahc not to issue RESET again, when it detected RESET on the bus. scsi_all.c patch makes opearation not to stopped by UNIT ATTENTION. After this patch, 'Someone reset channel A' doen't occurs continuously. and disk operation is not halted by peer's rebooting. Does this patch make sense ? $ diff aic7xxx.c.orig aic7xxx.c 4140c4140 < ahc_reset_current_bus(ahc); --- > /* ahc_reset_current_bus(ahc); */ 4152c4152 < ahc_reset_current_bus(ahc); --- > /* ahc_reset_current_bus(ahc); */ $ diff scsi_all.c.orig scsi_all.c 2134a2135,2139 > > error = ERESTART; > print_sense = FALSE; > break; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 04:57:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16099 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 04:57:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sloep106.cs.vu.nl (root@sloep106.cs.vu.nl [130.37.24.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16080 for ; Fri, 3 Jul 1998 04:57:02 -0700 (PDT) (envelope-from gkoller@cs.vu.nl) Received: from localhost by sloep106.cs.vu.nl with smtp (Smail3.1.28.1 #56) id m0ys4SK-0001f1C; Fri, 3 Jul 98 13:56 +0200 Date: Fri, 3 Jul 1998 13:56:43 +0200 (MET DST) From: Guido Kollerie Reply-To: Guido Kollerie To: Brett Taylor cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Buslogic 948 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 Thu, 2 Jul 1998, Brett Taylor wrote: > We're going to be > buying, if it's supported, a 948C. It APPEARS from the mailing list > archive that the 948 is supported, but I wanted to be absolutely sure > before we put in the purchase order. The BT-948 is supported by the old Buslogic Multimaster series driver as well as the new CAM Buslogic Multimaster series driver (in -stable & -current). For more info on CAM see: ftp://ftp.freebsd.org/pub/FreeBSD/cam/README -- Guido Kollerie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 13:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13460 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 13:16:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13455 for ; Fri, 3 Jul 1998 13:16:57 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt3-233.HiWAAY.net [208.147.146.233]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id PAA06760; Fri, 3 Jul 1998 15:16:53 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id PAA21647; Fri, 3 Jul 1998 15:16:50 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199807032016.PAA21647@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Harlan Stenn cc: dc-sage@dc-sage.org, scsi@FreeBSD.ORG, amanda-users@cs.umd.edu From: David Kelly Subject: Re: DDS/2 tape specs In-reply-to: Message from Harlan Stenn of "Fri, 03 Jul 1998 01:27:35 EDT." <596.899443655@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jul 1998 15:16:50 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Harlan Stenn writes: > My second test took 8191 `y' characters followed by a newline: > > % yes `cat 8ky` | dd bs=8k of=/dev/rst0 > > and I eventually killed after over 24 hours' elapsed time. > When I killed it, I think it claimed to have written nearly 10G to the tape. 24 hrs for only 10G doesn't sound good. To a similar DDS-2 (with compression) drive I once used dd to copy /dev/null until something broke. Got 88G on a DDS-1 90m tape. Took about 8 hours. SGI Indy R5000, Irix 6.2, OEM SGI/Seagate/Archive DDS-2 tape drive. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 3 15:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27738 for freebsd-scsi-outgoing; Fri, 3 Jul 1998 15:53:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA27730 for ; Fri, 3 Jul 1998 15:53:18 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 3352 invoked by uid 1017); 3 Jul 1998 21:50:10 -0000 Date: Fri, 3 Jul 1998 15:50:10 -0600 (MDT) From: Atipa To: "Justin T. Gibbs" cc: freebsd-scsi@FreeBSD.ORG Subject: CAM/Ultra2 no go... In-Reply-To: <199803091540.IAA06881@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin, The CAM code is not working w/ a Quantum Viking II 4.5 Ultra2 7200RPM drive. I am using the cam-boot floppy and the 5-20 CAM code and SNAP. It can not reset SCSI bus, page faults, and halts the system. Tried 2 different drives, same result. Using normal wide SCSI drives, all is well. > Support for aic7890/91/95 based controllers. > ULTRA2 speeds have not yet been tested. > I'd be happy to do so if someone wants to > send me a drive. 8-) FedEx # 4276-0903-9262. Will arrive Monday or Tuesday. Thanks, Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 4 01:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27701 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 01:32:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27668 for ; Sat, 4 Jul 1998 01:31:48 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id PAA28320; Sat, 4 Jul 1998 15:34:29 +0700 (NSS) Date: Sat, 4 Jul 1998 15:34:28 +0700 (NSS) From: Ustimenko Semen To: David Kelly cc: Harlan Stenn , dc-sage@dc-sage.org, scsi@FreeBSD.ORG, amanda-users@cs.umd.edu Subject: Re: DDS/2 tape specs In-Reply-To: <199807032016.PAA21647@nospam.hiwaay.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, 3 Jul 1998, David Kelly wrote: > Harlan Stenn writes: > > My second test took 8191 `y' characters followed by a newline: > > > > % yes `cat 8ky` | dd bs=8k of=/dev/rst0 > > > > and I eventually killed after over 24 hours' elapsed time. > > When I killed it, I think it claimed to have written nearly 10G to the tape. > > 24 hrs for only 10G doesn't sound good. > > To a similar DDS-2 (with compression) drive I once used dd to copy > /dev/null until something broke. Got 88G on a DDS-1 90m tape. Took > about 8 hours. SGI Indy R5000, Irix 6.2, OEM SGI/Seagate/Archive DDS-2 > tape drive. > Yes, in good times it writes real fs data on 500-800 Kb/s. But in worst, it goes on 20-80 Kb/s :-( Else total capacity and speed decrease after you use tape many times without eraseing it and/or cleaning drive's head. IMHO there are linear dependence between data speed and cartridge capacity (becouse the tape speed is fixed). I'm useing SDT-7000 under 2.2.6-stable. And i can't say: `It works perfectly!` :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 4 06:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00738 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 06:28:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00723; Sat, 4 Jul 1998 06:28:37 -0700 (PDT) (envelope-from wjw@surf.IAE.nl) Received: from surf.IAE.nl (root@surf.IAEhv.nl [194.151.66.2]) by IAEhv.nl (8.8.7/8.8.7) with ESMTP id PAA21772; Sat, 4 Jul 1998 15:28:37 +0200 (CEST) Received: (from wjw@localhost) by surf.IAE.nl (8.8.7/8.8.7) id PAA26905; Sat, 4 Jul 1998 15:28:37 +0200 (MET DST) Date: Sat, 4 Jul 1998 15:28:37 +0200 (MET DST) From: Willem Jan Withagen Message-Id: <199807041328.PAA26905@surf.IAE.nl> To: hackers@FreeBSD.ORG Subject: Re: Apollo tapes (was: Variant Link implementation, continued) X-Newsgroups: list.freebsd.hackers In-Reply-To: <199807030025.TAA18925@nospam.hiwaay.net> References: Organization: Internet Access Eindhoven, the Netherlands Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199807030025.TAA18925@nospam.hiwaay.net> you write: >Willem Jan Withagen writes: >> You ( David Kelly ) write: >> => For dd its "conv=swab". >> => >> => To duplicate your tapes use tcopy(1) if you have two tape drives. Tcopy >> >> Well I can't even dd them of either tape. So I've haven't een gotten into >> data incompatibility issues >> Julian suggested RTFM 'mt blocksize'. Which I'll as soon as I reboot to >> get the tape operational on my FreeBSD box. > >They were written on 4mm DAT? Not something weird like QIC-100? Saw an >HP "development system" which wrote QIC-100 format to DC-6150 tapes, I >think. Tapes had to be formatted. Then they mounted like a filesystem. >Slower than a tax refund. > >In the early bad old days of DAT (more correctly known as DSS) there >were more problems than there should have been with one tape drive not >being able to read tapes from another, all other things the same. Oke, My drive is again on line: [~] wjw@digi> mt stat Present Mode: Density = X3B5/88-185A Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3.136-1986 Blocksize = 512 bytes Mode 2: Density = X3.39-1986 Blocksize variable Mode 3: Density = X3.54-1986 Blocksize variable looking at: man mt: The different density codes are as follows: 0x0 default for device 0xE reserved for ECMA Value Tracks Density(bpi) Code Type Reference Note ........ 0x13 1 61000 DDS CS X3B5/88-185A 4 0x14 1 43245 RLL CS X3.202-1991 4 0x15 1 45434 RLL CS ECMA TC17 4 Which are 3 DAT formats. And thus it is a DDS-coded tape. And thus: How do I read this tape on a: (ncr0:6:0): "HP HP35480A T603" type 1 removable SCSI 2 st0(ncr0:6:0): Sequential-Access I've tried: mt density 0x13 but that buys me very little st0(ncr0:6:0): COMMAND FAILED (4 88) @f0697400. st0(ncr0:6:0): COMMAND FAILED (4 88) @f0697400. st0(ncr0:6:0): Deferred Error: MEDIUM ERROR asc:3b,0 Sequential positioning error Anybody with more suggestions?? (other than finding the "old" tapedrive) --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 4 07:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05989 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 07:33:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05984 for ; Sat, 4 Jul 1998 07:33:42 -0700 (PDT) (envelope-from rln@ludd.luth.se) Received: from father.ludd.luth.se (rln@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id QAA19109 for ; Sat, 4 Jul 1998 16:33:43 +0200 From: Rolf Larsson Received: (rln@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id QAA13909 for freebsd-scsi@freebsd.org; Sat, 4 Jul 1998 16:33:42 +0200 Message-Id: <199807041433.QAA13909@father.ludd.luth.se> Subject: Two problems (Ultra2-performance and CD-recording) To: freebsd-scsi@FreeBSD.ORG Date: Sat, 4 Jul 1998 16:33:42 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM899562821-13706-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM899562821-13706-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello people, I have two problems which I suspect may be related to CAM. The system in question is a twin-CPU PII-400 with 256MB ECC memory and an on-board Adaptec 7890 controller with a Seagate Cheetah Ultra2-LW disk and a Yamaha CD-R 4260t CD-writer. (entire dmesg & config attached below) Source is 3.0-SNAP-980520 with the CAM patches from the same day. Problem 1: I can't get the performance I want out of the disk. Probing when booting shows: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number LJ01239200001840H6VQ da0: 6.600MB/s transfers , 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) However, running camcontrol -i after booting gives me: [root@habanero] /sys/i386/conf > camcontrol -i Fixed Direct Access SCSI2 device Serial Number LJ01239200001840H6VQ 80.0MB/s transfers (40.0MHz, offset 0, 16bit), Tagged Queueing Enabled which seems more reasonable (to me at least). Playing around with bonnie, dd, etc gives no more than 5.2 MB/s throughput. This is both with and without the CD-burner attached, so it is not the cause of the problem. I would be happy to try out any ideas you have. Problem 2: The CD-writer doesn't show up when booting. I am clueless on this one, and would appreciate any hints (including "you have forgotten to add option FOO, stupid!" :-) that may help us in getting it going. Thank you, -- Rolf Larsson http://www.ludd.luth.se/~rln/ --ELM899562821-13706-0_ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename=habanero.dmesg Content-Description: habanero.dmesg Content-Transfer-Encoding: 7bit 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-980520-SNAP #6: Tue Jun 23 11:23:31 CEST 1998 rln@habanero.marratech.com:/usr/src/sys/compile/HABANERO Timecounter "i8254" frequency 1193182 Hz cost 3034 ns CPU: Pentium Pro (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff,MMX,> real memory = 268435456 (262144K bytes) avail memory = 258207744 (252156K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 int d irq 10 on pci0.4.2 chip4: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 10 on pci0.6.0 ahc0: Using left over BIOS settings ahc0: aic7890/91 Wide Channel A, SCSI Id=15, 32/255 SCBs vga0: rev 0x54 int a irq 10 on pci0.9.0 de0: rev 0x22 int a irq 11 on pci0.10.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:80:c8:47:6d:31 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A 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 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 DEVFS: ready to run struct nfsmount bloated (> 512bytes) Try reducing NFS_MUIDHASHSIZ ccd0-3: Concatenated disk drivers de0: enabling 100baseTX port changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number LJ01239200001840H6VQ da0: 6.600MB/s transfers , 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) (da0:ahc0:0:0:0): tagged openings now 58 (da0:ahc0:0:0:0): tagged openings now 57 (da0:ahc0:0:0:0): tagged openings now 56 (da0:ahc0:0:0:0): tagged openings now 55 (da0:ahc0:0:0:0): tagged openings now 54 (da0:ahc0:0:0:0): tagged openings now 53 (da0:ahc0:0:0:0): tagged openings now 52 (da0:ahc0:0:0:0): tagged openings now 51 (da0:ahc0:0:0:0): tagged openings now 50 (da0:ahc0:0:0:0): tagged openings now 49 --ELM899562821-13706-0_ Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: attachment; filename=habanero.conf Content-Description: habanero.conf Content-Transfer-Encoding: 7bit # # SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: SMP-GENERIC,v 1.12 1998/04/29 06:58:43 max Exp $ machine "i386" # SMP does NOT support 386/486 CPUs. #cpu "I386_CPU" #cpu "I486_CPU" #cpu "I586_CPU" cpu "I686_CPU" ident HABANERO maxusers 42 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs # Lets always enable the kernel debugger for SMP. options DDB # SMP shouldn't need x87 emulation, disable by default. #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options DEVFS config kernel root on da1s1 controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? disable port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? disable port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller isp0 options AHC_ALLOW_MEMIO options AHC_SHARE_SCBS #options AHC_SCBPAGING_ENABLE #options AHC_TAGENABLE #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device da0 #device od0 #See LINT for possible `od' options. device sa0 device pass9 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device fxp0 device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ie1 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr pseudo-device loop pseudo-device ether pseudo-device sl 1 # iijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 4 pseudo-device bpfilter 4 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" options DDB_UNATTENDED options UCONSOLE options MROUTING options FDESC options MFS options UNION #device worm0 at scbus? # SCSI worm pseudo-device ccd 4 #Concatenated disk driver pseudo-device su options "IBCS2" options COMPAT_LINUX --ELM899562821-13706-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 4 11:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25219 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 11:38:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25203; Sat, 4 Jul 1998 11:38:33 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA25911; Sat, 4 Jul 1998 11:33:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd025906; Sat Jul 4 18:33:33 1998 Date: Sat, 4 Jul 1998 11:33:29 -0700 (PDT) From: Julian Elischer To: Willem Jan Withagen cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Apollo tapes (was: Variant Link implementation, continued) In-Reply-To: <199807041328.PAA26905@surf.IAE.nl> 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 It is already running in that mode.. rememberr the four devices rst0.0 thru rst0.3 have the fixed modes mentionned (though you can change each..) and rst0 has the DEFAULT mode so try a few different densities (even past 0x18) and see which ones the DRIVE accepts. also then try setting blocksize to 512 (since that's what you think you wrote) On Sat, 4 Jul 1998, Willem Jan Withagen wrote: > In article <199807030025.TAA18925@nospam.hiwaay.net> you write: > > Oke, My drive is again on line: > > [~] wjw@digi> mt stat > Present Mode: Density = X3B5/88-185A Blocksize variable > ---------available modes--------- > Mode 0: Density = 0x00 Blocksize variable > Mode 1: Density = X3.136-1986 Blocksize = 512 bytes > Mode 2: Density = X3.39-1986 Blocksize variable > Mode 3: Density = X3.54-1986 Blocksize variable > > looking at: man mt: > The different density codes are as follows: > > 0x0 default for device > 0xE reserved for ECMA > > Value Tracks Density(bpi) Code Type Reference Note > ........ > 0x13 1 61000 DDS CS X3B5/88-185A 4 > 0x14 1 43245 RLL CS X3.202-1991 4 > 0x15 1 45434 RLL CS ECMA TC17 4 > no, they are set from the drive type not the tape. The DEFAULT mode is what the drive thinks is there, but you might try teh others in case it is wrong.. > Which are 3 DAT formats. And thus it is a DDS-coded tape. > > And thus: > How do I read this tape on a: > (ncr0:6:0): "HP HP35480A T603" type 1 removable SCSI 2 > st0(ncr0:6:0): Sequential-Access > > I've tried: > mt density 0x13 > but that buys me very little > st0(ncr0:6:0): COMMAND FAILED (4 88) @f0697400. > st0(ncr0:6:0): COMMAND FAILED (4 88) @f0697400. > st0(ncr0:6:0): Deferred Error: MEDIUM ERROR asc:3b,0 Sequential positioning > error > > Anybody with more suggestions?? (other than finding the "old" tapedrive) obviously it is NOT 0x13.. try 0x14 and 0x15 julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 4 18:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03845 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 18:16:55 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03839; Sat, 4 Jul 1998 18:16:49 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id KAA17365; Sun, 5 Jul 1998 10:46:48 +0930 (CST) Message-ID: <19980705104647.O358@freebie.lemis.com> Date: Sun, 5 Jul 1998 10:46:47 +0930 From: Greg Lehey To: Willem Jan Withagen , hackers@FreeBSD.ORG Cc: scsi@FreeBSD.ORG Subject: Re: Apollo tapes (was: Variant Link implementation, continued) References: <199807030025.TAA18925@nospam.hiwaay.net> <199807041328.PAA26905@surf.IAE.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807041328.PAA26905@surf.IAE.nl>; from Willem Jan Withagen on Sat, Jul 04, 1998 at 03:28:37PM +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 Saturday, 4 July 1998 at 15:28:37 +0200, Willem Jan Withagen wrote: > In article <199807030025.TAA18925@nospam.hiwaay.net> you write: >> In the early bad old days of DAT (more correctly known as DSS) there >> were more problems than there should have been with one tape drive not >> being able to read tapes from another, all other things the same. > > Oke, My drive is again on line: > > [~] wjw@digi> mt stat > Present Mode: Density = X3B5/88-185A Blocksize variable > ---------available modes--------- > Mode 0: Density = 0x00 Blocksize variable > Mode 1: Density = X3.136-1986 Blocksize = 512 bytes > Mode 2: Density = X3.39-1986 Blocksize variable > Mode 3: Density = X3.54-1986 Blocksize variable > > looking at: man mt: > The different density codes are as follows: > > 0x0 default for device > 0xE reserved for ECMA > > Value Tracks Density(bpi) Code Type Reference Note > ........ > 0x13 1 61000 DDS CS X3B5/88-185A 4 > 0x14 1 43245 RLL CS X3.202-1991 4 > 0x15 1 45434 RLL CS ECMA TC17 4 > > Which are 3 DAT formats. And thus it is a DDS-coded tape. This describes the tape unit, not the tape. We've already established that it can't read the tape. > Anybody with more suggestions?? (other than finding the "old" tapedrive) Give up? Or send them to Mike? 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 Sat Jul 4 19:49:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12087 for freebsd-scsi-outgoing; Sat, 4 Jul 1998 19:49:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12076 for ; Sat, 4 Jul 1998 19:49:30 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id MAA18320; Sun, 5 Jul 1998 12:18:30 +0930 (CST) Message-ID: <19980705121830.B358@freebie.lemis.com> Date: Sun, 5 Jul 1998 12:18:30 +0930 From: Greg Lehey To: Ustimenko Semen , David Kelly Cc: Harlan Stenn , dc-sage@dc-sage.org, scsi@FreeBSD.ORG, amanda-users@cs.umd.edu Subject: Re: DDS/2 tape specs References: <199807032016.PAA21647@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Ustimenko Semen on Sat, Jul 04, 1998 at 03:34:28PM +0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 4 July 1998 at 15:34:28 +0700, Ustimenko Semen wrote: > On Fri, 3 Jul 1998, David Kelly wrote: >> Harlan Stenn writes: >>> My second test took 8191 `y' characters followed by a newline: >>> >>>> yes `cat 8ky` | dd bs=8k of=/dev/rst0 >>> >>> and I eventually killed after over 24 hours' elapsed time. >>> When I killed it, I think it claimed to have written nearly 10G to the tape. That's reasonable. You've chosen an almost ideal pattern for compression. >> 24 hrs for only 10G doesn't sound good. >> >> To a similar DDS-2 (with compression) drive I once used dd to copy >> /dev/null until something broke. Got 88G on a DDS-1 90m tape. Took >> about 8 hours. SGI Indy R5000, Irix 6.2, OEM SGI/Seagate/Archive DDS-2 >> tape drive. > > Yes, in good times it writes real fs data on 500-800 Kb/s. > But in worst, it goes on 20-80 Kb/s :-( > > Else total capacity and speed decrease after you use tape many > times without eraseing it and/or cleaning drive's head. No, the capacity stays the same. But if you don't clean the head, it'll have more and more soft errors, and the throughput will drop dramatically. > IMHO there are linear dependence between data speed and cartridge > capacity (becouse the tape speed is fixed). Tape speed is fixed, but that doesn't mean that it's moving all the time. If the drive gets a data underrun on write, it'll stop, back up, and start again. This can drop its speed by 95% or more. This will also happen on I/O errors. This is obviously what's been happening to you. > I'm useing SDT-7000 under 2.2.6-stable. And i can't say: > `It works perfectly!` :-( Not surprising. 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