Date: Mon, 20 Oct 1997 09:41:32 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: roberto@keltia.freenix.fr (Ollivier Robert), current@FreeBSD.ORG Subject: Re: nullfs & current Message-ID: <255.877333292@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 19 Oct 1997 16:21:15 CDT." <199710192121.QAA05089@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199710192121.QAA05089@dyson.iquest.net>, "John S. Dyson" writes: >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. Which in this case means VOP_RECLAIM, right ? -- 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?255.877333292>