From owner-freebsd-current  Tue May 14 10:25:25 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA25691
          for current-outgoing; Tue, 14 May 1996 10:25:25 -0700 (PDT)
Received: from Glock.COM (root@glock.com [198.82.228.165])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA25686;
          Tue, 14 May 1996 10:25:23 -0700 (PDT)
Received: (from mmead@localhost) by Glock.COM (8.7.3/8.7.3) id NAA09242; Tue, 14 May 1996 13:25:21 -0400 (EDT)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199605141725.NAA09242@Glock.COM>
Subject: Re: JAZ drive mounted async
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Tue, 14 May 1996 13:25:21 -0400 (EDT)
Cc: current@freebsd.org
In-Reply-To: <199605141712.KAA24831@freefall.freebsd.org> from "Justin T. Gibbs" at May 14, 96 10:12:36 am
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-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Justin T. Gibbs writes:

> >    3 words - Don't Do It.  :-)  Anyway, it seems that the system
> >gets into deadlock when you mount a JAZ drive async and it spins
> >down after 30 minutes idle time.  The JAZ will never spin back
> >up...  Any ideas?

> So when you mount it sync, it does spin back up?  What prints to your
> console when it does spin up?

	Not a thing.  It just spins back up.  I'm assuming that
the scsi drivers are assuming that the drive is mounted sync and
tell it to spin up before writing data to it, but *not* before
writing inode data to it (since that would be done already in a
sync mount).


-matt

-- 
Matthew C. Mead

mmead@Glock.COM
http://www.Glock.COM/~mmead/