From owner-freebsd-current  Wed Mar 20 05:29:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA02268
          for current-outgoing; Wed, 20 Mar 1996 05:29:28 -0800 (PST)
Received: from neon.Glock.COM (root@neon.glock.com [198.82.228.159])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA02263
          for <current@freebsd.org>; Wed, 20 Mar 1996 05:29:26 -0800 (PST)
Received: (from mmead@localhost) by neon.Glock.COM (8.7.4/8.7.3) id IAA00770; Wed, 20 Mar 1996 08:29:25 -0500 (EST)
From: "matthew c. mead" <mmead@Glock.COM>
Message-Id: <199603201329.IAA00770@neon.Glock.COM>
Subject: Re: cvs-all-digest V1 #300
To: current@freebsd.org
Date: Wed, 20 Mar 1996 08:29:25 -0500 (EST)
In-Reply-To: <199603191927.LAA23880@freefall.freebsd.org> from "owner-cvs-all-digest@freefall.freebsd.org" at Mar 19, 96 11:27:18 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

owner-cvs-all-digest@freefall.freebsd.org writes:

> From: John Dyson <dyson>
> Date: Mon, 18 Mar 1996 21:13:24 -0800 (PST)
> Subject: cvs commit:  src/sys/miscfs/specfs spec_vnops.c src/sys/vm vnode_pager.c
> 
> dyson       96/03/18 21:13:24
> 
>   Modified:    sys/miscfs/specfs  spec_vnops.c
>                sys/vm    vnode_pager.c
>   Log:
>   Fix the problem that unmounting filesystems that are backed by a VMIO
>   device have reference count problems.  We mark the underlying object
>   ono-persistent, and account for the reference count that the VM system
>   maintainsfor the special device close.  This should fix the removable
>   device problem.
>   
>   Revision  Changes    Path
>   1.29      +3 -2      src/sys/miscfs/specfs/spec_vnops.c
>   1.59      +5 -2      src/sys/vm/vnode_pager.c
> 
> ------------------------------

	I've thoroughly tested this code change, and from what I
can tell, it fixes all the problems I've found using a JAZ drive,
save one.  The one that it doesn't fix is if you mount a UFS
filesystem on the JAZ drive and allow it to sleep, then before
waking it up via a standard filesystem call you fsck the raw
device (ok, ok, so I did this by accident the first time... :-),
then try to use the mounted ufs, you cannot unmount it or use it
until you reboot.  The solution to that problem is to not try to
fsck it while it's mounted.  Other than that, the unsleep code
and the unmount/unlocking for ejection code works great.


-matt

--
Matthew C. Mead

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