From owner-freebsd-current  Tue Aug 27 16:37:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA09479
          for current-outgoing; Tue, 27 Aug 1996 16:37:34 -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 QAA09470;
          Tue, 27 Aug 1996 16:37:30 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id XAA25859; Tue, 27 Aug 1996 23:37:13 GMT
Date: Wed, 28 Aug 1996 08:37:13 +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: <199608271545.IAA24710@phaeton.artisoft.com>
Message-ID: <Pine.SV4.3.93.960828083423.25812B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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?

Regards,


Mike