From owner-freebsd-current Mon Oct 20 01:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA08361 for current-outgoing; Mon, 20 Oct 1997 01:26:27 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from schizo.dk.tfs.com (mail.trw.dk [195.8.133.123]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08344 for ; Mon, 20 Oct 1997 01:26:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.7/8.7.3) with ESMTP id KAA08695; Mon, 20 Oct 1997 10:25:50 +0200 (MET DST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id JAA00222; Mon, 20 Oct 1997 09:38:59 +0200 (CEST) To: Ollivier Robert cc: FreeBSD-Current Subject: Re: nullfs & current In-reply-to: Your message of "Sun, 19 Oct 1997 22:14:25 +0200." <19971019221425.28468@keltia.freenix.fr> Date: Mon, 20 Oct 1997 09:38:58 +0200 Message-ID: <220.877333138@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19971019221425.28468@keltia.freenix.fr>, Ollivier Robert writes: >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 :-( You have to try to track all instances of "WILLRELE" across the nullfs bypass routine to catch this one. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."