From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 11 07:54:49 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E87416A4CE for ; Wed, 11 Aug 2004 07:54:49 +0000 (GMT) Received: from mail003.syd.optusnet.com.au (mail003.syd.optusnet.com.au [211.29.132.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEC6743D1F for ; Wed, 11 Aug 2004 07:54:47 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i7B7sbU09890; Wed, 11 Aug 2004 17:54:37 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i7B7saxP010451; Wed, 11 Aug 2004 17:54:36 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i7B7sasf010450; Wed, 11 Aug 2004 17:54:36 +1000 (EST) (envelope-from pjeremy) Date: Wed, 11 Aug 2004 17:54:35 +1000 From: Peter Jeremy To: Charles Sprickman , freebsd-hackers@freebsd.org Message-ID: <20040811075435.GA423@cirb503493.alcatel.com.au> References: <20040810234448.A709@toad.nat.fasttrackmonkey.com> <20040811061739.GD63484@pc5.i.0x5.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040811061739.GD63484@pc5.i.0x5.de> User-Agent: Mutt/1.4.2i Subject: Re: fsck and lost+found space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 07:54:49 -0000 On Wed, 2004-Aug-11 08:17:39 +0200, Nicolas Rachinsky wrote: >* Charles Sprickman [2004-08-10 23:52 -0400]: >> I was hoping for some option in fsck to allow an alternate lost+found >> directory on another device, but no such luck. This isn't possible - all fsck does is to create a directory entry pointing to the file. You could add an option to fsck to allow you to specify the directory name but you are still limited by fsck's inability to use indirect blocks for the fsck directory. >Can you stop fsck just before it begins to throw away files? Then you >could perhaps rename lost+found (perhaps with fsdb) and rerun fsck. I've done this. The problem is stopping fsck before it starts throwing away files. Once you stop fsck, you need to do a 'mount -f ...', rename lost+found to something else, unmount the filesystem and start lost+found again. -- Peter Jeremy