From owner-freebsd-current@FreeBSD.ORG  Wed Nov  3 07:55:10 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6E3E516A4CE
	for <freebsd-current@freebsd.org>;
	Wed,  3 Nov 2004 07:55:10 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB1EC43D2F
	for <freebsd-current@freebsd.org>;
	Wed,  3 Nov 2004 07:55:09 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iA37sxA3012707;
	Wed, 3 Nov 2004 08:55:04 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: David Gilbert <dgilbert@dclg.ca>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 03 Nov 2004 01:26:59 EST."
             <41887A33.2060608@dclg.ca> 
Date: Wed, 03 Nov 2004 08:54:59 +0100
Message-ID: <12706.1099468499@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: freebsd-current@freebsd.org
Subject: Re: More running-with-scissors and fsck. 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2004 07:55:10 -0000

In message <41887A33.2060608@dclg.ca>, David Gilbert writes:

>Well... the recoverdisk is a cool tool.  I can see it coming in handy 
>many times.  While there isn't much documentation, I've tended to use it 
>by creating a vnode md disk of exactly the right size to recover the 
>partition in question.

You could just have used a regular file for it and connected it to a
md later on.

>However, it's all right around something key.  When I run fsck on the 
>recovered image, fsck continuously complains that it can't create 
>lost+found.

Try running dump on it instead, dump will pull as much out of the
wreckage as possible.

If that doesn't work, you'll need to learn about the internals of
the UFS/FFS filesystem (read Kirks book) and grab fscb and get
to work.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.