Date: Mon, 20 Oct 1997 09:38:58 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Ollivier Robert <roberto@keltia.freenix.fr> Cc: FreeBSD-Current <current@FreeBSD.ORG> Subject: Re: nullfs & current Message-ID: <220.877333138@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 19 Oct 1997 22:14:25 %2B0200." <19971019221425.28468@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?220.877333138>