From owner-freebsd-scsi Sun Dec 20 10:22:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05385 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 10:22:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05368 for ; Sun, 20 Dec 1998 10:22:08 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id TAA29846; Sun, 20 Dec 1998 19:21:40 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id TAA17864; Sun, 20 Dec 1998 19:20:27 +0100 (MET) (envelope-from j) Message-ID: <19981220192026.11233@uriah.heep.sax.de> Date: Sun, 20 Dec 1998 19:20:26 +0100 From: J Wunsch To: Harlan Stenn Cc: scsi@FreeBSD.ORG Subject: Re: Problem with Amanda backups to 4mm tape Reply-To: Joerg Wunsch References: <29914.914136169@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <29914.914136169@brown.pfcs.com>; from Harlan Stenn on Sun, Dec 20, 1998 at 01:42:49AM -0500 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Harlan Stenn wrote: > Dec 19 22:10:57 pcfb1 /kernel: st1(ahc0:5:0): Target Busy > Dec 19 22:10:57 pcfb1 last message repeated 5 times Seems that Amanda is trying to open the tape while it's not yet ready (e. g. rewinding). The tape rejects the operation, and the driver doesn't wait until it's ready either. IMHO you can modify the behaviour with the little DIP switches, but i don't have any docs about them (at least that's been the case for the HP parts). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 20 10:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06985 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 10:31:20 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06933 for ; Sun, 20 Dec 1998 10:31:15 -0800 (PST) (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 ; Sun, 20 Dec 1998 13:31:03 -0500 (EST) 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 ; Sun, 20 Dec 1998 10:31:01 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 20 Dec 1998 13:31:00 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Joerg Wunsch cc: Harlan Stenn , scsi@FreeBSD.ORG Subject: Re: Problem with Amanda backups to 4mm tape In-Reply-To: J Wunsch's (j@uriah.heep.sax.de) message dated Sun, 20 Dec 1998 19:20:26. <19981220192026.11233@uriah.heep.sax.de> 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: Sun, 20 Dec 1998 13:31:00 -0500 Message-ID: <18936.914178660@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J"org, Thanks for the response. I have some of the docs for the tape drive here. How do I want the drive to behave? Should I look at the driver and add a quirk entry to increase a timeout value? Is there some SCSI debugging/verbosity I can turn on to help find this problem? I'm also wondering if I should spend the effort to put a similar tape drive into a -current system I have, just to see how CAM handles things. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 20 12:34:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18315 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 12:34:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18310 for ; Sun, 20 Dec 1998 12:34:27 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id MAA10252; Sun, 20 Dec 1998 12:34:22 -0800 (PST) Date: Sun, 20 Dec 1998 12:34:22 -0800 (PST) From: Chris Timmons To: Jeroen Ruigrok/Asmodai cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with SCSI-bus and high diskaccess? 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 [moved to -scsi] I am assuming that you posted to -current because you just cvsupped the latest 3.0-current bits and are running that. Else freebsd-scsi would be a good list for this kind of problem (be sure to say what version of FreeBSD you are running.) Although I haven't seen this sort of thing with a fireball, it reeks of quantum firmware. I have had similar problems with atlas-I and atlas-II drives. So you will want to check your firmware revision and see if there is something newer out at ftp.quantum.com (upgrading firmware is a fun way to waste a day.) You might try www.dejanews.com and search for your drive name and firmware revision. Chances are somebody else has already seen and documented a similar problem if it is indeed the drives. There is also a slight possibility that you are using an old enough version of FreeBSD and perhaps an integrated aha-2940UW on your mb (or perhaps the dreaded rev e(?) of the pci card. In that case, Justin committed fixes to the drivers months ago. Update your system. I find that IBM and Seagate drives work very well and come with firmware that works right the first time. Your mileage may vary :) -Chris On Sun, 20 Dec 1998, Jeroen Ruigrok/Asmodai wrote: > Hi, > > I just want some thoughts on this: > > In the last 24 hours my workstation is been going nuts, whereas it has been > running along nicely for weeks before. > > The things that kept me bugging today were these happy messages: > > Dec 20 10:51:14 chronias /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Dec 20 10:51:15 chronias /kernel: SEQADDR == 0x157 > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): SCB 0x5 - timed out while > idle, LASTPHASE == 0x1, SEQADDR == 0xc > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): no longer in timeout, status > = 353 > > After which page and swap process were running wild. > > The weird thing is, these HD's (two SCSI Quantum Fireballs) have been checked, the > HA (AHA 2940UW) is likewise in good shape and the memory chips have been tested as > well... The mainboard is also in good shape and is cooled by a few fans (3) which > all work, including the one on the CPU. > > The circumstances when this happened was when I did a locate.updatedb at the same > time as downloading a PDF file to the HD, and then I opened a mailbox at which > time the whole time went haywire... > > Unfortunately I wasn't able to write down the pager messages since they went by > with warpspeed 9 and they weren't logged in /var/log/messages =\ > > Does anybody have any ideas what to check to narrow down the problem? > > --- > Jeroen Ruigrok van der Werven Life is the only Pain > asmodai(at)wxs.nl we endeavour... > Network/Security Specialist > BSD & picoBSD: The Power to Serve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 20 13:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21907 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 13:14:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21866 for ; Sun, 20 Dec 1998 13:13:47 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.171]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA69C0; Sun, 20 Dec 1998 22:13:38 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 20 Dec 1998 22:19:57 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Chris Timmons Subject: Re: Problem with SCSI-bus and high diskaccess? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Dec-98 Chris Timmons wrote: > > [moved to -scsi] > > I am assuming that you posted to -current because you just cvsupped the > latest 3.0-current bits and are running that. Else freebsd-scsi would be > a good list for this kind of problem (be sure to say what version of > FreeBSD you are running.) Sorry, my bad... I did it because I thought I might be more related to current than scsi =\ Especially regarding the following pager messages, which might be in effect of not being able to write to the HD after the problem occured. I did some heavy disk access later on again and now my X completely froze, moused as well and after some seconds the whole thing rebooted spontaneously. No logs. As I said, the memory is fine, I never got SIG 11's, plus it has been tested recently. I reseated all the crap that can be reseated =) > Although I haven't seen this sort of thing with a fireball, it reeks of > quantum firmware. I have had similar problems with atlas-I and atlas-II > drives. So you will want to check your firmware revision and see if there > is something newer out at ftp.quantum.com (upgrading firmware is a fun way > to waste a day.) You might try www.dejanews.com and search for your drive > name and firmware revision. Chances are somebody else has already seen > and documented a similar problem if it is indeed the drives. OK, I am not dirty of updating firmware... Didn't even know HD's could be updated ;) And offcourse... Fireballs don't have firmware updates =\ ftp://ftp.quantum.com/Disk_Firmware/ ahc0: rev 0x00 int a irq 11 on pci0.17.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) > There is also a slight possibility that you are using an old enough > version of FreeBSD and perhaps an integrated aha-2940UW on your mb (or > perhaps the dreaded rev e(?) of the pci card. In that case, Justin > committed fixes to the drivers months ago. Update your system. Sorry, I forgot to post my version: [chronias] asmodai $ uname -a FreeBSD chronias.ninth-circle.org 3.0-CURRENT FreeBSD 3.0-CURRENT #20: Wed Dec 16 07:21:00 CET 1998 asmodai@chronias.ninth-circle.org:/work/cvs/src/sys/compile/CHRONIAS i386 And no, it ain't an integrated AHA... It's a PCI card, from the original kit, not the OEM version. I think the BIOS version is 1.2x just don't know what the x was, I thought 6 or 7 > I find that IBM and Seagate drives work very well and come with firmware > that works right the first time. Your mileage may vary :) Never had problems with Quantums before... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 20 18:49:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23620 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 18:49:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23615 for ; Sun, 20 Dec 1998 18:49:13 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA94760; Sun, 20 Dec 1998 19:47:51 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812210247.TAA94760@panzer.plutotech.com> Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: from Chris Timmons at "Dec 20, 98 12:34:22 pm" To: skynyrd@opus.cts.cwu.edu (Chris Timmons) Date: Sun, 20 Dec 1998 19:47:51 -0700 (MST) Cc: asmodai@wxs.nl, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Timmons wrote... > > [moved to -scsi] > > I am assuming that you posted to -current because you just cvsupped the > latest 3.0-current bits and are running that. Else freebsd-scsi would be > a good list for this kind of problem (be sure to say what version of > FreeBSD you are running.) Yep, it's best to post to -scsi with SCSI problems. > Although I haven't seen this sort of thing with a fireball, it reeks of > quantum firmware. I have had similar problems with atlas-I and atlas-II > drives. So you will want to check your firmware revision and see if there > is something newer out at ftp.quantum.com (upgrading firmware is a fun way > to waste a day.) You might try www.dejanews.com and search for your drive > name and firmware revision. Chances are somebody else has already seen > and documented a similar problem if it is indeed the drives. Yes, it looks like a firmware issue, most likely. > There is also a slight possibility that you are using an old enough > version of FreeBSD and perhaps an integrated aha-2940UW on your mb (or > perhaps the dreaded rev e(?) of the pci card. In that case, Justin > committed fixes to the drivers months ago. Update your system. True, that could be it. From his later message, though, we know that that isn't the problem. > I find that IBM and Seagate drives work very well and come with firmware Yep, they definitely seem to write better firmware. > On Sun, 20 Dec 1998, Jeroen Ruigrok/Asmodai wrote: > > > Hi, > > > > I just want some thoughts on this: > > > > In the last 24 hours my workstation is been going nuts, whereas it has been > > running along nicely for weeks before. > > > > The things that kept me bugging today were these happy messages: > > > > Dec 20 10:51:14 chronias /kernel: Unexpected busfree. LASTPHASE == 0xa0 > > Dec 20 10:51:15 chronias /kernel: SEQADDR == 0x157 > > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): SCB 0x5 - timed out while > > idle, LASTPHASE == 0x1, SEQADDR == 0xc > > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB > > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent > > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): no longer in timeout, status > > = 353 This indicates that the drive is having trouble. The timed out while idle problem generally happens when the drive doesn't respond to a command in the specified period of time. The default read/write timeout in the da driver is 60 seconds, which should be way more than enough time for the drive to respond. When the drive timed out, we hit it over the head with a BDR to wake it up. Usually, that will wake the drive up and get things going again. > > After which page and swap process were running wild. > > > > The weird thing is, these HD's (two SCSI Quantum Fireballs) have been checked, the > > HA (AHA 2940UW) is likewise in good shape and the memory chips have been tested as > > well... The mainboard is also in good shape and is cooled by a few fans (3) which > > all work, including the one on the CPU. > > > > The circumstances when this happened was when I did a locate.updatedb at the same > > time as downloading a PDF file to the HD, and then I opened a mailbox at which > > time the whole time went haywire... > > > > Unfortunately I wasn't able to write down the pager messages since they went by > > with warpspeed 9 and they weren't logged in /var/log/messages =\ > > > > Does anybody have any ideas what to check to narrow down the problem? The problem is probably just: Quantum Firmware + High Load == Drive goes out to lunch. With Quantum disks, the problem generally happens under high load. Chris is right, the Atlas I and Atlas II had problems like this as well. The latest firmware for the Atlas II at least has solved some of the problems, but not all. I believe the LYK8 Atlas II firmware has mostly solved the "drive goes out to lunch" problem. It hasn't solved the problem that causes it to continually return queue full until we have reduced the number of tags to the minimum. That's why we have Atlas II quirk entries setting the minimum number of tags to 24. I know that we (Pluto) have had trouble with the Fireball ST drives in the past in certain situations. (can't remember exactly what those situations were) I believe, though, that the '0F0J' firmware worked reasonably well. 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 Sun Dec 20 19:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24535 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 19:03:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24519 for ; Sun, 20 Dec 1998 19:03:54 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id UAA94802; Sun, 20 Dec 1998 20:02:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812210302.UAA94802@panzer.plutotech.com> Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 20, 98 10:19:57 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sun, 20 Dec 1998 20:02:32 -0700 (MST) Cc: skynyrd@opus.cts.cwu.edu, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai wrote... > On 20-Dec-98 Chris Timmons wrote: > > > > [moved to -scsi] > > > > I am assuming that you posted to -current because you just cvsupped the > > latest 3.0-current bits and are running that. Else freebsd-scsi would be > > a good list for this kind of problem (be sure to say what version of > > FreeBSD you are running.) > > Sorry, my bad... I did it because I thought I might be more related to current > than scsi =\ Especially regarding the following pager messages, which might be in > effect of not being able to write to the HD after the problem occured. > > I did some heavy disk access later on again and now my X completely froze, moused > as well and after some seconds the whole thing rebooted spontaneously. No logs. Well, if you were swapping at the time, it would certainly cause problems if your disk stopped responding. > As I said, the memory is fine, I never got SIG 11's, plus it has been tested > recently. I reseated all the crap that can be reseated =) Good idea. If you've got a second machine, it might be worthwhile to setup a serial console to catch any error messages that are printed out. I find it quite helpful with one of my machines at home. (I was having NMI problems, generally while in X, but I couldn't figure out exactly why until I put a serial console on the box. It turned out that although I was within the specs as far as the number of memory chips per SIMM, I was probably > > Although I haven't seen this sort of thing with a fireball, it reeks of > > quantum firmware. I have had similar problems with atlas-I and atlas-II > > drives. So you will want to check your firmware revision and see if there > > is something newer out at ftp.quantum.com (upgrading firmware is a fun way > > to waste a day.) You might try www.dejanews.com and search for your drive > > name and firmware revision. Chances are somebody else has already seen > > and documented a similar problem if it is indeed the drives. > > OK, I am not dirty of updating firmware... Didn't even know HD's could be updated > ;) > > And offcourse... Fireballs don't have firmware updates =\ > > ftp://ftp.quantum.com/Disk_Firmware/ Bummer. You might want to talk to Quantum about it...more below. > ahc0: rev 0x00 int a irq 11 on pci0.17.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) I know there is later firmware than that for the Fireball ST. I believe the drives we have at work that "work" have the 0F0J firmware revision. (the machine with the drives in question is down at the moment, so I can't check to be sure) Try calling Quantum Tech support and see if you can get them to give you a newer firmware revision. > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > da0: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) Dunno about this one. I'm not sure what sort of Fireball it is. > > There is also a slight possibility that you are using an old enough > > version of FreeBSD and perhaps an integrated aha-2940UW on your mb (or > > perhaps the dreaded rev e(?) of the pci card. In that case, Justin > > committed fixes to the drivers months ago. Update your system. > > Sorry, I forgot to post my version: > > [chronias] asmodai $ uname -a > FreeBSD chronias.ninth-circle.org 3.0-CURRENT FreeBSD 3.0-CURRENT #20: Wed Dec 16 > 07:21:00 CET 1998 > asmodai@chronias.ninth-circle.org:/work/cvs/src/sys/compile/CHRONIAS i386 > > And no, it ain't an integrated AHA... It's a PCI card, from the original kit, not > the OEM version. I think the BIOS version is 1.2x just don't know what the x was, > I thought 6 or 7 Well, don't worry about the Rev E/Rev B problem, Justin worked around it last summer, so what you're running is certainly new enough. > > I find that IBM and Seagate drives work very well and come with firmware > > that works right the first time. Your mileage may vary :) > > Never had problems with Quantums before... Then you've probably never pushed them very hard. I'm personally curious to see whether their newer drives (e.g. Atlas III, Atlas IV, Atlas 10K) have the same sorts of problems that their older drives did. I'm certainly not willing, however, to spend any money to find out. :) 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 Dec 21 15:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09267 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 15:19:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iserver.itworks.com.au (iserver.itworks.com.au [203.32.61.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09262 for ; Mon, 21 Dec 1998 15:19:04 -0800 (PST) (envelope-from gavin@itworks.com.au) Received: from localhost (gavin@localhost) by iserver.itworks.com.au (8.8.8/8.8.8) with SMTP id KAA05932 for ; Tue, 22 Dec 1998 10:18:52 +1100 (EST) (envelope-from gavin@itworks.com.au) Date: Tue, 22 Dec 1998 10:18:52 +1100 (EST) From: Gavin Cameron To: scsi@FreeBSD.ORG Subject: DPT problems 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 get a new server up and running and my DPT PM2144UW with raid gives me the following errors when I use the tape drive for an small amount of time (5 minutes)... I have 2 wide harddisks on the wide connector and a cd and a tape hanging of the 8-bit connector. Termination is set to "high only" The errors are: dpt0 ERROR: Marking 54402 (Unknown SCSI command) on c0b0t6u0 as late after 18813435usec dpt0 ERROR: Stale 54402 (Unknown SCSI command on c0b0t6u0 (28813435) gets another chance(1/5) dpt0: f1a20e00 is not in the SUBMITTED queue dpt0: f1a20e00 is in the FREE queue DPT options that I have enabled are Verify lost transactions Collect Metrics Handle Timeouts I'm using 2.2.7-RELEASE. Anyone have any idea? Thanks Gavin []-----------------------------------+------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : 0418 390350 | Suite 100, 85 Grattan Street | | Fax : +61 3 9347 6544 | Carlton, Victoria | | Email : gavin@itworks.com.au | Australia, 3053 | []-----------------------------------+------------------------------------[] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 21 16:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20184 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 16:36:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20179 for ; Mon, 21 Dec 1998 16:36:42 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.219]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5B75; Mon, 21 Dec 1998 22:14:12 +0100 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: <199812210302.UAA94802@panzer.plutotech.com> Date: Wed, 21 Jan 1998 22:20:35 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Kenneth D. Merry" Subject: Re: Problem with SCSI-bus and high diskaccess? Cc: freebsd-scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 21-Dec-98 Kenneth D. Merry wrote: > Jeroen Ruigrok/Asmodai wrote... >> On 20-Dec-98 Chris Timmons wrote: >> As I said, the memory is fine, I never got SIG 11's, plus it has been tested >> recently. I reseated all the crap that can be reseated =) > > Good idea. If you've got a second machine, it might be worthwhile to setup > a serial console to catch any error messages that are printed out. I find > it quite helpful with one of my machines at home. (I was having NMI > problems, generally while in X, but I couldn't figure out exactly why until > I put a serial console on the box. It turned out that although I was > within the specs as far as the number of memory chips per SIMM, I was > probably was probably what? =) I will try to get this spare 486 up and running... >> And offcourse... Fireballs don't have firmware updates =\ >> >> ftp://ftp.quantum.com/Disk_Firmware/ > > Bummer. You might want to talk to Quantum about it...more below. > > I know there is later firmware than that for the Fireball ST. I believe > the drives we have at work that "work" have the 0F0J firmware revision. > (the machine with the drives in question is down at the moment, so I can't > check to be sure) Try calling Quantum Tech support and see if you can > get them to give you a newer firmware revision. I am going to try this, if the US didn't decide on dropping some major SAPs so that quantum.com was unreachable =\ --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 21 19:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09363 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 19:10:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09358 for ; Mon, 21 Dec 1998 19:10:22 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA99349; Mon, 21 Dec 1998 19:57:46 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812220257.TAA99349@panzer.plutotech.com> Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: from Jeroen Ruigrok/Asmodai at "Jan 21, 98 10:20:35 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Mon, 21 Dec 1998 19:57:46 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai wrote... > On 21-Dec-98 Kenneth D. Merry wrote: > > Jeroen Ruigrok/Asmodai wrote... > >> On 20-Dec-98 Chris Timmons wrote: > > >> As I said, the memory is fine, I never got SIG 11's, plus it has been tested > >> recently. I reseated all the crap that can be reseated =) > > > > Good idea. If you've got a second machine, it might be worthwhile to setup > > a serial console to catch any error messages that are printed out. I find > > it quite helpful with one of my machines at home. (I was having NMI > > problems, generally while in X, but I couldn't figure out exactly why until > > I put a serial console on the box. It turned out that although I was > > within the specs as far as the number of memory chips per SIMM, I was > > probably > > was probably what? =) Oops. I was probably exceeding the amount of capacitance the memory subsystem on my motherboard could take. It's an ASUS P/I-P65UP5 with a C-P6ND CPU card. It has 8 SIMM slots. Theoretically, I think you're not supposed to have an average of more than 24 chips per SIMM. I had 8 32MB SIMMs, each with 24 chips on them. So, although I met the specifications, I think I probably just slightly exceeded the amount of load the memory subsystem could take. I would get periodic NMI's. They were just "generic" NMIs, not parity errors. (I had parity SIMMs on board.) Whenever I've had parity problems in the past, FreeBSD's NMI panic message has always said "RAM parity error". Anyway, I took out two of the 8 SIMMs, and things work fine now. Unfortunately, I have 192MB in the machine, and 64MB on the shelf now. > I will try to get this spare 486 up and running... It'll certainly help you find the source of the panics if you have a serial console. (especially if you tend to be running X when the panics occur) > >> And offcourse... Fireballs don't have firmware updates =\ > >> > >> ftp://ftp.quantum.com/Disk_Firmware/ > > > > Bummer. You might want to talk to Quantum about it...more below. > > > > I know there is later firmware than that for the Fireball ST. I believe > > the drives we have at work that "work" have the 0F0J firmware revision. > > (the machine with the drives in question is down at the moment, so I can't > > check to be sure) Try calling Quantum Tech support and see if you can > > get them to give you a newer firmware revision. > > I am going to try this, if the US didn't decide on dropping some major SAPs so > that quantum.com was unreachable =\ SAPs? What's that? (I've heard of SAMs, Cruise Missiles, AAA, and lots of other stuff, but the only two "SAP" things that come to mind are the kind that comes out of trees, and the German software company.) BTW, is there any particular reason that the date on your computer is set to January 21, 1998? (I noticed, because my mailer is set to sort based on message date.) 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 Dec 21 21:07:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26358 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 21:07:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26353 for ; Mon, 21 Dec 1998 21:07:37 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id VAA23619; Mon, 21 Dec 1998 21:07:30 -0800 (PST) Date: Mon, 21 Dec 1998 21:07:30 -0800 (PST) From: Chris Timmons To: "Kenneth D. Merry" cc: Jeroen Ruigrok/Asmodai , freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: <199812220257.TAA99349@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Heh... I guess you've never worked in the presence of the "Red Menace" (Novell). SAP is also an obnoxious "service advertisement protocol" in addition to evertything else those letters stand for. Stop me before I tell you about internal network numbers (blarf :) I don't think that's what Jeroen was talking about, however... On Mon, 21 Dec 1998, Kenneth D. Merry wrote: > SAPs? What's that? (I've heard of SAMs, Cruise Missiles, AAA, and lots of > other stuff, but the only two "SAP" things that come to mind are the kind > that comes out of trees, and the German software company.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 21 22:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02579 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 22:01:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02570 for ; Mon, 21 Dec 1998 22:01:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.190]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA2A2E; Tue, 22 Dec 1998 07:01:12 +0100 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: <199812220257.TAA99349@panzer.plutotech.com> Date: Tue, 22 Dec 1998 07:07:35 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Kenneth D. Merry" Subject: Re: Problem with SCSI-bus and high diskaccess? Cc: skynyrd@opus.cts.cwu.edu, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-Dec-98 Kenneth D. Merry wrote: > BTW, is there any particular reason that the date on your computer is set > to January 21, 1998? (I noticed, because my mailer is set to sort based on > message date.) [chronias] asmodai $ date Tue Dec 22 07:05:38 CET 1998 Now this is awkward. My BIOS is year 2000 compliant, so it cannot be (I hope) the thing already acting up. I use XFMail for my mail... Think I am going to need to mail the dude who wrote it and see if he missed anything like this... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 21 22:32:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06561 for freebsd-scsi-outgoing; Mon, 21 Dec 1998 22:32:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06556 for ; Mon, 21 Dec 1998 22:32:54 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id XAA00136; Mon, 21 Dec 1998 23:31:29 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812220631.XAA00136@panzer.plutotech.com> Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 22, 98 07:07:35 am" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Mon, 21 Dec 1998 23:31:29 -0700 (MST) Cc: skynyrd@opus.cts.cwu.edu, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai wrote... > On 22-Dec-98 Kenneth D. Merry wrote: > > BTW, is there any particular reason that the date on your computer is set > > to January 21, 1998? (I noticed, because my mailer is set to sort based on > > message date.) > > [chronias] asmodai $ date > Tue Dec 22 07:05:38 CET 1998 > > Now this is awkward. My BIOS is year 2000 compliant, so it cannot be (I hope) the > thing already acting up. I use XFMail for my mail... > > Think I am going to need to mail the dude who wrote it and see if he missed > anything like this... Well, here is a partial listing of the headers: > 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: <199812210302.UAA94802@panzer.plutotech.com> > Date: Wed, 21 Jan 1998 22:20:35 +0100 (CET) > Organization: Ninth Circle Enterprises > Sender: asmodai@chronias.ninth-circle.org > From: Jeroen Ruigrok/Asmodai > To: "Kenneth D. Merry" > Subject: Re: Problem with SCSI-bus and high diskaccess? > Cc: freebsd-scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu > Content-Transfer-Encoding: 8bit Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 08:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15230 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 08:51:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15225 for ; Tue, 22 Dec 1998 08:51:45 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id RAA00345 for freebsd-scsi@FreeBSD.org; Tue, 22 Dec 1998 17:51:38 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id RAA26511; Tue, 22 Dec 1998 17:31:05 +0100 (MET) (envelope-from j) Message-ID: <19981222173104.28962@uriah.heep.sax.de> Date: Tue, 22 Dec 1998 17:31:04 +0100 From: J Wunsch To: FreeBSD SCSI list Subject: 3.0R && AHA1540A == no go Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, today i've tried to install FreeBSD 3.0R on my scratch machine (that used to run some 2.2.x variant before), and the installation kernel failed with: (waiting 15 seconds blah blah) panic: Inavlid CCB opcode code 3 hccb = 0xf05aad08 (Written down on paper, but the `Inavlid' typo was there -- just as a hint for those who wanna spot it.) This machine has one of the nowadays rare pieces of an AHA1540*A* controller, which used to run well (as well as such an old part could do) until now. Any hints appreciated. A quick glance through the CAM sources didn't reveal me the source code line where the above message is issued. For the time being, i'll now install some 2.2.x system on the machine to have it running again at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 13:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19193 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 13:38:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19132 for ; Tue, 22 Dec 1998 13:38:35 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p108.telia.com [194.236.214.108]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id WAA00528; Tue, 22 Dec 1998 22:38:21 +0100 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id WAA00643; Tue, 22 Dec 1998 22:35:21 +0100 (CET) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199812222135.WAA00643@phoenix.granlund.nu> From: "Johan Granlund" To: "Kenneth D. Merry" Date: Tue, 22 Dec 1998 21:32:14 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Problem with SCSI-bus and high diskaccess? CC: freebsd-scsi@FreeBSD.ORG In-reply-to: <199812210302.UAA94802@panzer.plutotech.com> References: from Jeroen Ruigrok/Asmodai at "Dec 20, 98 10:19:57 pm" X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Never had problems with Quantums before... > > Then you've probably never pushed them very hard. I'm personally curious > to see whether their newer drives (e.g. Atlas III, Atlas IV, Atlas 10K) > have the same sorts of problems that their older drives did. I'm > certainly not willing, however, to spend any money to find out. :) And the answer is...Yes:( My Atlas II failed and got replaced with a Atlas III: da1: Fixed Direct Access SCSI-2 device It starts to reduce tags at 36 (da1:ahc0:0:8:0): tagged openings now 36) ,the same as the Atlas II and mine is now at 2 tags. The following patch fixes this: { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "QM39100*", "*" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 }, /Johan > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 13:43:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23168 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 13:43:11 -0800 (PST) (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 NAA23140 for ; Tue, 22 Dec 1998 13:42:52 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id OAA14499; Tue, 22 Dec 1998 14:34:44 -0700 (MST) Date: Tue, 22 Dec 1998 14:34:44 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812222134.OAA14499@narnia.plutotech.com> To: Joerg Wunsch cc: scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19981222173104.28962@uriah.heep.sax.de> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19981222173104.28962@uriah.heep.sax.de> you wrote: > Hi all, > > today i've tried to install FreeBSD 3.0R on my scratch machine (that > used to run some 2.2.x variant before), and the installation kernel > failed with: > > (waiting 15 seconds blah blah) > panic: Inavlid CCB opcode code 3 hccb = 0xf05aad08 I believe that the 1540A does not support residual calculating CCB opcodes. So, you'd have to modify the driver to use these opcodes on pre-historic devices. Unfortunately it is impossible to get correct underrun information without these opcodes, so you'll have to get creative in this case and you may expose portions of the CAM code that become confused if the residual reported is incorrect. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 14:26:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26950 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 14:26:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA26846 for ; Tue, 22 Dec 1998 14:26:06 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zsaFP-0002Lx-00; Tue, 22 Dec 1998 15:25:47 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id PAA36712; Tue, 22 Dec 1998 15:24:01 -0700 (MST) Message-Id: <199812222224.PAA36712@harmony.village.org> To: Joerg Wunsch Subject: Re: 3.0R && AHA1540A == no go Cc: FreeBSD SCSI list In-reply-to: Your message of "Tue, 22 Dec 1998 17:31:04 +0100." <19981222173104.28962@uriah.heep.sax.de> References: <19981222173104.28962@uriah.heep.sax.de> Date: Tue, 22 Dec 1998 15:24:01 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19981222173104.28962@uriah.heep.sax.de> J Wunsch writes: : This machine has one of the nowadays rare pieces of an AHA1540*A* : controller, which used to run well (as well as such an old part could : do) until now. First, you'll want to try 3.0-current rather than 3.0 release. Many changes to the probing and other things have gone into the aha driver. Second, you may be sol. It is my understanding that residuals are not updated on the 1540A and CAM would not properly work. If you have a driver that is approaching functionality, you should see the message: aha0: Warning: aha-1542A won't likely work. when you boot. CCB opcode code 3 isn't supported on the *A*. I've not looked into the effort taken to use the non-residual version in the driver. INITIATOR_CCB_WRESID is being used when INITIATOR_CCB should be used instead. Likewise with SG_CCB vs SG_CCB_WRESID. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 14:38:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09408 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 14:38:41 -0800 (PST) (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 OAA09380 for ; Tue, 22 Dec 1998 14:38:39 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA17795; Tue, 22 Dec 1998 14:35:52 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA17787; Tue Dec 22 22:35:45 1998 Message-ID: <36801EBB.3F54BC7E@whistle.com> Date: Tue, 22 Dec 1998 14:35:39 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: Joerg Wunsch , scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go References: <199812222134.OAA14499@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > In article <19981222173104.28962@uriah.heep.sax.de> you wrote: > > Hi all, > > > > today i've tried to install FreeBSD 3.0R on my scratch machine (that > > used to run some 2.2.x variant before), and the installation kernel > > failed with: > > > > (waiting 15 seconds blah blah) > > panic: Inavlid CCB opcode code 3 hccb = 0xf05aad08 > > I believe that the 1540A does not support residual calculating > CCB opcodes. So, you'd have to modify the driver to use these > opcodes on pre-historic devices. Unfortunately it is impossible > to get correct underrun information without these opcodes, so you'll > have to get creative in this case and you may expose portions of > the CAM code that become confused if the residual reported is incorrect. > > -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >From memory, the old driver tried to handle this case so you might look there for clues... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 14:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10997 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 14:41:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10924 for ; Tue, 22 Dec 1998 14:41:19 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id PAA01754; Tue, 22 Dec 1998 15:41:02 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199812222241.PAA01754@pluto.plutotech.com> To: Julian Elischer cc: "Justin T. Gibbs" , Joerg Wunsch , scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go In-reply-to: Your message of "Tue, 22 Dec 1998 14:35:39 PST." <36801EBB.3F54BC7E@whistle.com> Date: Tue, 22 Dec 1998 15:33:12 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From memory, the old driver tried to handle this case >so you might look there for clues... The old driver never used the residual reporting opcodes and the SCSI framework in general ignored residual information. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 14:46:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14211 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 14:46:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14129 for ; Tue, 22 Dec 1998 14:46:41 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA02947; Tue, 22 Dec 1998 15:46:33 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812222246.PAA02947@panzer.plutotech.com> Subject: Re: Problem with SCSI-bus and high diskaccess? In-Reply-To: <199812222135.WAA00643@phoenix.granlund.nu> from Johan Granlund at "Dec 22, 98 09:32:14 pm" To: johan@granlund.nu (Johan Granlund) Date: Tue, 22 Dec 1998 15:46:33 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Johan Granlund wrote... > > > Never had problems with Quantums before... > > > > Then you've probably never pushed them very hard. I'm personally curious > > to see whether their newer drives (e.g. Atlas III, Atlas IV, Atlas 10K) > > have the same sorts of problems that their older drives did. I'm > > certainly not willing, however, to spend any money to find out. :) > > And the answer is...Yes:( > > My Atlas II failed and got replaced with a Atlas III: > da1: Fixed Direct Access SCSI-2 > device > > It starts to reduce tags at 36 (da1:ahc0:0:8:0): tagged openings now 36) > ,the same as the Atlas II and mine is now at 2 tags. > > The following patch fixes this: > { > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "QM39100*", "*" }, > /*quirks*/0, /*mintags*/24, /*maxtags*/32 > }, Does anyone have the inquiry information for the 18G version of that drive? I suppose we might as well quirk both of them. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 15:19:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08217 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 15:19:36 -0800 (PST) (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 PAA08035 for ; Tue, 22 Dec 1998 15:19:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA18904; Tue, 22 Dec 1998 15:11:51 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdV18902; Tue Dec 22 23:11:49 1998 Date: Tue, 22 Dec 1998 15:11:43 -0800 (PST) From: Julian Elischer To: "Justin T. Gibbs" cc: Joerg Wunsch , scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go In-Reply-To: <199812222241.PAA01754@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 On Tue, 22 Dec 1998, Justin T. Gibbs wrote: > >From memory, the old driver tried to handle this case > >so you might look there for clues... > > The old driver never used the residual reporting opcodes and > the SCSI framework in general ignored residual information. The reseidual infrmation was not used because some adapters didn't supply it. However those same adaptrers can be assumed to either totally fail or succeed in disk operations (so you KNOW the residual), or on tape devices, the residual arrives later in a sense block. (for short reads) Since the 1540 returns the sense info with the response, it is possible to synthesise this information in all cases that a user of a 1540 probably needs. Joerg, you'll probably have to add the code yourself but you should be able to find the info you need in: 1/the old 1542 driver 2/the old st.c (fore getting residuals on tapes) 3/the old scsi_error.c (I think) more generic sense block handling stuff. I don't have any scsi stuff now so I'l going by memeory... > > -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 15:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10003 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 15:21:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09976 for ; Tue, 22 Dec 1998 15:21:36 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id AAA06936 for scsi@FreeBSD.ORG; Wed, 23 Dec 1998 00:21:26 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id AAA27461; Wed, 23 Dec 1998 00:00:52 +0100 (MET) (envelope-from j) Message-ID: <19981223000050.28179@uriah.heep.sax.de> Date: Wed, 23 Dec 1998 00:00:50 +0100 From: J Wunsch To: scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go Reply-To: Joerg Wunsch References: <19981222173104.28962@uriah.heep.sax.de> <199812222134.OAA14499@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199812222134.OAA14499@narnia.plutotech.com>; from Justin T. Gibbs on Tue, Dec 22, 1998 at 02:34:44PM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote: > I believe that the 1540A does not support residual calculating > CCB opcodes. I'm almost sure it doesn't. > So, you'd have to modify the driver to use these > opcodes on pre-historic devices. `these'? (Sorry, which ones?) > Unfortunately it is impossible > to get correct underrun information without these opcodes, so you'll > have to get creative in this case and you may expose portions of > the CAM code that become confused if the residual reported is incorrect. Hmm, what does that mean ``for the average user''? IOW: under normal circumstances, is it likely that residuals are reported at all? Or in case an adapter doesn't support them, can we just assume there's no residual (without big harm)? I have no good clues about what a residual actual means other than `something was left over from an old request' or something like that... It would be too bad if i had to throw away an otherwise working controller that does its job well (well enough for the environment it's running in, remember it's a scratch machine). I probably would stick with 2.2.x then, but that's a less optimal solution. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 22 15:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11005 for freebsd-scsi-outgoing; Tue, 22 Dec 1998 15:24:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10967 for ; Tue, 22 Dec 1998 15:24:32 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id QAA02978; Tue, 22 Dec 1998 16:24:22 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199812222324.QAA02978@pluto.plutotech.com> To: Julian Elischer cc: "Justin T. Gibbs" , Joerg Wunsch , scsi@FreeBSD.ORG Subject: Re: 3.0R && AHA1540A == no go In-reply-to: Your message of "Tue, 22 Dec 1998 15:11:43 PST." Date: Tue, 22 Dec 1998 16:16:33 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Tue, 22 Dec 1998, Justin T. Gibbs wrote: > >> >From memory, the old driver tried to handle this case >> >so you might look there for clues... >> >> The old driver never used the residual reporting opcodes and >> the SCSI framework in general ignored residual information. > >The reseidual infrmation was not used because some adapters didn't supply >it. >However those same adaptrers can be assumed to either totally fail or >succeed in disk operations (so you KNOW the residual), or on tape devices, >the residual arrives later in a sense block. (for short reads) In most cases, the complications occur for things like mode pages, inquiry data, and sense data. You need to proactively bzero these structures before performing the operation just in case the device does not fill the allocated space and the controller does not provide residual information. I don't know if all scenarios where these requests are performed follow this protocol. >2/the old st.c (fore getting residuals on tapes) Already done in the sa driver. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 23 02:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24026 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 02:12:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24019 for ; Wed, 23 Dec 1998 02:12:21 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id CAA17288; Wed, 23 Dec 1998 02:12:13 -0800 (PST) Date: Wed, 23 Dec 1998 02:12:13 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199812231012.CAA17288@math.berkeley.edu> To: freebsd-scsi@FreeBSD.ORG Subject: /dev/nrsa0 file mark handling Cc: dan@math.berkeley.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I came across the following text near the end of the "sa" man page on one of my release 3.0+ systems: The handling of file marks on write is automatic. If the user has written to the tape, and has not done a read since the last write, then a file mark will be written to the tape when the device is closed. If a rewind is requested after a write, then the driver assumes that the last file on the tape has been written, and ensures that there are two file marks written to the tape. The exception to this is that there seems to be a standard (which we follow, but don't understand why) that certain types of tape do not actually write two file marks to tape, but when read, re- port a `phantom' file mark when the last file is read. These devices in- clude the QIC family of devices. (It might be that this set of devices is the same set as that of fixed block devices. This has not been deter- mined yet, and they are treated as separate behaviors by the driver at this time.) I could have sworn that the automatic EOF mark issue was discussed within the last year on one or more of the freebsd mailing lists. Traditional behavior of traditional tape systems (i.e. 7 or 9 track open reel drives dating back at least 25 years) was to write one tape mark after each file (hence the name "EOF mark") and to write an extra tape mark after the last file to indicate the end of the recorded portion of the tape. This was an absolutely wonderful convention. It made all sorts of useful tape management procedures (e.g. recording checking and tape copying) independent of the data on a tape or the way in which it was formatted. The way to ensure the existence of the "extra" tape mark was to write two EOF marks after each file and backspace over the second mark. This convention was widely followed until the introduction of those junky QIC drives that used serpentine recording with a full tape width erase head separate from the recording head. The erase head is turned on while writing the first track. If you think about it, it should be pretty obvious that such a tape drive cannot safely write except at BOT (beginning of tape) or at EOM (end of recorded medium). QIC tape driver writers coped as best they could. They stopped writing double EOF marks and fudged the "phantom" EOF mark for the benefit of programs that expected the old EOM convention. (Note: traditional 9 track open reel tape drives cannot detect EOM. Modern SCSI drives generally can detect EOM and most will refuse to advance the tape past EOM. I believe this is sometimes foolish "user friendly" behavior designed to prevent fools from shooting holes in their feet.) I basically like the automatic file mark behavior claimed for the "sa" device except that the driver should contain a short list of popular tape drives that are known to be capable of writing over file marks (there ought to be a mode page field that indicates this) and do the double-EOF + BSF procedure at the end of every new file on those drives. While I am at it, I have another "request". The "sa" tape driver still needs a "control" device or some other way of accessing the driver without conflicting with current I/O activity in order to discover device status via the MTIOCGET ioctl(). (An alternative to a control device would be special interpretation of the O_NONBLOCK open flag.) It would be nice if the "struct mtget" fields mt_fileno and mt_blkno were implemented. It would be nice if there was another field that indicated the nature of any tape operation in progress (e.g. REW, FSF, WEOF, simple I/O). So much for dreaming. I have to get "back to work". I would be curious as to which of these suggested features people would actually like. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 23 08:26:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05852 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 08:26:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05807 for ; Wed, 23 Dec 1998 08:26:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id IAA10789; Wed, 23 Dec 1998 08:25:05 -0800 Date: Wed, 23 Dec 1998 08:25:05 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dan Strick cc: freebsd-scsi@FreeBSD.ORG Subject: Re: /dev/nrsa0 file mark handling In-Reply-To: <199812231012.CAA17288@math.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just got through actually re-implementing the 2FM@EOD as quirks. In my opinion it is only required, and only should be used, for tape drives that cannot detect physical end of media (this is different from early warning detection). Quirks are sufficient for this case. > > While I am at it, I have another "request". The "sa" tape driver > still needs a "control" device or some other way of accessing the > driver without conflicting with current I/O activity in order to > discover device status via the MTIOCGET ioctl(). (An alternative to > a control device would be special interpretation of the O_NONBLOCK > open flag.) It would be nice if the "struct mtget" fields mt_fileno > and mt_blkno were implemented. It would be nice if there was another > field that indicated the nature of any tape operation in progress > (e.g. REW, FSF, WEOF, simple I/O). "control open" - Already on my list. "mt_fileno/mt_blkno" - I'm mulling that one. Yes, I think I will, but it'll take a lot of work because there are (now) a large number of conditions that invalidate and make completely unknown those relative positions (EOD, hard block locating). "current state" - Interesting notion. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 23 10:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22142 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 10:43:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22137 for ; Wed, 23 Dec 1998 10:43:37 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.82]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5F for ; Wed, 23 Dec 1998 19:43:31 +0100 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 Date: Wed, 23 Dec 1998 19:50:00 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD SCSI Subject: Fireball ST Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, as of today my da1 is now: da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) Just another question, is this much? (da1:ahc0:0:1:0): tagged openings now 8 And does it match the drive you had, Kenneth? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 23 15:10:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20409 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 15:10:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20401 for ; Wed, 23 Dec 1998 15:10:19 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA07057; Wed, 23 Dec 1998 16:10:08 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812232310.QAA07057@panzer.plutotech.com> Subject: Re: Fireball ST In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 23, 98 07:50:00 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Wed, 23 Dec 1998 16:10:08 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai wrote... > OK, > > as of today my da1 is now: > > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled > da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) Good. That's one firmware rev that seems to work okay, I think. We've got two different revs: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2079MB (4259112 512 byte sectors: 64H 32S/T 2079C) da2 at ahc2 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI2 device da2: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da2: 2068MB (4235629 512 byte sectors: 255H 63S/T 263C) > Just another question, is this much? > > (da1:ahc0:0:1:0): tagged openings now 8 Nope, it's not much, but it's all you're going to get: (da0:ahc0:0:0:0): tagged openings now 8 At least the Fireball ST firmware doesn't seem to have the infinite queue full problem that the Atlas {I, II, III} has. > And does it match the drive you had, Kenneth? Yes, it does. (except for the capacity, of course.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 23 20:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06363 for freebsd-scsi-outgoing; Wed, 23 Dec 1998 20:43:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06357 for ; Wed, 23 Dec 1998 20:43:07 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: from rain.berkeley.edu (rain.Berkeley.EDU [128.32.183.196]) by math.berkeley.edu (8.8.7/8.8.7) with ESMTP id UAA10439 for ; Wed, 23 Dec 1998 20:42:47 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Received: (dan@localhost) by rain.berkeley.edu (8.8.5/8.6.4) id UAA03018 for freebsd-scsi@FreeBSD.ORG; Wed, 23 Dec 1998 20:42:45 -0800 (PST) Date: Wed, 23 Dec 1998 20:42:45 -0800 (PST) Message-Id: <199812240442.UAA03018@rain.berkeley.edu> To: freebsd-scsi@FreeBSD.ORG Subject: Re: /dev/nrsa0 file mark handling Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > "control open" - Already on my list. > > "mt_fileno/mt_blkno" - I'm mulling that one. Yes, I think I will, but > it'll take a lot of work because there are (now) a large number of > conditions that invalidate and make completely unknown those > relative positions (EOD, hard block locating). > > "current state" - Interesting notion. My motivation for wanting these things is that I have a program (designed for use with a different device driver that provided these facilities) that could repeatedly query the driver for device state and type the result using something like a curses overlay style. The result was something like a continuous drive status control panel that lent confidence to the progress of long tape jobs. It was also cute when used with disks (my disk driver returned the number of the most recently accessed block in the status struct). I liked to watch the heads march down the drive when doing disk-to-disk copies and such. I once considered doing a graphical interface that would draw a rotating disk with a sliding disk head arm over a numerical scale. (Note: pseudo cylinder numbers are useful even when not precisely accurate.) There are all sorts of other interesting possibilities. Bad sectors could be colored red. When disk errors occur, we could show bits falling off the disk and piling up on the floor. Imagine a snow storm of metallic film flakes. Color them dark red in honor of the traditional medium. but I digress ... back to work now Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 24 02:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16130 for freebsd-scsi-outgoing; Thu, 24 Dec 1998 02:54:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from firewall1.lehman.com (firewall.Lehman.COM [192.147.65.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16081; Thu, 24 Dec 1998 02:53:40 -0800 (PST) (envelope-from nclayton@lehman.com) From: nclayton@lehman.com Received: from relay.lehman.com by firewall1.lehman.com (8.8.6/8.8.6) id FAA28186; Thu, 24 Dec 1998 05:53:23 -0500 (EST) Received: from cmgrelay1.messaging-svcs.lehman.com by relay.lehman.com (4.1/LB-0.6) id AA19211; Thu, 24 Dec 98 05:52:52 EST Received: from lonmailhost.lehman.com by cmgrelay1.messaging-svcs.lehman.com (8.8.5/8.8.5) id FAA24058; Thu, 24 Dec 1998 05:52:49 -0500 (EST) Received: from lonadminvnm.lehman.com by lonmailhost.lehman.com (SMI-8.6/Lehman Bros. V1.5) id KAA11181; Thu, 24 Dec 1998 10:52:47 GMT Received: from lonadmin80.lehman.com by lonadminvnm.lehman.com (4.1/Lehman Bros. V1.6) id AA02030; Thu, 24 Dec 98 10:52:47 GMT Received: by lonadmin80.lehman.com (SMI-8.6/Lehman Bros. V1.5) id KAA14858; Thu, 24 Dec 1998 10:52:46 GMT Message-Id: <19981224105246.I10040@lehman.com> Date: Thu, 24 Dec 1998 10:52:46 +0000 To: questions@FreeBSD.ORG, scsi@FreeBSD.ORG Cc: nik@FreeBSD.ORG Subject: Python 02635-XXX 567D tape drive hangs 2.2.7-stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Lehman Brothers Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ sent to -questions and -scsi, since either could be appropriate ] I'm trying to back up my home system using a SCSI tape drive I've had handy. It's from a Sun system. However, ~30 minutes after starting 'dump', the system hangs, printing /kernel: sd1(ncr0:1:0): error code 1 /kernel: , retries:4 /kernel: sd1(ncr0:1:0): error code 1 /kernel: , retries:2 /kernel: sd1(ncr0:1:0): error code 1 /kernel: , FAILURE /kernel: sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted /kernel: , retries:3 on the console. I can ^C the dump command to get the prompt back, but any further disk access (ls, sync, and so on) locks the machine. This also happens when I use tar. This happens *before* dump has printed any of its messages. The boot messages for the SCSI devices on the system are: */kernel: ncr0 rev 3 int a irq 10 on pci0:12:0 /kernel: (ncr0:0:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2 /kernel: sd0(ncr0:0:0): Direct-Access /kernel: sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled /kernel: sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 16) /kernel: 2170MB (4445380 512 byte sectors) /kernel: (ncr0:1:0): "SEAGATE ST34520W 1444" type 0 fixed SCSI 2 /kernel: sd1(ncr0:1:0): Direct-Access /kernel: sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled /kernel: sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) /kernel: 4340MB (8888924 512 byte sectors) */kernel: (ncr0:4:0): "ARCHIVE Python 02635-XXX 567D" type 1 removable SCSI 2 */kernel: st0(ncr0:4:0): Sequential-Access */kernel: st0(ncr0:4:0): 6.7 MB/s (150 ns, offset 15) */kernel: density code 0x8c, 512-byte blocks, write-enabled /kernel: (ncr0:6:0): "TOSHIBA CD-ROM XM-3801TA 0207" type 5 removable SCSI 2 /kernel: cd0(ncr0:6:0): CD-ROM /kernel: cd0(ncr0:6:0): 10.0 MB/s (100 ns, offset 8) * = controller and tape drive. The mailing list archives have messages from people using ARCHIVE Python drives successfully, but none of them seem to have the same revision number as this one. AltaVista and DejaNews searches for those error messages (and revision numbers) haven't turned up anything useful either. I've checked for SCSI problems. The internal SCSI cable (two disks on it) is short enough, and properly terminated. The external SCSI cable only has this tape drive on it, and is ~ 1.5 feet long. The tape drive is self terminating, but the problem happens if add a terminator to the drive as well. I'm running 2.2.7-stable, built around the middle of last November. Upgrading to 2.2.8 is feasible to fix this, but if possible I don't want to have to go to -current to fix it (the reason I want it working is so that I can take a backup, wipe the system, and start running -current on it). Any suggestions gratefully received. N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 24 21:26:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04874 for freebsd-scsi-outgoing; Thu, 24 Dec 1998 21:26:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04824; Thu, 24 Dec 1998 21:25:48 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA12063; Thu, 24 Dec 1998 22:15:41 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812250515.WAA12063@panzer.plutotech.com> Subject: Re: cvs commit: ports/misc/amanda24 Makefile ports/misc/amanda24/files md5 ports/misc/amanda24/patches patch-ad patch-ah In-Reply-To: <199812250015.QAA16342@freefall.freebsd.org> from Chris Timmons at "Dec 24, 98 04:15:24 pm" To: cwt@FreeBSD.ORG (Chris Timmons) Date: Thu, 24 Dec 1998 22:15:41 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM914562941-11970-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM914562941-11970-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Chris Timmons wrote... > cwt 1998/12/24 16:15:24 PST > > Modified files: > misc/amanda24 Makefile > misc/amanda24/files md5 > misc/amanda24/pkg PLIST > Removed files: > misc/amanda24/patches patch-ad patch-ah > Log: > Amanda 2.4.1p1. Also, honor nodump flag - requested-by: wjw@hobby.digiware.nl > > Revision Changes Path > 1.21 +5 -3 ports/misc/amanda24/Makefile > 1.10 +1 -1 ports/misc/amanda24/files/md5 > 1.13 +4 -5 ports/misc/amanda24/pkg/PLIST I've written some preliminary CAM changer support for Amanda 2.4 (not p1). I haven't yet had an opportunity to test it, though. If anyone wants to try it out, just replace patches/patch-af with the attached patch. Ken -- Kenneth Merry ken@plutotech.com --ELM914562941-11970-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=amanda.patch-af Content-Description: amanda.patch-af Content-Transfer-Encoding: 7bit --- changer-src/scsi-chio.c.orig Tue Jul 7 22:04:04 1998 +++ changer-src/scsi-chio.c Thu Dec 17 17:00:04 1998 @@ -114,6 +114,116 @@ } +#if defined(__FreeBSD__) && defined(HAVE_CAMLIB_H) + +/* + * The CHIOGSTATUS ioctl is slightly different in FreeBSD/CAM than it was + * in earlier versions of the FreeBSD SCSI code. + */ +int +isempty(int fd, int slot) +{ + struct changer_element_status_request cesr; + int i, rc; + int empty = 1; + + get_changer_info(fd); + + bzero(&cesr, sizeof(cesr)); + + /* We want to check a slot */ + cesr.cesr_element_type = CHET_ST; + cesr.cesr_element_status = (struct changer_element_status *) + malloc(sizeof(struct changer_element_status)); + + /* Start at the given slot */ + cesr.cesr_element_base = slot; + + /* We only want info on this slot */ + cesr.cesr_element_count = 1; + + if ((rc = ioctl(fd, CHIOGSTATUS, &cesr)) == -1) { + free(cesr.cesr_element_status); + fprintf(stderr, "%s: changer status query failed: %#x %s\n", + get_pname(), rc, strerror(errno)); + return(rc); + } + + if (cesr.cesr_element_status[0].ces_flags & CES_STATUS_FULL) + empty = 0; + + free(cesr.cesr_element_status); + + return(empty); +} + +int +find_empty(int fd) +{ + struct changer_element_status_request cesr; + int i, rc; + + get_changer_info(fd); + + bzero(&cesr, sizeof(cesr)); + + /* We want to check a slot */ + cesr.cesr_element_type = CHET_ST; + cesr.cesr_element_status = (struct changer_element_status *) + malloc(sizeof(struct changer_element_status) * + changer_info.cp_nslots); + + if (cesr.cesr_element_status == NULL) + return(-1); + + /* Start at the first slot */ + cesr.cesr_element_base = 0; + + /* Grab all slots */ + cesr.cesr_element_count = changer_info.cp_nslots; + + if ((rc = ioctl(fd, CHIOGSTATUS, &cesr)) == -1) { + free(cesr.cesr_element_status); + fprintf(stderr, "%s: changer status query failed: %#x %s\n", + get_pname(), rc, strerror(errno)); + return(rc); + } + + for (i = 0; i < changer_info.cp_nslots; i++) { + if ((cesr.cesr_element_status[i].ces_flags & + CES_STATUS_FULL)==0) { + free(cesr.cesr_element_status); + return(i); + } + } + + free(cesr.cesr_element_status); + + return(-1); +} + +int +drive_loaded(int fd, int drivenum) +{ + struct changer_element_status_request cesr; + int i, rc; + + cesr.cesr_element_type = CHET_DT; + cesr.cesr_element_status = (struct changer_element_status *) + malloc(sizeof(struct changer_element_status)); + cesr.cesr_element_base = drivenum; + cesr.cesr_element_count = 1; + + if ((rc = ioctl(fd, CHIOGSTATUS, &cesr)) == -1) { + free(cesr.cesr_element_status); + fprintf(stderr, "%s: drive status query failed: %#x %s\n", + get_pname(), rc, strerror(errno)); + return(rc); + } +} + +#else + /* * this routine checks a specified slot to see if it is empty */ @@ -141,6 +251,8 @@ return !i; } + + /* * find the first empty slot */ @@ -169,6 +281,8 @@ return i; } + + /* * returns one if there is a tape loaded in the drive */ @@ -195,7 +309,7 @@ free(ces.ces_data); return i; } - +#endif /* * unloads the drive, putting the tape in the specified slot --ELM914562941-11970-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 24 22:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10781 for freebsd-scsi-outgoing; Thu, 24 Dec 1998 22:29:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10776 for ; Thu, 24 Dec 1998 22:29:10 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id WAA26321; Thu, 24 Dec 1998 22:28:56 -0800 (PST) Date: Thu, 24 Dec 1998 22:28:56 -0800 (PST) From: Chris Timmons To: "Kenneth D. Merry" cc: scsi@FreeBSD.ORG Subject: Re: cvs commit: ports/misc/amanda24 Makefile ports/misc/amanda24/files md5 ports/misc/amanda24/patches patch-ad patch-ah In-Reply-To: <199812250515.WAA12063@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Great! Since what I have in the port is a no-op anyways, feel free to add your patch when ready. I sent a note off to the amanda maintainer asking for HAVE_CAMLIB_H in config.h (the port modifies config.h.in to get it set by autoconf.) They are looking for camlib.h with autoconf, but then disabling chg-scsi support if they find it. It shouldn't take too long to get this squared away. -Chris On Thu, 24 Dec 1998, Kenneth D. Merry wrote: > I've written some preliminary CAM changer support for Amanda 2.4 (not p1). > > I haven't yet had an opportunity to test it, though. If anyone wants to > try it out, just replace patches/patch-af with the attached patch. > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 25 04:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04683 for freebsd-scsi-outgoing; Fri, 25 Dec 1998 04:23:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles337.castles.com [208.214.167.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04670 for ; Fri, 25 Dec 1998 04:23:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA05215; Fri, 25 Dec 1998 04:20:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812251220.EAA05215@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mason Loring Bliss cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI question... In-reply-to: Your message of "Thu, 24 Dec 1998 10:22:30 EST." <19981224102230.T365@acheron.middleboro.ma.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Dec 1998 04:20:55 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For some fairly obvious reasons, this should have gone to scsi@freebsd.org. > My company is trying to support FreeBSD, and it's been left to me to figure > out a couple things without having a FreeBSD box handy. Eek. That can be rough. > 1) Our box is a multi-LUN SCSI device. Are multiple LUNs supported in FreeBSD > by default? (A complication is that I don't know what version of FreeBSD our > client runs. I've been told -current, but I doubt that. I'm guessing 2.0.x. > I will find out for sure on Monday, but getting a jump over the weekend would > be cool.) Yes. > 2) Can I access multiple LUNs through individual device files? If so, can I > assume that the kernel will pop up messages saying what files have devices > attached? Presuming the "box" is something that is supported by the FreeBSD drivers, sure. You may have to add a quirk entry (and rebuild the kernel) to get it to probe all the LUs. > 3) Should I have the client do "/dev/MAKEDEV all" before rebooting with the > device attached? That would do what I want under NetBSD, but I'm not quite > sure about FreeBSD. You don't need to do it *before* booting, and again it depends on the release of FreeBSD and the nature of your device. Generally it's best to explicitly make the devices in question. > I'll probably have a FreeBSD box at both work and home before too long, but > at the moment I'm sort of groping in the dark to figure some of this out. > I want to know as much as possible before leading my client through an install > on Monday. Yikes, talk about being dropped in the deep end. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message