From owner-freebsd-hackers  Tue Jan 21 13:51:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id NAA16419
          for hackers-outgoing; Tue, 21 Jan 1997 13:51:39 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA16412
          for <hackers@freebsd.org>; Tue, 21 Jan 1997 13:51:37 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vmo6R-0000Fx-00; Tue, 21 Jan 1997 14:51:35 -0700
To: hackers@freebsd.org
Subject: Spin down problem back?
Date: Tue, 21 Jan 1997 14:51:34 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vmo6R-0000Fx-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm running a -current kernel from Nov 24.  I have just been able to
recreate a spindown problem with my Jaz drive.

The easy way to see this happen is to say something like:
	dump Bfu1 15000000 /dev/nrst0 /dev/rsd1c
(where sd1 is my jaz drive).  You get the following warning on the
console, and then my mountpoint dies, and no further access to the
drive is possible.  If I do an ls -l /jaz before I do the above mount
command (that's where it is mounted), it works fine.

After the above command fails, the mount point is dead:

ls: /jaz: Input/output error

and I have to reboot.  I'm going to try the latest kernel, but was
wondering if anybody else has seen this.

BTW, I get the following on my console (as reported by
/var/log/messages):
sd1(uha0:3:0): NOT READY asc:4,0
sd1(uha0:3:0):  Logical unit not ready, cause not reportable

Warner