From owner-freebsd-scsi Sun Oct 5 03:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11250 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 03:21:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA11242 for ; Sun, 5 Oct 1997 03:20:52 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA01267 for freebsd-scsi@FreeBSD.ORG; Sun, 5 Oct 1997 12:20:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id LAA29323; Sun, 5 Oct 1997 11:56:00 +0200 (MET DST) Message-ID: <19971005115559.AS58851@uriah.heep.sax.de> Date: Sun, 5 Oct 1997 11:55:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Subject: Re: New SCSI Framework Patches Available References: <199710031157.VAA02092@gurney.reilly.home> <199710031835.MAA04392@pluto.plutotech.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710031835.MAA04392@pluto.plutotech.com>; from Justin T. Gibbs on Oct 3, 1997 12:35:09 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Justin T. Gibbs wrote: > So, the question is how to best handle the problem? I would prefer a transition from b_blkno to b_offset, thereby eliminating all the ``shift right here, shift back left there'' mess completely. The drawback is that b_offset needs to be 64 bits, so naturally this will lead to more bloat and slower execution on 32-bit CPUs. The second problem is that b_blkno is being abused in quite a number of places (see b_lblkno and b_pblkno), making it more work to do the transition. Of course, the latter can be thought of as an advantage, in that it requires some code cleanup. ;-) The advantage (besides of achieving the goal to support arbitrary block sizes) is that the code will be cleaner. The 64-bit problem will no longer be a problem once running on a 64-bit CPU. -- 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 Oct 5 03:55:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA12545 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 03:55:03 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA12525 for ; Sun, 5 Oct 1997 03:54:38 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id FAA00587; Sun, 5 Oct 1997 05:52:55 -0500 (EST) From: "John S. Dyson" Message-Id: <199710051052.FAA00587@dyson.iquest.net> Subject: Re: New SCSI Framework Patches Available In-Reply-To: <19971005115559.AS58851@uriah.heep.sax.de> from J Wunsch at "Oct 5, 97 11:55:59 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 5 Oct 1997 05:52:50 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 said: > > I would prefer a transition from b_blkno to b_offset, thereby > eliminating all the ``shift right here, shift back left there'' mess > completely. The drawback is that b_offset needs to be 64 bits, so > naturally this will lead to more bloat and slower execution on 32-bit > CPUs. The second problem is that b_blkno is being abused in quite a > number of places (see b_lblkno and b_pblkno), making it more work to > do the transition. Of course, the latter can be thought of as an > advantage, in that it requires some code cleanup. ;-) > > The advantage (besides of achieving the goal to support arbitrary > block sizes) is that the code will be cleaner. The 64-bit problem > will no longer be a problem once running on a 64-bit CPU. > SCSI isn't probably the best place to discuss the eventual transition from b_blkno to b_offset, but I don't think that it will cause us very much inefficiency to move to the offset representation. My opinion (guess) is due to all of the conversions that we are already doing being costly. The cost is compounded by the necessity for us to do alot of the calculations in 64bits anyway. If we think that this should be a 3.0 thing, let's make the decision ASAP, and make sure that DG, BDE, and PHK get involved in the discussions. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-scsi Sun Oct 5 04:51:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA14446 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 04:51:53 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA14430; Sun, 5 Oct 1997 04:51:25 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA02238; Sun, 5 Oct 1997 13:51:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id NAA29883; Sun, 5 Oct 1997 13:48:40 +0200 (MET DST) Message-ID: <19971005134840.AJ14406@uriah.heep.sax.de> Date: Sun, 5 Oct 1997 13:48:40 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: phk@FreeBSD.ORG (Poul-Henning Kamp), davidg@FreeBSD.ORG (David Greenman) Subject: Re: New SCSI Framework Patches Available References: <19971005115559.AS58851@uriah.heep.sax.de> <199710051052.FAA00587@dyson.iquest.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710051052.FAA00587@dyson.iquest.net>; from John S. Dyson on Oct 5, 1997 05:52:50 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: (Me, about supporting arbitrary block sizes.) > > I would prefer a transition from b_blkno to b_offset, thereby > > eliminating all the ``shift right here, shift back left there'' mess > > completely. > SCSI isn't probably the best place to discuss the eventual transition > from b_blkno to b_offset, Well, it has less babble than -hackers, and seems to have all the relevant people on it anyway. :-) > but I don't think that it will cause us very much inefficiency to > move to the offset representation. My opinion (guess) is due to all > of the conversions that we are already doing being costly. Sounds reasonable. > The cost is compounded by the necessity for us to do alot of the > calculations in 64bits anyway. If we think that this should be a > 3.0 thing, let's make the decision ASAP, I'm willing to sacrifice my scratch machine for testing. It's probably beyond my understanding to resolve the various abuses of b_blkno however. (The transition itself could probably be done in a rather mechanic way, only these abuses need to be resolved manually, and replaced by better methods for providing arbitrary `cookies'.) > and make sure that DG, BDE, and PHK get involved in the > discussions. Bruce is listening to -scsi. I'm Cc'ing David and Poul, remove your names again if you are already on the list. -- 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 Oct 5 05:20:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA15698 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 05:20:46 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA15673; Sun, 5 Oct 1997 05:20:23 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id OAA08142; Sun, 5 Oct 1997 14:19:57 +0200 (CEST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-scsi@FreeBSD.ORG, davidg@FreeBSD.ORG (David Greenman) Subject: Re: New SCSI Framework Patches Available In-reply-to: Your message of "Sun, 05 Oct 1997 13:48:40 +0200." <19971005134840.AJ14406@uriah.heep.sax.de> Date: Sun, 05 Oct 1997 14:19:57 +0200 Message-ID: <8140.876053997@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > I would prefer a transition from b_blkno to b_offset, thereby >> > eliminating all the ``shift right here, shift back left there'' mess >> > completely. I agree. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-scsi Sun Oct 5 13:47:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA08515 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 13:47:02 -0700 (PDT) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA08492; Sun, 5 Oct 1997 13:46:54 -0700 (PDT) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id XAA03723; Sun, 5 Oct 1997 23:17:25 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id WAA21379; Sun, 5 Oct 1997 22:58:50 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id WAA03779; Sun, 5 Oct 1997 22:45:54 +0200 (CEST) Message-ID: <19971005224554.62507@deepo.prosa.dk> Date: Sun, 5 Oct 1997 22:45:54 +0200 From: Philippe Regnauld To: Chuck Cc: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Tape Backup References: <199710052037.QAA00299@daisy.capecod.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 In-Reply-To: <199710052037.QAA00299@daisy.capecod.net>; from Chuck on Sun, Oct 05, 1997 at 04:37:19PM -0400 X-Operating-System: FreeBSD 2.2.1-RELEASE i386 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Cc:ed to freebsd-scsi] Chuck writes: > > Khanh Nguyen writes: > > > Does FBSD-2.2.2-REL support Hewlett Packard Colorado T3000 tape > > > backup devices? If so, has anyone configured the kernel to use this? And > > > if yes, can you send me the copy of the kernel config? > > > We're talking about the Travan SCSI HP/Colorado, right ? > > There was some talk about this drive some time ago, and IIRC, > > it has a problem with tape locking or something like it (i.e.: > > the Travan doesn't support it, and any operations to access the > > drive fail miserably). Last time I checked the archives, no > > no patch is available. Maybe check the Linux code (don't know > > if they support it). > > Alas, as I found out, non-SCSI tapes of all stripes remain unsupported > under FreeBSD-2.2.2 :-( So I forked over 3 bills and bought a TR-4, > installed it as /dev/st0, and bingo, it goes like a champ, around > 500KB/second! I thought the T3000 was scsi (travan). What tape format does the TR-4 use ? > Alas, over an ethernet from another FreeBSD 2.2.2 system using dump, > it hiccuped continuously, getting just about 50KB/second. > Is there any fix for that, like perhaps a humongous buffer? I figured, > since the average data rate was 50KB/sec., and the hiccups averaged > 4 seconds, I was buffering about 200KB. Can I buffer say, 10MB? I expereienced the same problem with an old DAT drive and remote dump -- 50K/sec where I usualy get 200. This with a 2.2.1 laptop dumping to a -current machine. -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-scsi Sun Oct 5 14:05:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09300 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 14:05:53 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA09280; Sun, 5 Oct 1997 14:05:39 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA20636; Sun, 5 Oct 1997 13:50:51 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020634; Sun Oct 5 20:50:42 1997 Message-ID: <3437FD62.7D55368C@whistle.com> Date: Sun, 05 Oct 1997 13:49:39 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Poul-Henning Kamp CC: Joerg Wunsch , freebsd-scsi@FreeBSD.ORG, David Greenman Subject: Re: New SCSI Framework Patches Available References: <8140.876053997@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: my new disk layer stuff basically works in byte offsets. it starts with b_blkno, but all comparisins etc. end up being u_int64_t based.. (offset_t?) I'd rather see byte offsets ASAP, so that it matches the resid and other count values. of course it makes it easier to accidentally try do non-alligned transfers, but if you are making that big a, then othingis likely to help you except having your code rejected too much. > > >> > I would prefer a transition from b_blkno to b_offset, thereby > >> > eliminating all the ``shift right here, shift back left there'' mess > >> > completely. > > I agree. me too though I'd like to leave the b_pblkno, or maybe make it a b_poffset. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-scsi Sun Oct 5 19:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA24727 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 19:01:43 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from daisy.capecod.net (poca33.capecod.net [205.230.13.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA24719; Sun, 5 Oct 1997 19:01:32 -0700 (PDT) (envelope-from crtb@daisy.capecod.net) Received: (from crtb@localhost) by daisy.capecod.net (8.8.5/8.8.5) id WAA00761; Sun, 5 Oct 1997 22:00:58 -0400 (EDT) Date: Sun, 5 Oct 1997 22:00:58 -0400 (EDT) From: Chuck Message-Id: <199710060200.WAA00761@daisy.capecod.net> To: crtb@capecod.net, regnauld@deepo.prosa.dk Subject: Re: Tape Backup Cc: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Philippe writes: >Chuck writes: >> > Khanh Nguyen writes: >> > > Does FBSD-2.2.2-REL support Hewlett Packard Colorado T3000 tape >> > > backup devices? If so, has anyone configured the kernel to use this? And >> > > if yes, can you send me the copy of the kernel config? >> >> > We're talking about the Travan SCSI HP/Colorado, right ? >> > There was some talk about this drive some time ago, and IIRC, >> > it has a problem with tape locking or something like it (i.e.: >> > the Travan doesn't support it, and any operations to access the >> > drive fail miserably). Last time I checked the archives, no >> > no patch is available. Maybe check the Linux code (don't know >> > if they support it). >> >> Alas, as I found out, non-SCSI tapes of all stripes remain unsupported >> under FreeBSD-2.2.2 :-( So I forked over 3 bills and bought a TR-4, >> installed it as /dev/st0, and bingo, it goes like a champ, around >> 500KB/second! > > I thought the T3000 was scsi (travan). > What tape format does the TR-4 use ? 2 quesions; My TR-3 machine is an Exabyte Eagle, straight ISA, with its own board. Very nice if you run Micxxxxft OS, but unsupported in FreeBSD. There may also be a SCSI version. The TR-4 is apparently different. The cartridges look identical, but the TR-3 says 1.6GB, while the TR-4 says 4GB. Plastic, with an aluminum plate on one side. The format is evidently multiple passes end to end, with the head moving a tiny bit between passes, just like the old tapes. >> Alas, over an ethernet from another FreeBSD 2.2.2 system using dump, >> it hiccuped continuously, getting just about 50KB/second. >> Is there any fix for that, like perhaps a humongous buffer? I figured, >> since the average data rate was 50KB/sec., and the hiccups averaged >> 4 seconds, I was buffering about 200KB. Can I buffer say, 10MB? I'd still like to know if this is possible. > I expereienced the same problem with an old DAT drive and > remote dump -- 50K/sec where I usualy get 200. This with a 2.2.1 > laptop dumping to a -current machine. > >-- > >-[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- >-[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- Chuck Bacon - crtb@capecod.net From owner-freebsd-scsi Sun Oct 5 22:20:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA04537 for freebsd-scsi-outgoing; Sun, 5 Oct 1997 22:20:54 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA04525 for ; Sun, 5 Oct 1997 22:20:48 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA12284 for freebsd-scsi@FreeBSD.ORG; Mon, 6 Oct 1997 07:20:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA02778; Mon, 6 Oct 1997 07:09:33 +0200 (MET DST) Message-ID: <19971006070933.HO48297@uriah.heep.sax.de> Date: Mon, 6 Oct 1997 07:09:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Subject: Re: New SCSI Framework Patches Available References: <8140.876053997@critter.freebsd.dk> <3437FD62.7D55368C@whistle.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3437FD62.7D55368C@whistle.com>; from Julian Elischer on Oct 5, 1997 13:49:39 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > I'd rather see byte offsets ASAP, so that it matches the resid and > other count values. of course it makes it easier to accidentally > try do non-alligned transfers, but if you are making that big a, > then othingis likely to help you except having your code rejected > too much. (Well, i can't parse the above sentence really, but hope to have figured out what it meant. :) Drivers are expected to reject requests that don't match the underlying physical device anyway. IMHO, all (most ?) of our drivers do this already. That's why people see an EINVAL when trying to disklabel a 2048-byte sectored MO media (the label is attempted to be read/written with a granularity of 512 bytes). (General consensus) > though I'd like to leave the b_pblkno, or maybe make it a b_poffset. What for? Hmm, maybe. Slices are evil. :-) -- 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 Mon Oct 6 00:40:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11067 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 00:40:39 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA11062 for ; Mon, 6 Oct 1997 00:40:36 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA29502; Mon, 6 Oct 1997 00:35:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029500; Mon Oct 6 07:35:24 1997 Date: Mon, 6 Oct 1997 00:34:20 -0700 (PDT) From: Julian Elischer To: Joerg Wunsch cc: freebsd-scsi@FreeBSD.ORG Subject: Re: New SCSI Framework Patches Available In-Reply-To: <19971006070933.HO48297@uriah.heep.sax.de> 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 On Mon, 6 Oct 1997, J Wunsch wrote: > As Julian Elischer wrote: > > > I'd rather see byte offsets ASAP, so that it matches the resid and > > other count values. of course it makes it easier to accidentally > > try do non-alligned transfers, but if you are making that big a, > > then othingis likely to help you except having your code rejected > > too much. > > (Well, i can't parse the above sentence really, but hope to have > figured out what it meant. :) sorry typing on a bad line.. I think what was showing on my screen and what was sent did not correlate.. should read: "making that big a mess of things, then nothing is likely to help you, except having your code (should have said requests) rejected too much" i.e lots of really annoying messages to prod you into fixing it. > > Drivers are expected to reject requests that don't match the > underlying physical device anyway. IMHO, all (most ?) of our drivers > do this already. That's why people see an EINVAL when trying to > disklabel a 2048-byte sectored MO media (the label is attempted to be > read/written with a granularity of 512 bytes). > > (General consensus) yes > > > though I'd like to leave the b_pblkno, or maybe make it a b_poffset. > > What for? Hmm, maybe. Slices are evil. :-) you have to store the physical block number etc. somewhere so that when the request returns the original info is not destroyed, because the read request may be broken by physio() to be done in several chunks and you don't want to lose info. in fact the trouble is that you really want to save the initial state of the buf struct, or have a different version for each layer you go through.. I'm re-implimenting the slice code, and have run up against this. I'm not sure which entries in the buf I can clobber at low layers, and which I can't. I have the generic framework up and running, and slices being dynamically added etc. from a scsi disk vi an MBR handler. I have not yet written the disklabel handler. I'm using a floppy for testing.. :) (have fdisk'd a floppy) > > -- > 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 Mon Oct 6 06:26:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27509 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 06:26:55 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27488 for ; Mon, 6 Oct 1997 06:26:24 -0700 (PDT) (envelope-from richard@stevenson.cogsci.ed.ac.uk) Received: (from richard@localhost) by stevenson.cogsci.ed.ac.uk (8.8.5/8.8.5) id OAA04524; Mon, 6 Oct 1997 14:26:12 +0100 (BST) Date: Mon, 6 Oct 1997 14:26:12 +0100 (BST) Message-Id: <199710061326.OAA04524@stevenson.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Tape Backup To: Philippe Regnauld In-Reply-To: Philippe Regnauld's message of Sun, 5 Oct 1997 22:45:54 +0200 Organization: just say no Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > We're talking about the Travan SCSI HP/Colorado, right ? > > > There was some talk about this drive some time ago, and IIRC, > > > it has a problem with tape locking or something like it There's a harmless error message because the drive doesn't support locking the tape in, and the driver incorrectly doesn't pass SCSI_SILENT or whatever. There was also a problem that they required some bit I forget to be set. I've posted a patch for this several times, but it appears to have been fixed in more recent microcode. Just download the latest microcode from HP and patch it under DOS (yuk). > I thought the T3000 was scsi (travan). SCSI and Travan are orthogonal. I don't know anything about the T3000, it was the T4000s that I had. the "s" means SCSI. > What tape format does the TR-4 use ? TR-4 *is* the tape format, also known as QIC3095. > > Alas, over an ethernet from another FreeBSD 2.2.2 system using dump, > > it hiccuped continuously, getting just about 50KB/second. I used to use a blocksize of 128k, which was fine. However the current dump doesn't allow >64k, and that isn't fine. I know the kernel limits it to 64k, but giving a larger size to dump undeniably made it work better. > > Is there any fix for that, like perhaps a humongous buffer? I figured, > > since the average data rate was 50KB/sec., and the hiccups averaged > > 4 seconds, I was buffering about 200KB. Can I buffer say, 10MB? You could write a trivial C program that buffered as much as you like. HOWEVER, these Travan drives absolutely suck. I've had 3 replacements from HP in two weeks, and *NONE of them work*. -- Richard From owner-freebsd-scsi Mon Oct 6 06:31:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27903 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 06:31:44 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27883 for ; Mon, 6 Oct 1997 06:31:35 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id QAA11000; Mon, 6 Oct 1997 16:02:02 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id PAA22768; Mon, 6 Oct 1997 15:43:29 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id PAA05795; Mon, 6 Oct 1997 15:30:24 +0200 (CEST) Message-ID: <19971006153024.62498@deepo.prosa.dk> Date: Mon, 6 Oct 1997 15:30:24 +0200 From: Philippe Regnauld To: Richard Tobin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape Backup References: <199710061326.OAA04524@stevenson.cogsci.ed.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 In-Reply-To: <199710061326.OAA04524@stevenson.cogsci.ed.ac.uk>; from Richard Tobin on Mon, Oct 06, 1997 at 02:26:12PM +0100 X-Operating-System: FreeBSD 2.2.1-RELEASE i386 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Richard Tobin writes: > > > > Is there any fix for that, like perhaps a humongous buffer? I figured, > > > since the average data rate was 50KB/sec., and the hiccups averaged > > > 4 seconds, I was buffering about 200KB. Can I buffer say, 10MB? > > You could write a trivial C program that buffered as much as you like. Use team(1) ? > HOWEVER, these Travan drives absolutely suck. I've had 3 replacements > from HP in two weeks, and *NONE of them work*. You bet. -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-scsi Mon Oct 6 06:37:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA28263 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 06:37:33 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA28255; Mon, 6 Oct 1997 06:37:24 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA03686; Mon, 6 Oct 1997 23:35:17 +1000 Date: Mon, 6 Oct 1997 23:35:17 +1000 From: Bruce Evans Message-Id: <199710061335.XAA03686@godzilla.zeta.org.au> To: julian@whistle.com, phk@critter.freebsd.dk Subject: Re: New SCSI Framework Patches Available Cc: davidg@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >my new disk layer stuff basically works in byte offsets. >it starts with b_blkno, but all comparisins etc. end up being >u_int64_t based.. > >(offset_t?) off_t? Other parts of the system don't even pretend to support offsets >= 2^63. Negative offsets on disks are errors, but negative relative offsets may be useful. >> >> > I would prefer a transition from b_blkno to b_offset, thereby >> >> > eliminating all the ``shift right here, shift back left there'' mess >> >> > completely. >> >> I agree. >me too There is no way to eliminate the shift that converts filesystem blocks to disk blocks or bytes. Currently, this is the only shift invovled in the usual case where the h/w block size == DEV_BSIZE (at least in 2.2; in -current there are several evil multiplications and divisions in sd.c and od.c just to support unusual cases). If offsets were used everywhere, there would be an additional shifts or division to convert from byte offsets to h/w block numbers. >though I'd like to leave the b_pblkno, or maybe make it a b_poffset. I think it should be a block number (in h/w disk block size units) and all checking and conversions of buffer offsets and ranges should be centralized in dscheck(). It doesn't need to be 64 bits yet. I think the (time) bloat for b_offset instead of b_blkno would be less than the current bloat for just one of the evil divisions in sd.c. Not good, but probably acceptable. Bruce From owner-freebsd-scsi Mon Oct 6 07:42:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02243 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 07:42:11 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from mail.kcwc.com (h1.kcwc.com [206.139.252.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA02235; Mon, 6 Oct 1997 07:42:08 -0700 (PDT) (envelope-from curt@kcwc.com) Received: by mail.kcwc.com (NX5.67c/NeXT-2.0-KCWC-1.0) id AA04878; Mon, 6 Oct 97 10:41:49 -0400 Date: Mon, 6 Oct 97 10:41:49 -0400 From: curt@kcwc.com (Curt Welch) Message-Id: <9710061441.AA04878@mail.kcwc.com> Received: by NeXT.Mailer (1.87.1) Received: by NeXT Mailer (1.87.1) To: freebsd-isp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Tape Backup Cc: curt@kcwc.com Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Philippe writes: >Chuck writes: >> > Khanh Nguyen writes: >> > > Does FBSD-2.2.2-REL support Hewlett Packard Colorado T3000 tape >> > > backup devices? If so, has anyone configured the kernel to use this? And >> > > if yes, can you send me the copy of the kernel config? >> >> > We're talking about the Travan SCSI HP/Colorado, right ? I have an HP Colorado T4000s. It's a SCSI drive which uses TR-4 tapes. I have two of them. Don't know what the guy above was talking about. >> > There was some talk about this drive some time ago, and IIRC, >> > it has a problem with tape locking or something like it (i.e.: >> > the Travan doesn't support it, and any operations to access the >> > drive fail miserably). Last time I checked the archives, no >> > no patch is available. Maybe check the Linux code (don't know >> > if they support it). >> >> Alas, as I found out, non-SCSI tapes of all stripes remain unsupported >> under FreeBSD-2.2.2 :-( So I forked over 3 bills and bought a TR-4, >> installed it as /dev/st0, and bingo, it goes like a champ, around >> 500KB/second! > > I thought the T3000 was scsi (travan). > What tape format does the TR-4 use ? > 2 quesions; My TR-3 machine is an Exabyte Eagle, straight > ISA, with its own board. Very nice if you run Micxxxxft > OS, but unsupported in FreeBSD. There may also be a SCSI > version. The TR-4 is apparently different. The > cartridges look identical, but the TR-3 says 1.6GB, while > the TR-4 says 4GB. Plastic, with an aluminum plate on > one side. The format is evidently multiple passes end > to end, with the head moving a tiny bit between passes, > just like the old tapes. No, it's not multiple passes. It's a single pass format. And yes, it holds around 4GB (uncompressed). I think it just has some huge number of tracks - something like 75. I get around 450 KB/sec. You have to use fairly large block sizes to keep it streaming (32KB works for me). Also, you get error messages from the kernel everytime you access the drive. This is fixed by changing a line in /sys/scsi/st.c (around line 436): (someone on the net posted this fix) scsi_prevent(sc_link, PR_PREVENT, 0); /* who cares if it fails? */ To: scsi_prevent(sc_link, PR_PREVENT, SCSI_SILENT | SCSI_ERR_OK); This just makes the kernel not complain about a command that the T4000s doesn't support. This "fix" doesn't make the drive work any different, it just keeps the kernel from printing the message. >> Alas, over an ethernet from another FreeBSD 2.2.2 system using dump, >> it hiccuped continuously, getting just about 50KB/second. I had a similar problem that turnd out to be the ethernet card I was using. It seemed to work fine, but if I did large ftp's etc it would slow to a crawl. I didn't notice the problem until I tried to do an rdump. Make sure you problem is not your network. Do some large ftp's or rcp's and make sure you get the transfer rates you expect. Curt Welch http://CurtWelch.Com/ From owner-freebsd-scsi Mon Oct 6 13:31:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26302 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 13:31:28 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26289; Mon, 6 Oct 1997 13:31:20 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA16442; Mon, 6 Oct 1997 13:26:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd016440; Mon Oct 6 20:26:30 1997 Message-ID: <34394935.1F1A7590@whistle.com> Date: Mon, 06 Oct 1997 13:25:25 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: phk@critter.freebsd.dk, davidg@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de Subject: Re: New SCSI Framework Patches Available References: <199710061335.XAA03686@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: [stuff with which I have no arguments] > > I think it should be a block number (in h/w disk block size units) > and all checking and conversions of buffer offsets and ranges should be > centralized in dscheck(). It doesn't need to be 64 bits yet. dscheck doesn't exist in my kernels here any more (except in the old compatibility module) > > I think the (time) bloat for b_offset instead of b_blkno would be less > than the current bloat for just one of the evil divisions in sd.c. Not > good, but probably acceptable. my new code makes no assumptions about blocksize. sd.c wd.c and fd.c have no interst in locksizes (except to set some variables). That's all done at higher layers. > > Bruce From owner-freebsd-scsi Mon Oct 6 15:32:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA04655 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 15:32:06 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA04562; Mon, 6 Oct 1997 15:31:53 -0700 (PDT) (envelope-from kachun@zippo.com) Received: from dvl-1.pathlink.com (kachun@dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.6/8.8.7) with SMTP id PAA25655; Mon, 6 Oct 1997 15:38:21 -0700 (PDT) Message-Id: <199710062238.PAA25655@dopey.pathlink.com> To: freebsd-scsi@freebsd.org Subject: Re: AHC error messages with 2.2.5-BETA Cc: freebsd-stable@freebsd.org From: kachun@zippo.com (Kachun Lee) Date: Mon, 06 Oct 1997 15:31:49 -0700 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: <616rbe$758@news.pathlink.com> References: <616rbe$758@news.pathlink.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <616rbe$758@news.pathlink.com>, you say... > >I has a P6 200mhz system running 2.2-releng to the latest 2.2.5-BETA that >had 2 2740 controllers. I replaced 1 of 2740 with a 3740 when I added an >extra drive to it and splitted 12 drives into 3 channels. The system has >been generating the following errors about twice a day with different >drives/ahc channel... > >Oct 4 16:16:39 clark /kernel: ahc1: WARNING no command for scb 99 (cmdcmplt) >Oct 4 16:16:39 clark /kernel: QOUTCNT == 1 > [snip] The above system crashed twice (same sd8, which was running for 1 yr with the 2740) during the past couple days. I can't tell if it is specific to 2.2.5-BETA, since I exchanged a 2740 with a 3740 then upgraded to 2.2.5-BETA. In the meantime, I am trying to do something by disabled SCBPAGING. Any comment would be greately appreciated. Best regards. --------------------------------------------------------- sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): Target Busy sd8(ahc1:10:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted field rep laceable unit: 1 , retries:4 sd8(ahc1:10:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb Ordered Tag queued Ordered Tag sent sd8(ahc1:10:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb sd8(ahc1:10:0): Queueing an Abort SCB sd8(ahc1:10:0): Abort Message Sent sd8(ahc1:10:0): SCB 7 - Abort Tag Completed. sd8(ahc1:10:0): no longer in timeout ahc1: WARNING no command for scb 0 (cmdcmplt) QOUTCNT == 1 sd9(ahc1:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued Ordered Tag sent sd9(ahc1:11:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd9(ahc1:11:0): Queueing an Abort SCB sd9(ahc1:11:0): Abort Message Sent sd9(ahc1:11:0): SCB 5 - Abort Tag Completed. sd9(ahc1:11:0): no longer in timeout sd8(ahc1:10:0): data overrun of 16736233 bytes detected in Data-In phase. Tag = = 0x0. Forcing a retry. sd8(ahc1:10:0): Have seen Data Phase. Length = 40960. NumSGs = 10. sg[0] - Addr 0xc852000 : Length 4096 sg[1] - Addr 0xbad3000 : Length 4096 sg[2] - Addr 0x9ad4000 : Length 4096 sg[3] - Addr 0x995000 : Length 4096 sg[4] - Addr 0x8ad8000 : Length 4096 sg[5] - Addr 0x4357000 : Length 4096 sg[6] - Addr 0xbd8000 : Length 4096 sg[7] - Addr 0x64d9000 : Length 4096 sg[8] - Addr 0x7a9a000 : Length 4096 sg[9] - Addr 0xa89b000 : Length 4096 sd8(ahc1:10:0): data overrun of 16719337 bytes detected in Data-In phase. Tag = = 0x0. Forcing a retry. sd8(ahc1:10:0): Haven't seen Data Phase. Length = 40960. NumSGs = 10. sg[0] - Addr 0xc852000 : Length 4096 sg[1] - Addr 0xbad3000 : Length 4096 sg[2] - Addr 0x9ad4000 : Length 4096 sg[3] - Addr 0x995000 : Length 4096 sg[4] - Addr 0x8ad8000 : Length 4096 sg[5] - Addr 0x4357000 : Length 4096 sg[6] - Addr 0xbd8000 : Length 4096 sg[7] - Addr 0x64d9000 : Length 4096 sg[8] - Addr 0x7a9a000 : Length 4096 sg[9] - Addr 0xa89b000 : Length 4096 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x513c4073 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019d510 stack pointer = 0x10:0xefbffac8 frame pointer = 0x10:0xefbffad4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 107 (nfsd) interrupt mask = panic: page fault syncing disks... From owner-freebsd-scsi Mon Oct 6 16:02:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06785 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 16:02:12 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from veda.is (adam@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA06751; Mon, 6 Oct 1997 16:01:43 -0700 (PDT) (envelope-from adam@veda.is) Received: (from adam@localhost) by veda.is (8.8.7/8.8.5) id XAA10829; Mon, 6 Oct 1997 23:00:38 GMT From: Adam David Message-Id: <199710062300.XAA10829@veda.is> Subject: fixing bad SCSI sectors? To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Date: Mon, 6 Oct 1997 23:00:38 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL31 (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 How do I start fixing this disk? It suddenly developed these errors after a "bt0 not accepting commands" hang, while a second identical disk on the same 445C controller was unaffected. fsck and dd are of no use while there are sectors with hard errors. Do I need to use scsi(8) to remap or reformat the sectors, and which command bytes would be needed? Or is there an easier way other than reformatting the whole disk? The BT BIOS utility lists the units found on the SCSI bus when asked to verify the disk, which is an identical result to the next option down on the diagnostic menu (the one that is supposed to display this information). Here are the errors... (first round) sd1: MEDIUM ERROR info:0x2a0 asc:12,0 Address mark not found for id field , retries:4 sd1: MEDIUM ERROR info:0x29f asc:16,4, retries:3 sd1: MEDIUM ERROR info:0x2a1 asc:12,0 Address mark not found for id field , retries:2 sd1: MEDIUM ERROR info:0x2a0 asc:12,0 Address mark not found for id field , retries:1 sd1: MEDIUM ERROR info:0x2a0 asc:12,0 Address mark not found for id field , FAILURE And why is there space before the commas? So, how do I repair the disk without completely reformatting it? Please? :) --------------------------------------------------------------------------- | Adam David | What's a bigger annoyance than toll bridges? | | | Bill Gates! | +========================+ Why? | | Because we're _still_ waiting for him to put the curtains on Windows! | From owner-freebsd-scsi Mon Oct 6 23:50:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02626 for freebsd-scsi-outgoing; Mon, 6 Oct 1997 23:50:55 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA02615 for ; Mon, 6 Oct 1997 23:50:50 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA07820; Tue, 7 Oct 1997 08:50:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA08003; Tue, 7 Oct 1997 08:39:16 +0200 (MET DST) Message-ID: <19971007083916.RV43899@uriah.heep.sax.de> Date: Tue, 7 Oct 1997 08:39:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: adam@veda.is (Adam David) Subject: Re: fixing bad SCSI sectors? References: <199710062300.XAA10829@veda.is> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710062300.XAA10829@veda.is>; from Adam David on Oct 6, 1997 23:00:38 +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > How do I start fixing this disk? By formatting it... > So, how do I repair the disk without completely reformatting it? Oh... Well, try to turn on AWRE/ARRE (mode page 1), and force a write to those blocks. The block numbers are mentioned in the `info' field. Note that they are absolute for the disk, i.e. use them as an lseek offset for /dev/rsd1. Alas, dd(1) doesn't lseek on raw devices when using "seek=". Hmm, our dd man page suggests it were seeking on anything but tape devices... Try it before using. -- 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 Tue Oct 7 04:39:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA18979 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 04:39:51 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA18967 for ; Tue, 7 Oct 1997 04:39:47 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.8.5/8.8.5) with SMTP id IAA17167 for ; Tue, 7 Oct 1997 08:38:47 -0300 (EST) Date: Tue, 7 Oct 1997 08:38:47 -0300 (EST) From: Paulo Fragoso To: freebsd-scsi@freebsd.org Subject: HP 6020 WORMIOFIXATION 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, I was using FBSD 2.2.1 and HP writer 6020 it was work fine. After upgrade to FBSD 2.2.2 and Pentium 200MHz (before 133MHz) have errors in fixate: Place CD in the worm drive now and press return: 582698 kilobytes, 1935 seconds 1165396+0 records in 29134+1 records out 596682752 bytes transferred in 1945.585739 secs (306685 bytes/sec) wormcontrol: ioctl(WORMIOFIXATION): Input/output error ^^^^^^^^^^^^^^ in dmesg: sd1(ahc0:2:0): SCB 0x0 - timed out in command phase, SCSISIGI == 0x84 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 worm0(ahc0:4:0): abort message in message buffer worm0(ahc0:4:0): SCB 0x1 - timed out in command phase, SCSISIGI == 0x94 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc0: Issued Channel A Bus Reset. 3 SCBs aborted Clearing bus reset Clearing 'in-reset' flag worm0(ahc0:4:0): no longer in timeout sd1(ahc0:2:0): UNIT ATTENTION asc:29,0 sd1(ahc0:2:0): Power on, reset, or bus device reset occurred , retries:3 ahc0:A:4: refuses synchronous negotiation. Using asynchronous transfers What's heppening? Are there any solution? Thanks, Paulo. From owner-freebsd-scsi Tue Oct 7 06:55:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27128 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 06:55:16 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from elvis.mu.org (paul@elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27121 for ; Tue, 7 Oct 1997 06:55:12 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (4.1/4.1) id IAA08824 for freebsd-scsi@freebsd.org; Tue, 7 Oct 1997 08:55:53 -0500 (CDT) From: Paul Saab Message-Id: <199710071355.IAA08824@elvis.mu.org> Subject: errors.. hosed? To: freebsd-scsi@freebsd.org Date: Tue, 7 Oct 1997 08:55:53 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (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 take it this means the disk is bad? sd4(ahc1:2:0): MEDIUM ERROR info:915f5 csi:1,e8,1,79 asc:11,0 Unrecovered read error field replaceable unit: 15 , retries:4 sd4(ahc1:2:0): MEDIUM ERROR info:821dc csi:1,b5,1,4 asc:11,0 Unrecovered read error field replaceable unit: 15 , retries:4 sd4(ahc1:2:0): MEDIUM ERROR info:959b7 csi:1,f6,1,6b asc:11,0 Unrecovered read error field replaceable unit: 15 , retries:4 Paul From owner-freebsd-scsi Tue Oct 7 08:13:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02577 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 08:13:23 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from veda.is (root@veda.is [193.4.230.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02448 for ; Tue, 7 Oct 1997 08:11:27 -0700 (PDT) (envelope-from adam@veda.is) Received: from ubiq.veda.is (adam@ubiq.veda.is [193.4.230.60]) by veda.is (8.8.7/8.8.5) with ESMTP id PAA19526; Tue, 7 Oct 1997 15:06:41 GMT From: Adam David Received: (from adam@localhost) by ubiq.veda.is (8.8.7/8.8.5) id PAA00374; Tue, 7 Oct 1997 15:06:35 GMT Message-Id: <199710071506.PAA00374@ubiq.veda.is> Subject: Re: fixing bad SCSI sectors? In-Reply-To: <19971007083916.RV43899@uriah.heep.sax.de> from J Wunsch at "Oct 7, 97 08:39:16 am" To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 7 Oct 1997 15:06:34 +0000 (GMT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 > > How do I start fixing this disk? > > By formatting it... This has been most weird. I figured out eventually that the device list was a menu of devices to choose from, and did a "Verify" from the BT445C BIOS. As soon as it hit sector 0x2a0 (deduced from previous context), it bailed out with "Verify Failed !". The disk is now up and running again... after a thorough massage, taking about 6 hours of repeated assaults. This is roughly what it took: 1. SCSI BIOS Verify --> Failed early 2. Switch off the power and wait for 30 seconds 3. SCSI BIOS Verify --> Failed late 4. Repeat 3 or more times from 1. --> Succeeded 5. fsck --> Failed late, bt0 not taking commands (same sector broke each time) 6. Repeat 3 or more times from 2. omitting Verify on final pass --> Succeeded I've no idea whether anything was remapped, the SCSI BIOS utility only reports success or failure. > Alas, dd(1) doesn't lseek on raw devices when using "seek=". ... and/or "skip="... but I guess it should do? Anyway, it turned out this time to be a hardware (not a media) problem by the looks of it. It was the wrong phase of the moon for this controller at an age of 3 years. I hope this doesn't happen every month. Does anyone know why the BT44x controllers are prone to this kind of lockup, and whether anything can be done about it? -- Adam David From owner-freebsd-scsi Tue Oct 7 14:15:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23377 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 14:15:40 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA23353 for ; Tue, 7 Oct 1997 14:15:30 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 7072 invoked from network); 7 Oct 1997 21:15:19 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 7 Oct 1997 21:15:19 -0000 From: "Evan Champion" To: Subject: DPT Driver Date: Tue, 7 Oct 1997 17:15:17 -0400 Message-ID: <01bcd366$1c321360$513654c7@cello.synapse.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Where can I pick up the DPT RAID controller driver from? Evan From owner-freebsd-scsi Tue Oct 7 15:21:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27656 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 15:21:48 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA27631 for ; Tue, 7 Oct 1997 15:21:43 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA03007; Wed, 8 Oct 1997 00:21:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA11641; Wed, 8 Oct 1997 00:16:45 +0200 (MET DST) Message-ID: <19971008001644.YV43395@uriah.heep.sax.de> Date: Wed, 8 Oct 1997 00:16:44 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: paulo@nlink.com.br (Paulo Fragoso) Subject: Re: HP 6020 WORMIOFIXATION References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Paulo Fragoso on Oct 7, 1997 08:38:47 -0300 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Paulo Fragoso wrote: > I was using FBSD 2.2.1 and HP writer 6020 it was work fine. After upgrade > to FBSD 2.2.2 and Pentium 200MHz (before 133MHz) have errors in fixate: There's a known bug in 2.2-stable (about to be fixed anytime soon), but your problem rather smells like a problem with the ahc driver. -- 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 Tue Oct 7 15:22:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27734 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 15:22:49 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA27726 for ; Tue, 7 Oct 1997 15:22:44 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA03017; Wed, 8 Oct 1997 00:22:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA11675; Wed, 8 Oct 1997 00:20:47 +0200 (MET DST) Message-ID: <19971008002047.AG30116@uriah.heep.sax.de> Date: Wed, 8 Oct 1997 00:20:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: paul@mu.org (Paul Saab) Subject: Re: errors.. hosed? References: <199710071355.IAA08824@elvis.mu.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710071355.IAA08824@elvis.mu.org>; from Paul Saab on Oct 7, 1997 08:55:53 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Paul Saab wrote: > I take it this means the disk is bad? > > sd4(ahc1:2:0): MEDIUM ERROR info:915f5 csi:1,e8,1,79 asc:11,0 Unrecovered read error field replaceable unit: 15 Basically, yes. Do you have automatic sector replacement enabled (mode page 1, see scsi(8))? Reformatting the disk (scsiformat(8)) might help, since it usually rebuilds the bad sector table as well. -- 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 Tue Oct 7 19:33:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11022 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 19:33:25 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA11016 for ; Tue, 7 Oct 1997 19:33:23 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA03386; Tue, 7 Oct 1997 19:26:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003384; Wed Oct 8 02:26:47 1997 Message-ID: <343AEF25.1D706F6D@whistle.com> Date: Tue, 07 Oct 1997 19:25:41 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Paul Saab CC: freebsd-scsi@FreeBSD.ORG Subject: Re: errors.. hosed? References: <199710071355.IAA08824@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Paul Saab wrote: > > I take it this means the disk is bad? > > sd4(ahc1:2:0): MEDIUM ERROR info:915f5 csi:1,e8,1,79 asc:11,0 Unrecovered read error field replaceable unit: 15 > , retries:4 > sd4(ahc1:2:0): MEDIUM ERROR info:821dc csi:1,b5,1,4 asc:11,0 Unrecovered read error field replaceable unit: 15 > , retries:4 > sd4(ahc1:2:0): MEDIUM ERROR info:959b7 csi:1,f6,1,6b asc:11,0 Unrecovered read error field replaceable unit: 15 > , retries:4 > > Paul yes but it DID recover the data.. you shold do a scsi -f /dev/rsd4.ctl -e -m 1 and set the first 2 entries to 1 so that the disk will spare those sectors out when it gets an error. From owner-freebsd-scsi Tue Oct 7 22:45:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA21822 for freebsd-scsi-outgoing; Tue, 7 Oct 1997 22:45:57 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA21799 for ; Tue, 7 Oct 1997 22:45:52 -0700 (PDT) (envelope-from shimon@sendero-ppp.i-connect.net) Received: (qmail 29119 invoked by uid 1000); 8 Oct 1997 05:46:18 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-100597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <01bcd366$1c321360$513654c7@cello.synapse.net> Date: Tue, 07 Oct 1997 22:46:18 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Evan Champion" Subject: RE: DPT Driver Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Evan Champion"; On 07-Oct-97 you wrote: > Where can I pick up the DPT RAID controller driver from? ftp://ftp.i-connect.net/crash --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-scsi Wed Oct 8 02:38:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA07126 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 02:38:27 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA07117 for ; Wed, 8 Oct 1997 02:38:24 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id MAA32565 for ; Wed, 8 Oct 1997 12:09:19 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id LAA25828 for ; Wed, 8 Oct 1997 11:50:52 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id LAA10464; Wed, 8 Oct 1997 11:37:25 +0200 (CEST) Message-ID: <19971008113725.46245@deepo.prosa.dk> Date: Wed, 8 Oct 1997 11:37:25 +0200 From: Philippe Regnauld To: freebsd-scsi@freebsd.org Subject: 2.2.2 anc NCR875 failures Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 X-Operating-System: FreeBSD 2.2.1-RELEASE i386 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just got (a week ago) a new machine to run a keyserver on... The configuration is TX97/K6-180, NCR-875, 64MB RAM, 2 x 2.2 Atlas II UW disks. I've had the following failure three times so far, I would guess during some fair amount of disk i/o: (written on paper, I'm trying to reread myself): ncr0: ERROR (81:0) 8af80 (10/1b) @24:00000000 script cms = 98000000 reg = da 10 c0 1b 47 10 01 07 75 08 81 af 80 00 07 00 ncr0: restart (fatal error) ncr0:1: error 81:0 8af80 sd1:(ncr0:1:0) COMMAND FAILED (9ff) @ f0cf7e00 sd0:(ncr0:0:0) COMMAND FAILED (9ff) @ f0cf7e00 sd0:(ncr0:0:0) COMMAND FAILED (9ff) @ f0cd1800 [...] ncr0: timeout ccb = f0cf7e00 ncr0: timeout ccb = f0cf7600 ... In the two other cases, I had some other message, every 30 sec. or so, like "retrying block = xxxyyy". No crash, no reboot... I had to go and manually reset the machine (off-site!) every time. I tried reducing TAG number in ncrcontrol -- nada. Help ? PS: I'm not subscribed to the list, but will if necessary :-) -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]- From owner-freebsd-scsi Wed Oct 8 14:13:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14836 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 14:13:43 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA14829 for ; Wed, 8 Oct 1997 14:13:33 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA04305 (5.67b/IDA-1.5 for ); Wed, 8 Oct 1997 23:13:12 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id WAA01232; Wed, 8 Oct 1997 22:55:53 +0200 (CEST) X-Face: " Date: Wed, 8 Oct 1997 22:55:52 +0200 From: Stefan Esser To: Philippe Regnauld Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 2.2.2 anc NCR875 failures References: <19971008113725.46245@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971008113725.46245@deepo.prosa.dk>; from Philippe Regnauld on Wed, Oct 08, 1997 at 11:37:25AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-08 11:37 +0200, Philippe Regnauld wrote: > I just got (a week ago) a new machine to run a keyserver on... > The configuration is > > TX97/K6-180, NCR-875, 64MB RAM, 2 x 2.2 Atlas II UW disks. > > I've had the following failure three times so far, I would > guess during some fair amount of disk i/o: (written on paper, > I'm trying to reread myself): > > > ncr0: ERROR (81:0) 8af80 (10/1b) @24:00000000 The NCR is failing on one the first instructions, and the error code indicates that an illegal instruction has been fetched. This was most probably caused by a jump to the immediate operand of an instruction: /*--------------------------< START >-----------------------*/ { /* ** Claim to be still alive ... */ SCR_COPY (sizeof (((struct ncb *)0)->heartbeat)), KVAR (KVAR_TIME_TV_SEC), NADDR (heartbeat), /* ** Make data structure address invalid. ** clear SIGP. */ SCR_LOAD_REG (dsa, 0xff), 0, SCR_FROM_REG (ctest2), ===>>> 0, The NCR processor tried to execute that constant 0, and it was not recognized as a valid instruction ... Hmmm, the (10/1b) in the error message indicate, that synchronous transfers have been negotiated (the offset is set to 0x10 == 16 bytes), but the clock pre-scaler (0x1b) is not set correctly for the 53c875, it appears! But I don't understand, how you can possibly complete a single SCSI transfer, at twice the correct clock rate. You did not tell, which version of the NCR driver (and FreeBSD) that is. The pre-scaler may be correct, if you are running the NCR driver as of FreeBSD-2.2.2 and if the 53c875 is revision 2 or newer. > In the two other cases, I had some other message, every > 30 sec. or so, like "retrying block = xxxyyy". No crash, > no reboot... Hmmm, there is no such message anywhere in the NCR driver. > I had to go and manually reset the machine (off-site!) every > time. Sorry to hear that ... > I tried reducing TAG number in ncrcontrol -- nada. No, your problem is different from the QUEUE FULL situation others are suffering from. But that may still hurt you, if you got revision LXY4 firmware in your Atlas II drives ... > Help ? Please let me know, what version of FreeBSD and the NCR driver you are using. Booting with "-v -v" will enable extra verbose boot message, and there will be more information on the NCR initalization. I'd like to know those messages. I'm very sorry for the inconvenience. I'll try to help you get this problem solved as quickly as possible, but it does look like a hardware problem to me, currently. But it may also be because of the timing loop used to measure the NCR 875 clock frequency, which may fail on your particular hardware, for as of now unknown reasons. Regards, STefan From owner-freebsd-scsi Wed Oct 8 17:16:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24966 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 17:16:37 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24956 for ; Wed, 8 Oct 1997 17:16:25 -0700 (PDT) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id UAA02602 for scsi@freebsd.org; Wed, 8 Oct 1997 20:16:17 -0400 (EDT) From: Keith Mitchell Message-Id: <199710090016.UAA02602@weenix.guru.org> Subject: Micropolis 4221WT Drive To: scsi@freebsd.org Date: Wed, 8 Oct 1997 20:16:17 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I had to replace a Micropolis 4221 recently (the thing had a head crash) and I have been experiencing lockups (no error messages, just hard lockups -- the SCSI light is light solid when this happens) ever since. The first replacement I received was another 4221 with a slightly newer firmware. The second replacement I recieved was a 4221WT which is supposed to be a low capacity version of the 4345. I get the same behavior from both of the replacements -- hard lockups. All of this is running off an Adaptec 3940UW. On the first channel, there is a Micropolis 4345W, and on the second channel there is the replacement drive. (I have other drives too, but I took them off while performing the tests). I was able to disklabel/newfs the new drive, but within thirty seconds of trying to copy over data from the 4345, the lockup happens. All of the jumper settings as well as the Settings in SCSI-Select are identical between the two drives (the drives even look identical except for the model number). They even have the same revision of the firmware. If I take out the 4221WT even thing works fine though. I even tried putting both drives on the same SCSI chain (that didn't work either). I have also tried using the Automatic and the manual terminations settings for the controller. I have also tried using the builtin terminators on the drive as well as a self-terminating cable I got from Adaptec. The only diffence that I know about is the 4345 is a Ultra-Wide drive and the 4221WT is simply a wide drive. I have termiantion power set to let the host provide power (as I recall Adaptec boards require this) on both drives. Anyone seen something similar or have any clues?? Thanks. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved Unauthorized use or duplication prohibited From owner-freebsd-scsi Wed Oct 8 18:07:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA27557 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 18:07:41 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA27552 for ; Wed, 8 Oct 1997 18:07:35 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id UAA15778; Wed, 8 Oct 1997 20:07:34 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id UAA00702; Wed, 8 Oct 1997 20:07:33 -0500 (CDT) Message-ID: <19971008200733.26786@Mars.Mcs.Net> Date: Wed, 8 Oct 1997 20:07:33 -0500 From: Karl Denninger To: Keith Mitchell Cc: scsi@FreeBSD.ORG Subject: Re: Micropolis 4221WT Drive References: <199710090016.UAA02602@weenix.guru.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <199710090016.UAA02602@weenix.guru.org>; from Keith Mitchell on Wed, Oct 08, 1997 at 08:16:17PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 08, 1997 at 08:16:17PM -0400, Keith Mitchell wrote: > Hi, > > I had to replace a Micropolis 4221 recently (the thing had a head crash) and > I have been experiencing lockups (no error messages, just hard lockups -- the > SCSI light is light solid when this happens) ever since. Those drives SUCK. Faster controllers (like the recent Adaptecs) blow them out of the water. I ditched all my Micropolis disks almost a year ago over this very issue. I believe some of them were even 4221s. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-scsi Wed Oct 8 18:38:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29250 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 18:38:32 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA29241 for ; Wed, 8 Oct 1997 18:38:28 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xJ7XM-0007FV-00; Wed, 8 Oct 1997 18:37:12 -0700 Date: Wed, 8 Oct 1997 18:37:10 -0700 (PDT) From: Tom To: Keith Mitchell cc: scsi@freebsd.org Subject: Re: Micropolis 4221WT Drive In-Reply-To: <199710090016.UAA02602@weenix.guru.org> 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 On Wed, 8 Oct 1997, Keith Mitchell wrote: > Anyone seen something similar or have any clues?? Version of FreeBSD? Microcropolis drive suck. Newer versions of ahc driver have become more adept at kicking starting crappy drives when they hang, but it can't work miracles. > Thanks. > > -- > Keith Mitchell Head Administrator: acm.vt.edu > Email: kmitch@weenix.guru.org PGP key available upon request > http://weenix.guru.org/~kmitch > Address and URL (c) 1997 Keith Mitchell - All Rights Reserved > Unauthorized use or duplication prohibited > > Tom From owner-freebsd-scsi Thu Oct 9 13:55:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA29097 for freebsd-scsi-outgoing; Thu, 9 Oct 1997 13:55:56 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA29087 for ; Thu, 9 Oct 1997 13:55:52 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA21326 (5.67b/IDA-1.5 for ); Thu, 9 Oct 1997 22:55:50 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id WAA00946; Thu, 9 Oct 1997 22:55:34 +0200 (CEST) X-Face: " Date: Thu, 9 Oct 1997 22:55:33 +0200 From: Stefan Esser To: Philippe Regnauld Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 2.2.2 anc NCR875 failures References: <19971008113725.46245@deepo.prosa.dk> <19971008225552.49139@mi.uni-koeln.de> <19971009182853.57538@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971009182853.57538@deepo.prosa.dk>; from Philippe Regnauld on Thu, Oct 09, 1997 at 06:28:53PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-09 18:28 +0200, Philippe Regnauld wrote: > Stefan Esser writes: > > > > No, your problem is different from the QUEUE FULL > > situation others are suffering from. But that may > > still hurt you, if you got revision LXY4 firmware > > in your Atlas II drives ... > > Oh great! Here's the info: > > The NCR chip says: > > 609-0392 410 > dp03283 > 9717r > > The FLASH rom says: > > Rev 2.00 FLASH 390F/U > > (this is a "Tekram 390" with ncr 53c875) Yes, that's the latest Tekram DC390F with Flash ROM ... > Output from dmesg with -v -v: (as you will see, I _have_ LXY4 > on both disks :-[ They may cause problems with tags at times. I do not know whether there is newer firmware, but it generally available from Quantums FTP site: ftp://ftp.qntm.com/pub/support/Firmware > FreeBSD 2.2.2-RELEASE #2: Thu Oct 9 18:21:09 CEST 1997 Well, you reminded me of the subject in a previous message, and I've got to admit that I just did not bother to read the full text of the subject line ... > CPU: AMD K6 (187.11-MHz 586-class CPU) What's the PCI bus clock ??? Anything beyond 33MHz may cause problems with some PCI chips. (The NCR controllers are known to work at 37.5MHz, but many other devices may cause spurious errors!) If you currently are running with 5 x 37.5, then you may want to try 6 x 30 instead. Even though your system will be some 10% slower, you may find that it becomes stable again ... > chip0 rev 1 on pci0:0 > chip1 rev 1 on pci0:1:0 > pci0:1:1: Intel Corporation, device=0x7111, class=storage (ide) [no driver assigned] > map(20): io(e000) > pci0:1:2: Intel Corporation, device=0x7112, class=0x0c, subclass=0x03 int d irq 9 [no driver assigned] > map(20): io(d800) > chip2 rev 1 on pci0:1:3 Hmmm, have to make sure they will be correctly identified in 2.2.5 ... > vga0 rev 0 int a irq 12 on pci0:10 What brand of VGA card is that ? > ncr0 rev 3 int a irq 11 on pci0:12 > initial value of SCNTL3 = 03, final = 13 Ok. The register is set to a save value. This is the NCR driver before the Fast-20 patches went in. It uses the 875 with a 40MHz clock, just like a non-Ultra SCSI chip, and the value that surprised in me in your original problem report is in fact quite right for that driver revision. > (ncr0:0:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2 > sd0(ncr0:0:0): 20.0 MB/s (100 ns, offset 16) > (ncr0:1:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2 > sd1(ncr0:1:0): 20.0 MB/s (100 ns, offset 16) Ok. My advice: Make sure you are not running with a bus clock beyond that specified in the PCI spec. And with 37.5MHz, you are some 15% higher than allowed! I'm sure your system will become reliable, then. Regards, STefan From owner-freebsd-scsi Thu Oct 9 23:25:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27251 for freebsd-scsi-outgoing; Thu, 9 Oct 1997 23:25:58 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27203; Thu, 9 Oct 1997 23:25:25 -0700 (PDT) (envelope-from tarkhil@mgt.msk.ru) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id KAA10363; Fri, 10 Oct 1997 10:24:55 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.7/8.8.6) with ESMTP id KAA06724; Fri, 10 Oct 1997 10:24:20 +0400 (MSD) Message-Id: <199710100624.KAA06724@asteroid.mgt.msk.ru> To: hardware@freebsd.org cc: stable@freebsd.org, scsi@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: Trouble with dump on ncr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Oct 1997 10:24:19 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm trying to make dump, and constantly unable to do it. It looks like: DUMP: Date of this level 0 dump: Fri Oct 10 10:21:06 1997 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0s1e (/var) to /var/async/tmp/test DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 14328 tape blocks on 0.37 tape(s). DUMP: dumping (Pass III) [directories] DUMP: slave couldn't reopen disk: Device not configured DUMP: The ENTIRE dump is aborted. asteroid#/usr/FreeBSD-CVS/src 138_> Oct 10 10:21:06 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f063ec00 ... and so on. What should I do to fix it? Here is uname -a output: FreeBSD asteroid.mgt.msk.ru 2.2-STABLE FreeBSD 2.2-STABLE #0: Thu Oct 9 13:17:25 MSD 1997 root@asteroid.mgt.msk.ru:/net/unix/FreeBSD/src/sys/compile/ASTEROID i386 and part of dmesg: CPU: Pentium (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31010816 (30284K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ncr0 rev 2 int a irq 11 on pci0:8 ncr0 waiting for scsi devices to settle (ncr0:0:0): 5.0 MB/s (200 ns, offset 8) (ncr0:0:0): "IBM DALS-3540 S60E" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) 516MB (1056768 512 byte sectors) (ncr0:1:0): 5.0 MB/s (200 ns, offset 8) (ncr0:1:0): "WDIGTL ENTERPRISE 1.61" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) 2077MB (4254819 512 byte sectors) Alex. From owner-freebsd-scsi Fri Oct 10 12:41:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03087 for freebsd-scsi-outgoing; Fri, 10 Oct 1997 12:41:02 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA03075 for ; Fri, 10 Oct 1997 12:40:58 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA02254; Fri, 10 Oct 1997 21:40:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id VAA24287; Fri, 10 Oct 1997 21:23:37 +0200 (MET DST) Message-ID: <19971010212337.WB21205@uriah.heep.sax.de> Date: Fri, 10 Oct 1997 21:23:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: tarkhil@mgt.msk.ru Subject: Re: Trouble with dump on ncr References: <199710100624.KAA06724@asteroid.mgt.msk.ru> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710100624.KAA06724@asteroid.mgt.msk.ru>; from Alexander B. Povolotsky on Oct 10, 1997 10:24:19 +0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Alexander B. Povolotsky wrote: > I'm trying to make dump, and constantly unable to do it. > asteroid#/usr/FreeBSD-CVS/src 138_> Oct 10 10:21:06 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > Oct 10 10:21:07 asteroid /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 > Oct 10 10:21:07 asteroid /kernel: sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0461000. > (ncr0:0:0): "IBM DALS-3540 S60E" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) > 516MB (1056768 512 byte sectors) Re-read the freebsd-scsi archives... and then either disable tagged command queuing (``options FAILSAFE''), or alternatively remove all calls to scsi_start_unit() in /sys/scsi/sd.c. Btw., i think we are safe to make the latter change anyway. As i've already mentioned in a private mail to Justin, i've recently proven that the calls to scsi_start_unit() are completely useless and don't work. (I had taken down a disk manually, and later tried to implicitly start it by opening it again.) Thus, by removing these calls, we won't break anything that's not already broken. Anybody objecting? -- 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 Oct 11 01:59:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA09338 for freebsd-scsi-outgoing; Sat, 11 Oct 1997 01:59:26 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA09329 for ; Sat, 11 Oct 1997 01:59:22 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA13749 (5.67b/IDA-1.5 for ); Sat, 11 Oct 1997 10:59:19 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id JAA00335; Sat, 11 Oct 1997 09:16:06 +0200 (CEST) X-Face: " Date: Sat, 11 Oct 1997 09:16:05 +0200 From: Stefan Esser To: Joerg Wunsch Cc: scsi@FreeBSD.ORG Subject: Re: Trouble with dump on ncr References: <199710100624.KAA06724@asteroid.mgt.msk.ru> <19971010212337.WB21205@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971010212337.WB21205@uriah.heep.sax.de>; from J Wunsch on Fri, Oct 10, 1997 at 09:23:37PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-10 21:23 +0200, J Wunsch wrote: > Re-read the freebsd-scsi archives... and then either disable tagged > command queuing (``options FAILSAFE''), or alternatively remove all > calls to scsi_start_unit() in /sys/scsi/sd.c. > > Btw., i think we are safe to make the latter change anyway. As i've > already mentioned in a private mail to Justin, i've recently proven > that the calls to scsi_start_unit() are completely useless and don't > work. (I had taken down a disk manually, and later tried to > implicitly start it by opening it again.) Thus, by removing these > calls, we won't break anything that's not already broken. > > Anybody objecting? I'm all for the removal of the scsi_start_unit() calls. The start unit command should instead be issued from the recovery code in the generic SCSI layer, IMHO, whenever the return status from the SCSI card driver indicates a drive has (been) stopped in an attempt to recover from that situation. Regards, STefan From owner-freebsd-scsi Sat Oct 11 12:34:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03554 for freebsd-scsi-outgoing; Sat, 11 Oct 1997 12:34:26 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03548 for ; Sat, 11 Oct 1997 12:34:21 -0700 (PDT) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.8.7/8.8.7) id PAA19728 for scsi@freebsd.org; Sat, 11 Oct 1997 15:34:17 -0400 (EDT) From: Keith Mitchell Message-Id: <199710111934.PAA19728@weenix.guru.org> Subject: Re: Micropolis 4221WT Drive In-Reply-To: From kmitch at "Oct 8, 97 08:16:17 pm" To: scsi@freebsd.org Date: Sat, 11 Oct 1997 15:34:17 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have a little more information on the problem. Well, it doesn't appear to be a clear-cut problem with the drive. I took out the 3940UW and merged the two SCSI chains onto one and put them on a 2940UW. Then everything worked fine. I then yanked out the 2940 and put the 3940 back in (but all on one channel) and everything works fine there too. One thing I did notice. When I booted verbose with the devices split, Channel A didn't detect Autoterm correctly. It thought there were no devices connected: ahc0: type 0 fixed SCSI 2 sd0: Direct-Access 4340MB (8890029 512 byte sectors) sd0: with 4811 cyls, 11 heads, and an avera When I put everything on Channel A, it detected termination correctly and seemed to be working fine. I should mention that forcing the termiantion setting made no difference as far as the system working. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved Unauthorized use or duplication prohibited From owner-freebsd-scsi Sat Oct 11 23:17:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01291 for freebsd-scsi-outgoing; Sat, 11 Oct 1997 23:17:11 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from pluto.plutotech.com (ken@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01206; Sat, 11 Oct 1997 23:15:57 -0700 (PDT) (envelope-from ken@plutotech.com) Received: (from ken@localhost) by pluto.plutotech.com (8.8.5/8.8.5) id AAA18578; Sun, 12 Oct 1997 00:15:56 -0600 (MDT) From: Kenneth Merry Message-Id: <199710120615.AAA18578@pluto.plutotech.com> Subject: Re: Trouble with dump on ncr In-Reply-To: <19971011091605.32335@mi.uni-koeln.de> from Stefan Esser at "Oct 11, 97 09:16:05 am" To: se@FreeBSD.ORG (Stefan Esser) Date: Sun, 12 Oct 1997 00:15:56 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser wrote... > On 1997-10-10 21:23 +0200, J Wunsch wrote: > > Re-read the freebsd-scsi archives... and then either disable tagged > > command queuing (``options FAILSAFE''), or alternatively remove all > > calls to scsi_start_unit() in /sys/scsi/sd.c. > > > > Btw., i think we are safe to make the latter change anyway. As i've > > already mentioned in a private mail to Justin, i've recently proven > > that the calls to scsi_start_unit() are completely useless and don't > > work. (I had taken down a disk manually, and later tried to > > implicitly start it by opening it again.) Thus, by removing these > > calls, we won't break anything that's not already broken. > > > > Anybody objecting? > > I'm all for the removal of the scsi_start_unit() calls. > > The start unit command should instead be issued from the > recovery code in the generic SCSI layer, IMHO, whenever > the return status from the SCSI card driver indicates a > drive has (been) stopped in an attempt to recover from > that situation. FWIW, that's what the new CAM SCSI code does. The da (i.e. sd) driver does a read capacity upon open. If the read capacity returns with 0x04, 0x02 ("Logical unit not ready, initializing cmd. required"), the error recovery code issues a start unit command to the drive. One interesting thing about that, though.. Apparantly not all drives return 0x04,0x02 when they aren't spun up. I ran into some Quantum Fireball ST (Stratus) drives that return 0x04,0x0b when they aren't spun up. Strange, 'eh? That sense code qualifier isn't in the SCSI specs (not even SCSI-3), and it isn't in Quantum's documentation on the drive. Ken -- Kenneth Merry ken@plutotech.com