From owner-freebsd-fs  Wed Aug 28 04:21:22 1996
Return-Path: owner-fs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA20285
          for fs-outgoing; Wed, 28 Aug 1996 04:21:22 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20263;
          Wed, 28 Aug 1996 04:21:17 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id LAA00080; Wed, 28 Aug 1996 11:21:08 GMT
Date: Wed, 28 Aug 1996 20:21:07 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Terry Lambert <terry@lambert.org>
cc: eric@ms.uky.edu, freebsd-fs@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: vclean (was The VIVA file system)
In-Reply-To: <Pine.SV4.3.93.960828083423.25812B-100000@parkplace.cet.co.jp>
Message-ID: <Pine.SV4.3.93.960828201655.66A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-fs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 28 Aug 1996, I wrote:

> On Tue, 27 Aug 1996, Terry Lambert wrote:
> 
> > Yes.  The number one problem is that the in-place freelist with valid
> > buffers hanging off of them is not recoverable once the inode data has
> > been disassociated.  The vnode is effectively unrecoverable without
> > the buffers being freed.
> > 
> 
> 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.

Regards,


Mike Hancock