From owner-freebsd-fs  Wed Aug 28 09:57:56 1996
Return-Path: owner-fs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA13405
          for fs-outgoing; Wed, 28 Aug 1996 09:57:56 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA13383;
          Wed, 28 Aug 1996 09:57:47 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA26908; Wed, 28 Aug 1996 09:46:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199608281646.JAA26908@phaeton.artisoft.com>
Subject: Re: vclean (was The VIVA file system)
To: michaelh@cet.co.jp (Michael Hancock)
Date: Wed, 28 Aug 1996 09:46:22 -0700 (MST)
Cc: terry@lambert.org, eric@ms.uky.edu, freebsd-fs@FreeBSD.ORG,
        current@FreeBSD.ORG
In-Reply-To: <Pine.SV4.3.93.960828083423.25812B-100000@parkplace.cet.co.jp> from "Michael Hancock" at Aug 28, 96 08:37:13 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-fs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 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?

vfs_subr.c:
/*
 * Disassociate the underlying file system from a vnode.
 */
static void
vclean(struct vnode *vp, int flags, struct proc *p)


Any time vclean is called... 8-(.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.