From owner-freebsd-current  Sun Oct 19 12:38:30 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA27998
          for current-outgoing; Sun, 19 Oct 1997 12:38:30 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA27993
          for <current@FreeBSD.ORG>; Sun, 19 Oct 1997 12:38:26 -0700 (PDT)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA00533;
	Sun, 19 Oct 1997 21:36:43 +0200 (CEST)
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: FreeBSD-Current <current@FreeBSD.ORG>
Subject: Re: nullfs & current 
In-reply-to: Your message of "Sun, 19 Oct 1997 15:33:25 +0200."
             <19971019153325.26490@keltia.freenix.fr> 
Date: Sun, 19 Oct 1997 21:36:43 +0200
Message-ID: <531.877289803@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <19971019153325.26490@keltia.freenix.fr>, Ollivier Robert writes:
>
>I'm trying to read the source but I'm not very experienced with vnodes/VFS
>and such. After studying the code, we have
>
>unlink
>  VOP_REMOVE
>    null_bypass
>      ufs_remove
>
>ufs_remove does remove the file from the directory but the refcount is
>still probably at one somewhere so the blocks are not reclaimed till umount 
>time. I don't know where to look at now. I'll have to read more about the
>whole VFS/vnode business. It is too bad I don't have a second machine to
>use remote gdb...

And then when the vnode comes down VOP_INACTIVE and VOP_RECLAIM will 
trigger the actual removal.  (Somebody might have the file open, remember ?)

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."