From owner-freebsd-scsi Sun Dec 22 14:26:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA22662 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 14:26:49 -0800 (PST) Received: from fcom.com (subsolar@flamingo1.fcom.com [204.252.66.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA22657 for ; Sun, 22 Dec 1996 14:26:47 -0800 (PST) Received: by fcom.com (8.6.13/FCOM-1.22) id OAA06031; Sun, 22 Dec 1996 14:26:38 -0800 Date: Sun, 22 Dec 1996 14:26:38 -0800 From: subsolar@fcom.com (???) Message-Id: <199612222226.OAA06031@fcom.com> To: scsi@freebsd.org Subject: test Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk test From owner-freebsd-scsi Sun Dec 22 14:54:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA23926 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 14:54:42 -0800 (PST) Received: from fcom.com (root@flamingo1.fcom.com [204.252.66.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA23919 for ; Sun, 22 Dec 1996 14:54:39 -0800 (PST) Received: from flamingo1.fcom.com by fcom.com (8.6.13/FCOM-1.22) id OAA06097; Sun, 22 Dec 1996 14:54:38 -0800 Date: Sun, 22 Dec 1996 14:54:38 -0800 (PST) From: SubSolar To: scsi@freebsd.org Subject: Adaptec 2920 PCI SCSI support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I was wondering if there was a FreeBSD driver for the Adaptec AHA-2920 PCI SCSI controller. Thanx. From owner-freebsd-scsi Sun Dec 22 15:32:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA26091 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 15:32:54 -0800 (PST) Received: from deacon.cogsci.ed.ac.uk (deacon.cogsci.ed.ac.uk [129.215.144.7]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA26086 for ; Sun, 22 Dec 1996 15:32:52 -0800 (PST) Received: from pitcairn.cogsci.ed.ac.uk (pitcairn.cogsci.ed.ac.uk [129.215.197.19]) by deacon.cogsci.ed.ac.uk (8.6.10/8.6.12) with ESMTP id XAA16749; Sun, 22 Dec 1996 23:32:47 GMT Date: Sun, 22 Dec 1996 23:32:46 GMT Message-Id: <1309.199612222332@pitcairn.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: good way to add disks? To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) In-Reply-To: J Wunsch's message of Wed, 18 Dec 1996 23:31:05 +0100 (MET) Organization: just say no Cc: sadmin@roundtable.cif.rochester.edu Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > You should be able to do a dump onto the raw disk device, without even > > making a file system on it. > Not if you think of `dump' in terms of dump(8)/restore(8). Only if > you think of `dump' in terms of dd(1) -- but who would be willing to > do this these days? Er, no, actually I was thinking of: spottisvax# dump -fBb /dev/rsd1 xxx yyy / Is there some reason not to do this? -- Richard From owner-freebsd-scsi Sun Dec 22 15:51:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA26971 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 15:51:36 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA26965 for ; Sun, 22 Dec 1996 15:51:31 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA12484; Mon, 23 Dec 1996 00:51:08 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA04956; Mon, 23 Dec 1996 00:51:08 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA17324; Mon, 23 Dec 1996 00:27:23 +0100 (MET) From: J Wunsch Message-Id: <199612222327.AAA17324@uriah.heep.sax.de> Subject: Re: Adaptec 2920 PCI SCSI support? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Mon, 23 Dec 1996 00:27:23 +0100 (MET) Cc: subsolar@flamingo1.fcom.com (SubSolar) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from SubSolar at "Dec 22, 96 02:54:38 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As SubSolar wrote: > Hello, I was wondering if there was a FreeBSD driver for the Adaptec > AHA-2920 PCI SCSI controller. No, it's not, and there's most likely nobody working on it right now. Btw., these controllers are actually ``Future Domain'' controllers, and part of the story why there's still nobody writing a driver is that they are, despite of their promising name (in resemblance of the fairly good 2940/3940 series), basically poor hardware. They are PIO only controllers, so you'll suffer from the same problems as with using an IDE disk. If you're looking for a cheap _and_ good SCSI controller, stick with the SymBios ones (formerly NCR). -- 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. ;-) From owner-freebsd-scsi Sun Dec 22 16:21:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA28162 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 16:21:24 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA28156 for ; Sun, 22 Dec 1996 16:21:21 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA17180; Mon, 23 Dec 1996 01:21:12 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA05360; Mon, 23 Dec 1996 01:21:12 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA20751; Mon, 23 Dec 1996 00:54:43 +0100 (MET) From: J Wunsch Message-Id: <199612222354.AAA20751@uriah.heep.sax.de> Subject: Re: good way to add disks? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Mon, 23 Dec 1996 00:54:43 +0100 (MET) Cc: sadmin@roundtable.cif.rochester.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <1309.199612222332@pitcairn.cogsci.ed.ac.uk> from Richard Tobin at "Dec 22, 96 11:32:46 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Richard Tobin wrote: > > > You should be able to do a dump onto the raw disk device, without even > > > making a file system on it. > > > Not if you think of `dump' in terms of dump(8)/restore(8). Only if > > you think of `dump' in terms of dd(1) -- but who would be willing to > > do this these days? > > Er, no, actually I was thinking of: > > spottisvax# dump -fBb /dev/rsd1 xxx yyy / > > Is there some reason not to do this? Is there some reason you want to do this? :-) Basically, it will make /dev/rsd1 a ``dump tape''. However, i don't think this will do you any good, at the very least, it's nothing you would even remotely be able to mount... The only purpose you could use /dev/rsd1 thereafter is feeding it into restore(8). -- 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. ;-) From owner-freebsd-scsi Sun Dec 22 20:36:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA15280 for freebsd-scsi-outgoing; Sun, 22 Dec 1996 20:36:41 -0800 (PST) Received: from fcom.com (root@flamingo1.fcom.com [204.252.66.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id UAA15275 for ; Sun, 22 Dec 1996 20:36:40 -0800 (PST) Received: from flamingo1.fcom.com by fcom.com (8.6.13/FCOM-1.22) id UAA06875; Sun, 22 Dec 1996 20:36:39 -0800 Date: Sun, 22 Dec 1996 20:36:38 -0800 (PST) From: SubSolar To: scsi@freebsd.org Subject: Iomega SCSI Zip Drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry to bother you again, but I was wondering if there was a FreeBSD driver for the SCSI Iomega Zip drive. From owner-freebsd-scsi Mon Dec 23 02:23:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27749 for freebsd-scsi-outgoing; Mon, 23 Dec 1996 02:23:09 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA27740 for ; Mon, 23 Dec 1996 02:22:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA24629; Mon, 23 Dec 1996 11:22:56 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA10732; Mon, 23 Dec 1996 11:22:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA02707; Mon, 23 Dec 1996 11:21:17 +0100 (MET) From: J Wunsch Message-Id: <199612231021.LAA02707@uriah.heep.sax.de> Subject: Re: Iomega SCSI Zip Drive To: subsolar@flamingo1.fcom.com (SubSolar) Date: Mon, 23 Dec 1996 11:21:17 +0100 (MET) Cc: scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from SubSolar at "Dec 22, 96 08:36:38 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As SubSolar wrote: > Sorry to bother you again, but I was wondering if there was a FreeBSD > driver for the SCSI Iomega Zip drive. Doesn't it work for you? -- 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. ;-) From owner-freebsd-scsi Wed Dec 25 02:21:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA04610 for freebsd-scsi-outgoing; Wed, 25 Dec 1996 02:21:32 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA04595 for ; Wed, 25 Dec 1996 02:21:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA28791; Wed, 25 Dec 1996 11:21:18 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA18286; Wed, 25 Dec 1996 11:21:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA16758; Wed, 25 Dec 1996 11:05:03 +0100 (MET) From: J Wunsch Message-Id: <199612251005.LAA16758@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/scsi cd.c To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Wed, 25 Dec 1996 11:05:03 +0100 (MET) Cc: msmith@atrad.adelaide.edu.au (Michael Smith) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612250117.LAA21192@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 25, 96 11:47:48 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Moved to -scsi) As Michael Smith wrote: > > Modified: sys/scsi cd.c > > Slightly re-order the sequence of commands issued, so try to send > > the START UNIT command before testing whether the device is ready. > > Maybe it should be done even earlier, i'm not 100 % sure. > > >From recent experience with a box full of disks jumpered to spin up on > command (inadequate power supply), I'd really appreciate it if the > START UNIT command could be sent during the probe, followed by a > _long_ wait for the drive to become ready. But that's a little unrelated to this commit, right? This one was for CDs. However, it looks as if the original drivers for sd/cd/od were all cloned from the same, and thus inherited all the bugs... so i think the same problem still exists in the sd driver. Why do you want to have the disks spun up at probe time? IMHO, issuing the START UNIT at open time would be sufficient. There's no need to start the spindles before you're going to access them. The INQUIRY command is usually answered fine without spinning. Of course, the long wait is still required. The current timeout is 10 seconds, it's in the function scsi_start_unit() in sys/scsi/scsi_base.c. Feel free to bump this to 60 seconds once you know what you need. (I think you could experiment with a change to the sd driver that is similar to the cd driver change we're discussing about here.) -- 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. ;-) From owner-freebsd-scsi Thu Dec 26 03:25:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA17608 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 03:25:31 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA17601 for ; Thu, 26 Dec 1996 03:25:27 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA14666 (5.67b/IDA-1.5 for ); Thu, 26 Dec 1996 12:25:24 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id MAA01001; Thu, 26 Dec 1996 12:20:37 +0100 (CET) Message-Id: Date: Thu, 26 Dec 1996 12:19:17 +0100 From: se@freebsd.org (Stefan Esser) To: joerg_wunsch@sax.sax.de (Joerg Wunsch) Cc: freebsd-scsi@freebsd.org (FreeBSD SCSI list), msmith@atrad.adelaide.edu.au (Michael Smith) Subject: Re: cvs commit: src/sys/scsi cd.c References: <199612250117.LAA21192@genesis.atrad.adelaide.edu.au> <199612251005.LAA16758@uriah.heep.sax.de> X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: <199612251005.LAA16758@uriah.heep.sax.de>; from J Wunsch on Dec 25, 1996 11:05:03 +0100 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 25, j@uriah.heep.sax.de (J Wunsch) wrote: > Why do you want to have the disks spun up at probe time? IMHO, > issuing the START UNIT at open time would be sufficient. There's no Please make this: ONE (instead of A) START UNIT command ... There are drives that don't like to receive an START UNIT command while executing being in the process of executing some command. (This may happen, if you have tagged commands enabled and open the disk character devices, like eg. dump does ...) Regards, STefan From owner-freebsd-scsi Thu Dec 26 04:03:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA18341 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 04:03:57 -0800 (PST) Received: from gaia.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.2.31]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA18336 for ; Thu, 26 Dec 1996 04:03:53 -0800 (PST) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.3/8.7.3) id RAA29325; Wed, 25 Dec 1996 17:34:46 -0200 (EDT) From: Joao Carlos Mendes Luis Message-Id: <199612251934.RAA29325@gaia.coppe.ufrj.br> Subject: Re: Iomega SCSI Zip Drive To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 25 Dec 1996 17:34:46 -0200 (EDT) Cc: subsolar@flamingo1.fcom.com, scsi@freebsd.org In-Reply-To: <199612231021.LAA02707@uriah.heep.sax.de> from J Wunsch at "Dec 23, 96 11:21:17 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(J Wunsch) // As SubSolar wrote: // // > Sorry to bother you again, but I was wondering if there was a FreeBSD // > driver for the SCSI Iomega Zip drive. // // Doesn't it work for you? Aside from the drop to debugger when I change disks, its perfect. // // -- // 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. ;-) // Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-scsi Thu Dec 26 06:22:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA21499 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 06:22:10 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA21494 for ; Thu, 26 Dec 1996 06:22:04 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA00688; Thu, 26 Dec 1996 15:21:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA10928; Thu, 26 Dec 1996 15:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id PAA05373; Thu, 26 Dec 1996 15:15:55 +0100 (MET) From: J Wunsch Message-Id: <199612261415.PAA05373@uriah.heep.sax.de> Subject: Re: Iomega SCSI Zip Drive To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Thu, 26 Dec 1996 15:15:54 +0100 (MET) Cc: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis), subsolar@flamingo1.fcom.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612251934.RAA29325@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Dec 25, 96 05:34:46 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Joao Carlos Mendes Luis wrote: (driver for the SCSI Iomega Zip drive) > // Doesn't it work for you? > > Aside from the drop to debugger when I change disks, its perfect. Huh, that's not supposed to happen. Can you quote a little more from your error messages? You might also try experimenting with the `od' driver. It is better targeted for the requirements of a changeable media device. In order to register your Zip drive with the `od' driver, you gotta add a quirk record to sys/scsi/scsconf.c. Something like: Index: scsiconf.c =================================================================== RCS file: /home/ncvs/src/sys/scsi/scsiconf.c,v retrieving revision 1.73 diff -u -u -r1.73 scsiconf.c --- scsiconf.c 1996/12/20 20:43:45 1.73 +++ scsiconf.c 1996/12/26 14:12:52 @@ -265,6 +265,10 @@ T_DIRECT, T_OPTICAL, T_REMOV, "RICOH", "RO-*", "*", "od", SC_ONE_LU }, + { + T_DIRECT, T_OPTICAL, T_REMOV, "IOMEGA", "ZIP*", "*", + "od", SC_ONE_LU + }, #endif /* NOD */ #if NSD > 0 { Of course, you need to replace the "ZIP*" by whatever you drive sends as inquiry data (see the boot message logs). It's possible that the above patch doesn't apply to non-current systems, i had to reorder some of the entries in that table recently. But you should get the picture. -- 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. ;-) From owner-freebsd-scsi Thu Dec 26 07:43:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24655 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 07:43:32 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24650 for ; Thu, 26 Dec 1996 07:43:30 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id IAA09009 for ; Thu, 26 Dec 1996 08:43:25 -0700 (MST) Message-ID: <32C29D1D.41C67EA6@fsl.noaa.gov> Date: Thu, 26 Dec 1996 08:43:25 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: scsi@freebsd.org Subject: Explain this you SCSI tape experts! :-) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This isn't FreeBSD-specific, but you guys are unusually enlightened, so I'm sure you can provide an answer. A new DAT backup tape used in a WangDAT 6130HS drive reads and writes just fine. Several nights ago, Amanda read its label, and wrote a backup set to it. I stuck it on the shelf, away from magnetic sources and what-not, nestled in with the other tapes in the current rotation. As fate would have it, that's the very tape I need. But when I stick it in the drive, FreeBSD reports BLANK CHECK. Doh! What could cause that? -- Sean Kelly NOAA Forecast Systems Laboratory Boulder Colorado USA From owner-freebsd-scsi Thu Dec 26 08:52:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA27159 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 08:52:04 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA27147 for ; Thu, 26 Dec 1996 08:52:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA14078; Thu, 26 Dec 1996 17:51:00 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA13336; Thu, 26 Dec 1996 17:51:00 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA10779; Thu, 26 Dec 1996 17:33:33 +0100 (MET) From: J Wunsch Message-Id: <199612261633.RAA10779@uriah.heep.sax.de> Subject: Re: Explain this you SCSI tape experts! :-) To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Thu, 26 Dec 1996 17:33:32 +0100 (MET) Cc: kelly@fsl.noaa.gov (Sean Kelly) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32C29D1D.41C67EA6@fsl.noaa.gov> from Sean Kelly at "Dec 26, 96 08:43:25 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Sean Kelly wrote: > As fate would have it, that's the very tape I need. But when I stick it > in the drive, FreeBSD reports BLANK CHECK. Doh! > > What could cause that? No idea why there's nothing on the tape, but BLANK CHECK does of course mean you're trying to read beyond the recorded medium area. -- 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. ;-) From owner-freebsd-scsi Thu Dec 26 09:28:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA28005 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 09:28:24 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA28000 for ; Thu, 26 Dec 1996 09:28:21 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBF31F.930D51C0@kaori.communique.net>; Thu, 26 Dec 1996 11:26:01 -0600 Message-ID: From: Raul Zighelboim To: "'scsi@freebsd.org'" , "'Sean Kelly'" Subject: RE: Explain this you SCSI tape experts! :-) Date: Thu, 26 Dec 1996 11:26:00 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Murphy law: backups only fail if you need them! ---------------------------------------------- Raul Zighelboim mailto:mango@communique.net Communique Inc. http://communique.net >---------- >From: Sean Kelly[SMTP:kelly@fsl.noaa.gov] >Sent: Thursday, December 26, 1996 9:43 AM >To: scsi@freebsd.org >Subject: Explain this you SCSI tape experts! :-) > >This isn't FreeBSD-specific, but you guys are unusually enlightened, so >I'm sure you can provide an answer. > >A new DAT backup tape used in a WangDAT 6130HS drive reads and writes >just fine. Several nights ago, Amanda read its label, and wrote a >backup set to it. I stuck it on the shelf, away from magnetic sources >and what-not, nestled in with the other tapes in the current rotation. > >As fate would have it, that's the very tape I need. But when I stick >it >in the drive, FreeBSD reports BLANK CHECK. Doh! > >What could cause that? > >-- >Sean Kelly >NOAA Forecast Systems Laboratory >Boulder Colorado USA > From owner-freebsd-scsi Thu Dec 26 09:57:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00499 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 09:57:13 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA00494 for ; Thu, 26 Dec 1996 09:57:10 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id KAA09204; Thu, 26 Dec 1996 10:56:59 -0700 (MST) Message-ID: <32C2BC69.41C67EA6@fsl.noaa.gov> Date: Thu, 26 Dec 1996 10:56:57 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Raul Zighelboim CC: "'scsi@freebsd.org'" Subject: Re: Explain this you SCSI tape experts! :-) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Raul Zighelboim wrote: > Murphy law: backups only fail if you need them! And, being Irish, I seem to know Murphy really well. ;-) --k From owner-freebsd-scsi Thu Dec 26 10:20:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01344 for freebsd-scsi-outgoing; Thu, 26 Dec 1996 10:20:25 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01336 for ; Thu, 26 Dec 1996 10:20:15 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id KAA27492; Thu, 26 Dec 1996 10:18:37 -0800 (PST) Message-ID: <32C2C13E.41C67EA6@whistle.com> Date: Thu, 26 Dec 1996 10:17:34 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD SCSI list , Sean Kelly Subject: Re: Explain this you SCSI tape experts! :-) References: <199612261633.RAA10779@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Sean Kelly wrote: > > > As fate would have it, that's the very tape I need. But when I stick it > > in the drive, FreeBSD reports BLANK CHECK. Doh! > > > > What could cause that? > > No idea why there's nothing on the tape, but BLANK CHECK does of > course mean you're trying to read beyond the recorded medium area. didi you rewind it accidentally between sets? did you rewind if after the last one? etc. etc. From owner-freebsd-scsi Fri Dec 27 00:47:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA10576 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 00:47:19 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA10569 for ; Fri, 27 Dec 1996 00:47:15 -0800 (PST) Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vdXwe-000QYtC; Fri, 27 Dec 96 09:47 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id JAA03088; Fri, 27 Dec 1996 09:35:02 +0100 (MET) From: grog@lemis.de Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612270835.JAA03088@freebie.lemis.de> Subject: Re: good way to add disks? In-Reply-To: <199612182231.XAA24183@uriah.heep.sax.de> from J Wunsch at "Dec 18, 96 11:31:05 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 09:35:01 +0100 (MET) Cc: freebsd-scsi@freebsd.org (FreeBSD SCSI Mailing List) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: > As Richard Tobin wrote: > >> You should be able to do a dump onto the raw disk device, without even >> making a file system on it. > > Not if you think of `dump' in terms of dump(8)/restore(8). Only if > you think of `dump' in terms of dd(1) -- but who would be willing to > do this these days? I, for one. As long as you don't change your disk geometry, it works fine, and it's faster than any file-system related method. There's only one problem: it doesn't work. To be more specific, it didn't work for me last year when using pre-release 2.1. There was some problem about the device protecting itself, and I never resolved it. Possibly I just used the wrong device. It worked fine on BSD/OS once you disabled the label overwrite protection code. Greg From owner-freebsd-scsi Fri Dec 27 00:47:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA10589 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 00:47:23 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA10575 for ; Fri, 27 Dec 1996 00:47:18 -0800 (PST) Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vdXwf-000QaEC; Fri, 27 Dec 96 09:47 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id JAA02999; Fri, 27 Dec 1996 09:25:57 +0100 (MET) From: grog@lemis.de Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612270825.JAA02999@freebie.lemis.de> Subject: Re: Explain this you SCSI tape experts! :-) In-Reply-To: <32C2C13E.41C67EA6@whistle.com> from Julian Elischer at "Dec 26, 96 10:17:34 am" To: julian@whistle.com (Julian Elischer) Date: Fri, 27 Dec 1996 09:25:55 +0100 (MET) Cc: freebsd-scsi@freebsd.org (FreeBSD SCSI Mailing List) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: > J Wunsch wrote: >> >> As Sean Kelly wrote: >> >> As fate would have it, that's the very tape I need. But when I stick it >> in the drive, FreeBSD reports BLANK CHECK. Doh! >> >> What could cause that? >> >> No idea why there's nothing on the tape, but BLANK CHECK does of >> course mean you're trying to read beyond the recorded medium area. > > didi you rewind it accidentally between sets? > did you rewind if after the last one? I wish I understood what happened here. I would almost guess that you (Sean) have mistaken the tape for another one which is really blank. In any case, it's not a question of rewinding: helical scan drives rewind tapes before ejecting them, even if you have specified /dev/nrst*. I can't see how you could write anything on the tape without first writing at the start, and after loading again, it will definitely be positioned at BOT. Greg From owner-freebsd-scsi Fri Dec 27 01:21:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA11649 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 01:21:46 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA11637 for ; Fri, 27 Dec 1996 01:21:43 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA02834 for ; Fri, 27 Dec 1996 10:21:30 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA28735 for freebsd-scsi@FreeBSD.org; Fri, 27 Dec 1996 10:21:30 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA03481 for freebsd-scsi@FreeBSD.org; Fri, 27 Dec 1996 10:06:31 +0100 (MET) From: J Wunsch Message-Id: <199612270906.KAA03481@uriah.heep.sax.de> Subject: Re: good way to add disks? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Fri, 27 Dec 1996 10:06:31 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612270835.JAA03088@freebie.lemis.de> from Greg Lehey at "Dec 27, 96 09:35:01 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > > Only if > > you think of `dump' in terms of dd(1) -- but who would be willing to > > do this these days? > > I, for one. As long as you don't change your disk geometry, it works > fine, and it's faster than any file-system related method. There's > only one problem: it doesn't work. It does. > Possibly I just used the wrong > device. Likely. You need to use the ``entire disk'' device: dd if=/dev/rsd0 of=/dev/rst0 bs=64k for the backup, and dd if=/dev/rst0 of=/dev/rsd0 bs=64k for restore. -- 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. ;-) From owner-freebsd-scsi Fri Dec 27 04:00:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA16305 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 04:00:10 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA16294 for ; Fri, 27 Dec 1996 04:00:05 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id WAA27787; Fri, 27 Dec 1996 22:28:29 +1030 (CST) From: Michael Smith Message-Id: <199612271158.WAA27787@genesis.atrad.adelaide.edu.au> Subject: Re: cvs commit: src/sys/scsi cd.c In-Reply-To: <199612251005.LAA16758@uriah.heep.sax.de> from J Wunsch at "Dec 25, 96 11:05:03 am" To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 22:28:28 +1030 (CST) Cc: freebsd-scsi@FreeBSD.org, msmith@atrad.adelaide.edu.au X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > (Moved to -scsi) Tks. Should have done that myself (lazy bum that I am). > > > Slightly re-order the sequence of commands issued, so try to send > > > the START UNIT command before testing whether the device is ready. > > > Maybe it should be done even earlier, i'm not 100 % sure. > > > > >From recent experience with a box full of disks jumpered to spin up on > > command (inadequate power supply), I'd really appreciate it if the > > START UNIT command could be sent during the probe, followed by a > > _long_ wait for the drive to become ready. > > But that's a little unrelated to this commit, right? This one was for > CDs. However, it looks as if the original drivers for sd/cd/od were > all cloned from the same, and thus inherited all the bugs... so i > think the same problem still exists in the sd driver. The "unit is not spinning" status should probably be an error/status return to the generic SCSI layer in the "ideal world". I haven't looked at Justin's new SCSI code, so I don't know if this is already the case. > Why do you want to have the disks spun up at probe time? IMHO, Because there are no other demands on the system at that point in time. As far as I'm concerned, a disk that is not spinning when it's accessed is lying down on the job, and should be prodded accordingly. Stefan's point about some disks being touchy about START UNIT is also a good one; at probe time the environment surrounding the disks is quiet and well-controlled. > it's in the function scsi_start_unit() in sys/scsi/scsi_base.c. Feel > free to bump this to 60 seconds once you know what you need. If I can find a card for the Sabre, I'll check it out. As it stands just now, I ripped the PSU out of the box and jumpered all the disks to start at poweron. Now I have to deal with the one that overheats and spins down after a couple of days. *grumble*. > (I think you could experiment with a change to the sd driver that is > similar to the cd driver change we're discussing about here.) I think I was trying to resolve an over-complicated issue on simplistic principles. If/when I get a chance to play with it again, I'll think more carefully about it. > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Fri Dec 27 08:22:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA25950 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 08:22:44 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA25938 for ; Fri, 27 Dec 1996 08:22:39 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA19377; Fri, 27 Dec 1996 17:22:14 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA03556; Fri, 27 Dec 1996 17:21:58 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA13776; Fri, 27 Dec 1996 17:02:46 +0100 (MET) From: J Wunsch Message-Id: <199612271602.RAA13776@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/scsi cd.c To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Fri, 27 Dec 1996 17:02:46 +0100 (MET) Cc: msmith@atrad.adelaide.edu.au (Michael Smith) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612271158.WAA27787@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 27, 96 10:28:28 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > The "unit is not spinning" status should probably be an error/status > return to the generic SCSI layer in the "ideal world". Why? No. For example, i've added extra code to the od driver to (optionally) take the drive down if it's idle. I know that other people have also been requesting this for fixed disks, e.g. in cases where they use it as an archive disk which is only rarely used and generates enough noise so you don't wanna have it running all the time. Actually, the guy requesting this even thought of a timeout- controlled spindown, while my code only uses device open/close events. > > Why do you want to have the disks spun up at probe time? IMHO, > > Because there are no other demands on the system at that point in time. There are no other activities on that particular drive at device open time either, provided you catch multiple open's with a driver-internal flag. Things are more complicated for a timeout-controlled spindown, but even then, you can still arrange for that target not seeing multiple commands. -- 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. ;-) From owner-freebsd-scsi Fri Dec 27 12:39:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06980 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 12:39:08 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA06974 for ; Fri, 27 Dec 1996 12:39:03 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id KAA00623; Fri, 27 Dec 1996 10:41:34 -0800 (PST) Message-ID: <32C4181D.167EB0E7@whistle.com> Date: Fri, 27 Dec 1996 10:40:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Greg Lehey CC: FreeBSD SCSI Mailing List Subject: Re: Explain this you SCSI tape experts! :-) References: <199612270825.JAA02999@freebie.lemis.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey wrote: > > Julian Elischer writes: > > J Wunsch wrote: > >> > >> As Sean Kelly wrote: > >> > >> As fate would have it, that's the very tape I need. But when I stick it > >> in the drive, FreeBSD reports BLANK CHECK. Doh! > >> > >> What could cause that? > >> > >> No idea why there's nothing on the tape, but BLANK CHECK does of > >> course mean you're trying to read beyond the recorded medium area. > > > > didi you rewind it accidentally between sets? > > did you rewind if after the last one? > > I wish I understood what happened here. I would almost guess that you > (Sean) have mistaken the tape for another one which is really blank. > In any case, it's not a question of rewinding: helical scan drives > rewind tapes before ejecting them, even if you have specified > /dev/nrst*. I can't see how you could write anything on the tape > without first writing at the start, and after loading again, it will > definitely be positioned at BOT. > > Greg I've seen people use /dev/rst0 instead of nrst0 and then every 'close' rewinds the device. If the s/w does a write data/close/open/write EOF/write EOF/close sequence on rst0 it will result in the 2xEOF (== EOM) being at the front of the tape. The tape will then return BLANK CHECK if you try read past that. From owner-freebsd-scsi Fri Dec 27 13:25:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA09207 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 13:25:54 -0800 (PST) Received: from hda.hda.com (ip62-max1-fitch.ziplink.net [199.232.245.62]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA09201 for ; Fri, 27 Dec 1996 13:25:50 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id QAA10111; Fri, 27 Dec 1996 16:22:20 -0500 From: Peter Dufault Message-Id: <199612272122.QAA10111@hda.hda.com> Subject: Re: Explain this you SCSI tape experts! :-) In-Reply-To: <32C4181D.167EB0E7@whistle.com> from Julian Elischer at "Dec 27, 96 10:40:29 am" To: julian@whistle.com (Julian Elischer) Date: Fri, 27 Dec 1996 16:22:20 -0500 (EST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I've seen people use /dev/rst0 instead of nrst0 and then every 'close' > rewinds the device. > If the s/w does a write data/close/open/write EOF/write EOF/close > sequence on rst0 it will result in the 2xEOF (== EOM) being at > the front of the tape. The tape will then return BLANK CHECK > if you try read past that. We were coincidentally discussing the following scenario in the office recently - we think it has happened (but not on FreeBSD): Something resets the SCSI bus. The tape drive rewinds. The tape driver returns EIO. The application detects the write failure and closes the tape to save as much as it can, and the tape now looks blank. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Fri Dec 27 15:05:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12765 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 15:05:32 -0800 (PST) Received: from red.stepnet.com ([206.14.120.102]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA12760 for ; Fri, 27 Dec 1996 15:05:29 -0800 (PST) Received: (from ping@localhost) by red.stepnet.com (8.8.2/8.8.2) id PAA00430 for freebsd-scsi@freebsd.org; Fri, 27 Dec 1996 15:04:53 -0800 (PST) From: Ping Mai Message-Id: <199612272304.PAA00430@red.stepnet.com> Subject: Q: ideal block size for exb 8505 To: freebsd-scsi@freebsd.org Date: Fri, 27 Dec 1996 15:04:53 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am using dump to backup to a exb 8505xl. can anyone recommand an ideal block size to get max through put? i understand that one can also set the block size using mt. how's this diff from blocksize given to dump? i am confused. thk, ping From owner-freebsd-scsi Fri Dec 27 15:52:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA14726 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 15:52:28 -0800 (PST) Received: from mailhost.pi.net (root@mailhost.pi.net [145.220.3.9]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA14713 for ; Fri, 27 Dec 1996 15:52:20 -0800 (PST) Received: from kinchenna (asd70.pi.net [145.220.192.70]) by mailhost.pi.net (8.8.3/8.7.1) with SMTP id AAA23739 for ; Sat, 28 Dec 1996 00:52:02 +0100 (MET) Posted-Date: Sat, 28 Dec 1996 00:52:02 +0100 (MET) Date: Sat, 28 Dec 96 00:37:36 Romance Standard Time From: Guido Kollerie Subject: Buslogic driver && SCSI id's > 7 To: freebsd-scsi@freebsd.org X-Mailer: Chameleon ATX 6.0, Standards Based IntraNet Solutions, NetManage Inc. X-Priority: 3 (Normal) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Last week I was installing FreeBSD 2.1.5 on a system with a Buslogic BT-958 UW-SCSI adapter. As this is a wide adapater it supports SCSI id's from 0 to 15. This is a list with the SCSI id's in use: 2: Pioneer DR-U10X SCSI-2 CDROM drive 7: BT-958 15: Fast-Wide SCSI-2 2,1 GB Fujitsu M2952QUA harddrive When I tried to boot, it recognized the adapter as a BT-946 adapter. The CDROM (id 2) was recognized but my harddrive (id 15) wasn't. Nevertheless the menu appeared and I selected Novice installation. A message appeared telling me a fdisk like program would be used to select a slice/partition. I pressed continue upon which I got a message saying no disks were found! I thought that as my adapter was recognized as a BT-946, which isn't a wide adapter and as a result doesn't support SCSI id's higher the 7, my harddisk simply couldn't be seen by the driver. Fortunately assigning a different SCSI id on the Fujitsu harddrive was very easy as the jumpers are on the front of the harddrive. I removed the four jumpers assigning the harddrive a SCSI id of 0. I rebooted my computer and this time the driver did recognize my harddrive. I was wondering if someone is working on the Buslogic driver to extend it to include full support for the Buslogic Wide adapters. This shouldn't be to hard. Thanks, Guido Kollerie. From owner-freebsd-scsi Fri Dec 27 16:19:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17366 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 16:19:30 -0800 (PST) Received: from gaia.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.2.31]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA17361 for ; Fri, 27 Dec 1996 16:19:27 -0800 (PST) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.3/8.7.3) id WAA22879; Fri, 27 Dec 1996 22:17:58 -0200 (EDT) From: Joao Carlos Mendes Luis Message-Id: <199612280017.WAA22879@gaia.coppe.ufrj.br> Subject: Re: Iomega SCSI Zip Drive To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 27 Dec 1996 22:17:57 -0200 (EDT) Cc: freebsd-scsi@freebsd.org In-Reply-To: <199612261415.PAA05373@uriah.heep.sax.de> from J Wunsch at "Dec 26, 96 03:15:54 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(J Wunsch) // As Joao Carlos Mendes Luis wrote: // // (driver for the SCSI Iomega Zip drive) // // > // Doesn't it work for you? // > // > Aside from the drop to debugger when I change disks, its perfect. // // Huh, that's not supposed to happen. Can you quote a little more from // your error messages? It drops into the debugger with "sdopen: no slices" error if I try to do a mount with no disk or immediatelly after changing disks.. (BTW: I'm running 2.1-stable ! 2.2 floppy does not boot in my machine.) // You might also try experimenting with the `od' driver. It is better // targeted for the requirements of a changeable media device. In order // to register your Zip drive with the `od' driver, you gotta add a quirk // record to sys/scsi/scsconf.c. Something like: // // Index: scsiconf.c // =================================================================== // RCS file: /home/ncvs/src/sys/scsi/scsiconf.c,v // retrieving revision 1.73 // diff -u -u -r1.73 scsiconf.c // --- scsiconf.c 1996/12/20 20:43:45 1.73 // +++ scsiconf.c 1996/12/26 14:12:52 // @@ -265,6 +265,10 @@ // T_DIRECT, T_OPTICAL, T_REMOV, "RICOH", "RO-*", "*", // "od", SC_ONE_LU // }, // + { // + T_DIRECT, T_OPTICAL, T_REMOV, "IOMEGA", "ZIP*", "*", // + "od", SC_ONE_LU // + }, // #endif /* NOD */ // #if NSD > 0 // { // // Of course, you need to replace the "ZIP*" by whatever you drive sends // as inquiry data (see the boot message logs). It's possible that the // above patch doesn't apply to non-current systems, i had to reorder // some of the entries in that table recently. But you should get the // picture. Well, I looked for it in scsiconf.c, and used this patch: ( BTW: What's an "options NEW_SCSICONF" ? :^) ) --- scsiconf.old Fri Dec 27 21:46:59 1996 +++ scsiconf.c Fri Dec 27 21:32:14 1996 @@ -342,6 +342,12 @@ T_OPTICAL, T_REMOV, "SONY", "SMO-C501-09" ,"*", "od", SC_MORE_LUS }, +#ifdef ZEUS + { + T_DIRECT, T_REMOV, "IOMEGA", "ZIP*" + , "*", "od", SC_ONE_LU + }, +#endif #endif /* NOD */ #if NSD > 0 { Note that ZEUS is my machine's name, and so the define above is true. (I checked this with grep -l ZIP /sys/compile/ZEUS/*) No luck. It still boots likes this: (disk in drive, options SCSIDEBUG, SCSI_REPORT_GEOMETRY, device od0, etc.) ... 100 nSEC ok, using 150 nSEC aha0 at 0x330-0x333 irq 11 drq 5 on isa (aha0:3:0): "CONNER CTT8000-S 1.07" type 1 removable SCSI 2 st0(aha0:3:0): Sequential-Access density code 0x45, drive empty (aha0:5:0): "IOMEGA ZIP 100 N.38" type 0 removable SCSI 2 sd0(aha0:5:0): Direct-Access sd0(aha0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry 96MB (196608 512 byte sectors) sd0(aha0:5:0): with 96 cyls, 64 heads, and an average 32 sectors/track ... If I try this one: --- scsiconf.old Fri Dec 27 21:46:59 1996 +++ scsiconf.c Fri Dec 27 21:32:14 1996 @@ -342,6 +342,12 @@ T_OPTICAL, T_REMOV, "SONY", "SMO-C501-09" ,"*", "od", SC_MORE_LUS }, +#ifdef ZEUS + { + T_DIRECT, T_REMOV, "*", "*" + , "*", "od", SC_ONE_LU + }, +#endif #endif /* NOD */ #if NSD > 0 { And no changes at all again... // -- // 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. ;-) Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-scsi Fri Dec 27 18:50:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA23457 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 18:50:13 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA23452 for ; Fri, 27 Dec 1996 18:50:10 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA00474; Sat, 28 Dec 1996 13:18:43 +1030 (CST) From: Michael Smith Message-Id: <199612280248.NAA00474@genesis.atrad.adelaide.edu.au> Subject: Re: cvs commit: src/sys/scsi cd.c In-Reply-To: <199612271602.RAA13776@uriah.heep.sax.de> from J Wunsch at "Dec 27, 96 05:02:46 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 28 Dec 1996 13:18:43 +1030 (CST) Cc: freebsd-scsi@FreeBSD.org, msmith@atrad.adelaide.edu.au X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > As Michael Smith wrote: > > > The "unit is not spinning" status should probably be an error/status > > return to the generic SCSI layer in the "ideal world". > > Why? I was visualising it as a soft error : SCSI: driver: Do can't, it's not spinning oops, start it ok, started Do ok This obviates the need to explicitly perform the start command; any command (that requires the disk to be spinning) to a disk that is not spinning will cause the error handler to start it and retry the command(s) - this then covers the case where a disk is powered down for whatever reason while it's open. > No. For example, i've added extra code to the od driver to > (optionally) take the drive down if it's idle. I know that other > people have also been requesting this for fixed disks, e.g. in cases > where they use it as an archive disk which is only rarely used and > generates enough noise so you don't wanna have it running all the > time. Actually, the guy requesting this even thought of a timeout- > controlled spindown, while my code only uses device open/close events. A lot of SCSI disks don't seem to accept STOP UNIT. (I tried that here out of interest; none of the disks I could safely unmount accepted it; admittedly that's mostly CDC and Seagate disks.) > There are no other activities on that particular drive at device open > time either, provided you catch multiple open's with a driver-internal > flag. Things are more complicated for a timeout-controlled spindown, > but even then, you can still arrange for that target not seeing > multiple commands. That's not the issue I was confronting; I was more worried about other things (perhaps not aware of the need to spin a disk up) that might give up before the disk is ready. The avoid-multiple-commands would seem to be fairly straightforward; a flag on the command that indicates that all commands before it must be complete before it is queued, and that until it is complete no other commands can be queued. > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-scsi Fri Dec 27 20:06:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA25822 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 20:06:22 -0800 (PST) Received: from red.stepnet.com ([206.14.120.102]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA25817 for ; Fri, 27 Dec 1996 20:06:19 -0800 (PST) Received: (from ping@localhost) by red.stepnet.com (8.8.2/8.8.2) id UAA01359 for freebsd-scsi@freebsd.org; Fri, 27 Dec 1996 20:05:39 -0800 (PST) From: Ping Mai Message-Id: <199612280405.UAA01359@red.stepnet.com> Subject: Q: scsi parity error? To: freebsd-scsi@freebsd.org Date: Fri, 27 Dec 1996 20:05:39 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i am getting massive scsi parity error trying to install 2.1.6, 2.2-ALPHA, and 2.2-BETA. install target is a quantum empire 2100, fresh out of the box from quantum because its predecessor died. i swapped in another scsi ribbon cable, same problem. parity is enable on the controller as well as the hd and the scsi cdrom. i checked termination settings as well. Same hw configuration used to work with metropolis, ibm, and hp drives running 2.1.5. hw config: p166 on intel tucson motherboard w/ 430hx chipset and sound, 256k cache 2940UA metrox meteor 60ns 64mb parity ram ne2000 clone (used for ftp install) nec 4x scsi cdrom teac floppy exact error message: sd0(ahc0:0:0): ABORTED COMMAND info:c53a0 asc:47,0 SCSI parity error, retires:1 i like to know if this is a problem with the drive hw, or am i doing something wrong. if it's a drive problem i need to return it to quantum asap. thanks a lot, ping From owner-freebsd-scsi Fri Dec 27 21:54:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA29471 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 21:54:02 -0800 (PST) Received: from halla.dacom.co.kr (halla.dacom.co.kr [164.124.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA29466 for ; Fri, 27 Dec 1996 21:53:59 -0800 (PST) Received: (from khr@localhost) by halla.dacom.co.kr (8.6.12h2/8.6.9) id OAA03321 for freebsd-scsi@freebsd.org; Sat, 28 Dec 1996 14:49:32 +0900 From: Kil-Hyen Ryu Message-Id: <199612280549.OAA03321@halla.dacom.co.kr> To: freebsd-scsi@freebsd.org Subject: unsubscribe Date: Sat, 28 Dec 96 14:49:32 KST Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-scsi Fri Dec 27 22:10:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA29954 for freebsd-scsi-outgoing; Fri, 27 Dec 1996 22:10:45 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA29941; Fri, 27 Dec 1996 22:10:34 -0800 (PST) Message-Id: <199612280610.WAA29941@freefall.freebsd.org> To: Guido Kollerie cc: freebsd-scsi@freebsd.org Subject: Re: Buslogic driver && SCSI id's > 7 In-reply-to: Your message of "Sat, 28 Dec 1996 00:37:36 EST." Date: Fri, 27 Dec 1996 22:10:34 -0800 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Its not hard to add this code to the Buslogic driver. You should be able to pull it almost directly from the NetBSD driver. There is even an XXX comment in the current FreeBSD driver that documents where and how you would inform the generic SCSI layer that more than 7 targets should be probed. I'm totally swamped right now or I'd do it myself. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Dec 28 07:22:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA14870 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 07:22:39 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA14864 for ; Sat, 28 Dec 1996 07:22:29 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA20062; Sat, 28 Dec 1996 16:21:40 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA03423; Sat, 28 Dec 1996 16:21:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id QAA12158; Sat, 28 Dec 1996 16:15:01 +0100 (MET) From: J Wunsch Message-Id: <199612281515.QAA12158@uriah.heep.sax.de> Subject: Re: Iomega SCSI Zip Drive To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sat, 28 Dec 1996 16:15:00 +0100 (MET) Cc: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612280017.WAA22879@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Dec 27, 96 10:17:57 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Joao Carlos Mendes Luis wrote: > // > Aside from the drop to debugger when I change disks, its perfect. > // > // Huh, that's not supposed to happen. Can you quote a little more from > // your error messages? > > It drops into the debugger with "sdopen: no slices" error if I try > to do a mount with no disk or immediatelly after changing disks.. Hmpf. Bruce? Couldn't this be avoided? > (BTW: I'm running 2.1-stable ! 2.2 floppy does not boot in my machine.) So maybe it's no longer the case in 2.2... i'm not very confident with the slice code. > Well, I looked for it in scsiconf.c, and used this patch: > ( BTW: What's an "options NEW_SCSICONF" ? :^) ) NEW_SCSICONF is the default configuration method now. > +#ifdef ZEUS NB: this will no longer work in 2.2, the machine ID doesn't get automatically converted into a -D switch. > + { > + T_DIRECT, T_REMOV, "IOMEGA", "ZIP*" > + , "*", "od", SC_ONE_LU > + }, > +#endif This could not work. You need 2.2, so you can use the ``SCSI type override code''. You might have noticed that my patch looked like: { T_DIRECT, T_OPTICAL, T_REMOV, "IOMEGA", "ZIP*" , "*", "od", SC_ONE_LU }, i.e., there's one additional field now. Even the most recent 2.2 bootblocks don't work for you? -- 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. ;-) From owner-freebsd-scsi Sat Dec 28 07:53:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15725 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 07:53:01 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA15717 for ; Sat, 28 Dec 1996 07:52:53 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA23542; Sat, 28 Dec 1996 16:52:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA03720; Sat, 28 Dec 1996 16:52:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id QAA12624; Sat, 28 Dec 1996 16:39:25 +0100 (MET) From: J Wunsch Message-Id: <199612281539.QAA12624@uriah.heep.sax.de> Subject: Re: Q: scsi parity error? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sat, 28 Dec 1996 16:39:25 +0100 (MET) Cc: ping@stepnet.com (Ping Mai) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612280405.UAA01359@red.stepnet.com> from Ping Mai at "Dec 27, 96 08:05:39 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ping Mai wrote: > exact error message: > > sd0(ahc0:0:0): ABORTED COMMAND info:c53a0 asc:47,0 SCSI parity error, retires:1 > > i like to know if this is a problem with the drive hw, or am i doing > something wrong. if it's a drive problem i need to return it to quantum asap. It's usually a problem with the drives. I used to have a similar problem with an older Seagate drive, but only after replacing my old mainboard with its BusLogic Bt742A EISA controller with an NCR 53c810. I finally gave up fighting against it, and simply didn't log the first error. (The first retry did always succeed, so other than a slightly reduced throughput, there was no ill side-effect from this.) -- 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. ;-) From owner-freebsd-scsi Sat Dec 28 07:54:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15759 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 07:54:21 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA15751 for ; Sat, 28 Dec 1996 07:54:15 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA23606; Sat, 28 Dec 1996 16:52:58 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA03729; Sat, 28 Dec 1996 16:52:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id QAA12728; Sat, 28 Dec 1996 16:49:51 +0100 (MET) From: J Wunsch Message-Id: <199612281549.QAA12728@uriah.heep.sax.de> Subject: Re: Q: ideal block size for exb 8505 To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sat, 28 Dec 1996 16:49:51 +0100 (MET) Cc: ping@red.stepnet.com (Ping Mai) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612272304.PAA00430@red.stepnet.com> from Ping Mai at "Dec 27, 96 03:04:53 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ping Mai wrote: > I am using dump to backup to a exb 8505xl. can anyone > recommand an ideal block size to get max through > put? i understand that one can also set the block size > using mt. how's this diff from blocksize given to > dump? i am confused. You can only set a fixed blocksize with mt(1). Most drives limit the ability to accept a fixed blocksize to 512 bytes, some also allow for 1024 bytes. Most (and all modern) drives don't work with a fixed block size, but with a variable one (expressed as 0). This basically means they write the amount you pass to the driver in a single write(2) call into a single tape block. Reading these blocks requires a read(2) of at least the same (or a larger) size, and will return exactly the amount of bytes that have been written into that block (i.e., will yield a `short read' when attempting to read more bytes than have been there in the tape block -- that's how restore(8) examines the tape block size). Something like 32 KB is a good value. Larger values reduce the overhead, but the impact is probably getting neglicible above something like 10 KB. Some programs default to 512 bytes only which is stupid and often causes tapes to stop streaming. physio(9) in the kernel currently slices all requests into chunks of 64 KB (this has been discussed at length recently), so you can't really read and write variable-block tapes with more than 64 KB per tape block. dump(8) stupidly even decreases that limit and chokes if you try more than 32 KB. -- 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. ;-) From owner-freebsd-scsi Sat Dec 28 14:40:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA28601 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 14:40:53 -0800 (PST) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA28581 for ; Sat, 28 Dec 1996 14:40:48 -0800 (PST) Received: from sand (sand.sentex.ca [206.222.77.6]) by granite.sentex.net (8.8.4/8.6.9) with SMTP id RAA12659 for ; Sat, 28 Dec 1996 17:43:38 -0500 (EST) Message-Id: <3.0.32.19961228173309.00973970@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 28 Dec 1996 17:33:10 -0500 To: freebsd-scsi@freebsd.org From: Mike Tancsa Subject: SCSI BUS Resets... What are the causes / solutions ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After I installed a new SCSI drive into our news server, we have been getting a lot of the following errors. I searched through the list to see if there were any other mention of it, but failed to see anything other than perhaps a power issue. However, I have a machine here at home (same power supply and motherboard Dec 28 07:43:05 flint /kernel: sd4(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x4 Dec 28 07:43:05 flint /kernel: sd4(ahc0:1:0): BUS DEVICE RESET message queued. Dec 28 07:43:07 flint /kernel: sd4(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x4 Dec 28 07:43:07 flint /kernel: ahc0: Issued Channel A Bus Reset #1. 8 SCBs aborted Dec 28 07:43:07 flint /kernel: sd2(ahc0:6:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Power on, reset, or bus device reset occurred Dec 28 07:43:08 flint /kernel: , retries:3 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:08 flint /kernel: , retries:3 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:08 flint /kernel: , retries:2 Dec 28 07:43:08 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:2 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:09 flint /kernel: , retries:1 Dec 28 07:43:09 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:10 flint /kernel: , FAILURE Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:10 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , FAILURE Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , retries:4 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:11 flint /kernel: , retries:4 Dec 28 07:43:11 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:3 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:3 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:12 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:12 flint /kernel: , retries:2 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:13 flint /kernel: , retries:2 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:13 flint /kernel: , retries:1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:13 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , retries:1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , FAILURE Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): NOT READY asc:4,1 Dec 28 07:43:14 flint /kernel: sd2(ahc0:6:0): Logical unit is in process of becoming ready Dec 28 07:43:14 flint /kernel: , FAILURE Dec 28 07:43:14 flint /kernel: sd3(ahc0:4:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:14 flint /kernel: sd3(ahc0:4:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 Dec 28 07:43:15 flint /kernel: sd4(ahc0:1:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:15 flint /kernel: sd4(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 Dec 28 07:43:15 flint /kernel: sd1(ahc0:5:0): UNIT ATTENTION asc:29,0 Dec 28 07:43:15 flint /kernel: sd1(ahc0:5:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Dec 28 07:43:15 flint /kernel: , retries:3 And then, on the new drive, that I added when I modified the disklabel, I got Dec 28 17:22:04 flint /kernel: sd5(ahc0:3:0): UNIT ATTENTION asc:29,2 Dec 28 17:22:05 flint /kernel: , retries:2 This is on a Pentium 133 with 128Meg of RAM, Adaptec 2940 version 1.16 (or might be .18) Dec 28 01:50:09 flint /kernel: FreeBSD 2.1.5-RELEASE #0: Fri Dec 27 11:32:42 EST 1996 Dec 28 01:50:09 flint /kernel: mdtancsa@flint.sentex.net:/usr/src/sys/compile/FLINT Dec 28 01:50:10 flint /kernel: CPU: 133-MHz Pentium 735\90 or 815\100 (Pentium-class CPU) Dec 28 01:50:10 flint /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Dec 28 01:50:10 flint /kernel: Features=0x1bf Dec 28 01:50:11 flint /kernel: real memory = 134217728 (131072K bytes) Dec 28 01:50:11 flint /kernel: avail memory = 130138112 (127088K bytes) Dec 28 01:50:11 flint /kernel: Probing for devices on PCI bus 0: Dec 28 01:50:12 flint /kernel: chip0 rev 1 on pci0:0 Dec 28 01:50:12 flint /kernel: chip1 rev 0 on pci0:7:0 Dec 28 01:50:12 flint /kernel: chip2 rev 0 on pci0:7:1 Dec 28 01:50:13 flint /kernel: vga0 rev 211 int a irq 11 on pci0:9 Dec 28 01:50:13 flint /kernel: ahc0 rev 3 int a irq 10 on pci0:11 Dec 28 01:50:13 flint /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs Dec 28 01:50:14 flint /kernel: ahc0 waiting for scsi devices to settle Dec 28 01:50:14 flint /kernel: (ahc0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Dec 28 01:50:15 flint /kernel: sd0(ahc0:0:0): Direct-Access 1003MB (2055035 512 byte sectors) Dec 28 01:50:15 flint /kernel: (ahc0:1:0): "SEAGATE ST31200N 8630" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd4(ahc0:1:0): Direct-Access 1006MB (2061108 512 byte sectors) Dec 28 01:50:16 flint /kernel: (ahc0:3:0): "FUJITSU M2954S-512 0124" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd5(ahc0:3:0): Direct-Access 4149MB (8498506 512 byte sectors) Dec 28 01:50:16 flint /kernel: (ahc0:4:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 Dec 28 01:50:16 flint /kernel: sd3(ahc0:4:0): Direct-Access 1006MB (2061108 512 byte sectors) Dec 28 01:50:17 flint /kernel: (ahc0:5:0): "SEAGATE ST15150N 0023" type 0 fixed SCSI 2 Dec 28 01:50:17 flint /kernel: sd1(ahc0:5:0): Direct-Access 4095MB (8388315 512 byte sectors) Dec 28 01:50:17 flint /kernel: (ahc0:6:0): "IBM DORS-32160 WA0A" type 0 fixed SCSI 2 Dec 28 01:50:17 flint /kernel: sd2(ahc0:6:0): Direct-Access 2063MB (4226725 512 byte sectors) SD0 and SD1 are both external drives and do not draw off the power supply... Are there any bugs in 2.1.5 that might be the cause of this? Our other machine is running 2.1.6 and has not seen these errors ever. ---Mike From owner-freebsd-scsi Sat Dec 28 15:52:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA02864 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 15:52:37 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA02846 for ; Sat, 28 Dec 1996 15:52:32 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA18535 (5.67b/IDA-1.5 for freebsd-scsi@FreeBSD.org); Sun, 29 Dec 1996 00:38:59 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id SAA10725; Sat, 28 Dec 1996 18:49:02 +0100 (MET) From: Wilko Bulte Message-Id: <199612281749.SAA10725@yedi.iaf.nl> Subject: Re: Q: ideal block size for exb 8505 To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 28 Dec 1996 18:49:02 +0100 (MET) Cc: freebsd-scsi@FreeBSD.org, ping@red.stepnet.com In-Reply-To: <199612281549.QAA12728@uriah.heep.sax.de> from "J Wunsch" at Dec 28, 96 04:49:51 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote... > As Ping Mai wrote: > > > I am using dump to backup to a exb 8505xl. can anyone > > recommand an ideal block size to get max through > > put? i understand that one can also set the block size > > using mt. how's this diff from blocksize given to > > dump? i am confused. > > You can only set a fixed blocksize with mt(1). Most drives limit the > ability to accept a fixed blocksize to 512 bytes, some also allow for > 1024 bytes. Most (and all modern) drives don't work with a fixed > block size, but with a variable one (expressed as 0). This basically > means they write the amount you pass to the driver in a single > write(2) call into a single tape block. Reading these blocks requires > a read(2) of at least the same (or a larger) size, and will return > exactly the amount of bytes that have been written into that block > (i.e., will yield a `short read' when attempting to read more bytes > than have been there in the tape block -- that's how restore(8) > examines the tape block size). > > Something like 32 KB is a good value. Larger values reduce the > overhead, but the impact is probably getting neglicible above > something like 10 KB. Some programs default to 512 bytes only which Keep in mind that drives that use hardware compression really appreciate a big blocksize. For example DLTs really like 32kB, 10kB is too small (for compressible data) to keep 'm really working at max efficiency. But again: highly data and device dependent. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda --------------------------------------------------------------------------