From owner-freebsd-current Tue May 14 10:24:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA25552 for current-outgoing; Tue, 14 May 1996 10:24:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA25512 for ; Tue, 14 May 1996 10:23:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA12577; Tue, 14 May 1996 10:20:46 -0700 From: Terry Lambert Message-Id: <199605141720.KAA12577@phaeton.artisoft.com> Subject: Re: JAZ drive mounted async To: mmead@Glock.COM (matthew c. mead) Date: Tue, 14 May 1996 10:20:46 -0700 (MST) Cc: current@freebsd.org In-Reply-To: <199605141457.KAA08355@Glock.COM> from "matthew c. mead" at May 14, 96 10:57:00 am X-Mailer: ELM [version 2.4 PL24] 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 > 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? If you are running debug, there is a sysctl flag for write reordering which occurs whether or not the thing is mounted async. If you aren't running debug, you should grep -i for sysctl in the sys/ufs/ufs/ufs*.c sources and change the manifest constant to disable this behaviour. I *think* this will fix it (temporarily, at least). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.