Date: Sun, 19 Oct 1997 21:36:43 +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: <531.877289803@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 19 Oct 1997 15:33:25 %2B0200." <19971019153325.26490@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531.877289803>