From owner-freebsd-hackers Mon Apr 28 20:09:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19238 for hackers-outgoing; Mon, 28 Apr 1997 20:09:43 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA19230 for ; Mon, 28 Apr 1997 20:09:41 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wM3I8-0000ws-00; Mon, 28 Apr 1997 21:09:20 -0600 To: Simon Shapiro Subject: Re: A Desparate Plea for Help... Cc: Peter Dufault , freebsd-hackers@freebsd.org In-reply-to: Your message of "Mon, 28 Apr 1997 10:25:49 PDT." References: Date: Mon, 28 Apr 1997 21:09:19 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Simon Shapiro writes: : : Hi Peter Dufault; On 28-Apr-97 you wrote: : > (To keep the jazz from spinning down send it a TEST UNIT READY : > every so often). : : To keep this motor here from boiling over, use this here coathanger to tie : this belt together :-))) I know this trick... I was expecting Iomega, for : an initial order of 200 units to at least answer the question, or supply a : spec. It is a dog-slow device anyway. You might wanna try the patch that I've been using here for a while. It seems to work and fixed my dumps trash the /jaz mount point problem that you may have seen in the list archives. This is against a few days old kernel, so it should apply fairly cleanly. Thanks to Joerge who pointed me at the od.c code that already did this sort of thing. Warner P.S. What do others thing of the change? Index: sd.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/scsi/sd.c,v retrieving revision 1.104 diff -u -r1.104 sd.c --- sd.c 1997/03/24 11:25:02 1.104 +++ sd.c 1997/03/28 15:42:39 @@ -271,6 +271,12 @@ dev, unit, PARTITION(dev))); /* + * In case it is a funny one, tell it to start + * not needed for most hard drives (ignore failure) + */ + scsi_start_unit(sc_link, SCSI_ERR_OK | SCSI_SILENT); + + /* * "unit attention" errors should occur here if the * drive has been restarted or the pack changed. * just ingnore the result, it's a decoy instruction @@ -294,11 +300,6 @@ dsgone(&sd->dk_slices); } - /* - * In case it is a funny one, tell it to start - * not needed for most hard drives (ignore failure) - */ - scsi_start_unit(sc_link, SCSI_ERR_OK | SCSI_SILENT); /* * Check that it is still responding and ok.