From owner-freebsd-current  Sun Oct 19 14:25:20 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA02886
          for current-outgoing; Sun, 19 Oct 1997 14:25:20 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA02881
          for <current@FreeBSD.ORG>; Sun, 19 Oct 1997 14:25:15 -0700 (PDT)
          (envelope-from toor@dyson.iquest.net)
Received: (from root@localhost)
	by dyson.iquest.net (8.8.7/8.8.5) id QAA05089;
	Sun, 19 Oct 1997 16:21:15 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199710192121.QAA05089@dyson.iquest.net>
Subject: Re: nullfs & current
In-Reply-To: <19971019221425.28468@keltia.freenix.fr> from Ollivier Robert at "Oct 19, 97 10:14:25 pm"
To: roberto@keltia.freenix.fr (Ollivier Robert)
Date: Sun, 19 Oct 1997 16:21:15 -0500 (EST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Ollivier Robert said:
> According to Poul-Henning Kamp:
> > And then when the vnode comes down VOP_INACTIVE and VOP_RECLAIM will 
> > trigger the actual removal.  (Somebody might have the file open, remember ?)
> 
> That's how I understand it but in this case, the blocks are not reclaimed
> even though it is supposed to be the last close of the file. There is a
> refcount one higher than it should be. The nullfs is by itself very simple
> and I don't see where :-(
> 
The VM system holds a reference.  You have to do a vnode_pager_uncache when
deleting a file.


-- 
John
dyson@freebsd.org
jdyson@nc.com