Date: Wed, 28 Aug 1996 09:50:18 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: michaelh@cet.co.jp (Michael Hancock) Cc: terry@lambert.org, eric@ms.uky.edu, freebsd-fs@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: vclean (was The VIVA file system) Message-ID: <199608281650.JAA26928@phaeton.artisoft.com> In-Reply-To: <Pine.SV4.3.93.960828201655.66A-100000@parkplace.cet.co.jp> from "Michael Hancock" at Aug 28, 96 08:21:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > This was the point I was missing. What is disassociating the inode and > > when is it happening? > > Yikes! I took a look below, but I didn't expect to see vgone() calls in > ufs_inactive(). > > if (vp->v_usecount == 0 && ip->i_mode == 0) > vgone(vp); > > I need to figure out what ip->i_mode == 0 means. The file type is a non-zero value in the high bits of the mode word; it means that the inode does not refer to real data any more. The vgone call is just part of the subsystem I think should be replaced wholesale; I'd like to see a per FS vrele() (back to locally managed pools) replace most of those calls. The vgone() calls vgone1() calls vclean, and we're back in my hate-zone. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608281650.JAA26928>