From owner-freebsd-questions Tue Nov 21 10:05:14 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA10601 for questions-outgoing; Tue, 21 Nov 1995 10:05:14 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA10591 for ; Tue, 21 Nov 1995 10:05:04 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04276; Tue, 21 Nov 1995 11:02:53 -0700 From: Terry Lambert Message-Id: <199511211802.LAA04276@phaeton.artisoft.com> Subject: Re: lost+found? To: archie@tribe.com (Archie Cobbs) Date: Tue, 21 Nov 1995 11:02:53 -0700 (MST) Cc: freebsd-questions@FreeBSD.org In-Reply-To: <199511210049.QAA00362@bubba.tribe.com> from "Archie Cobbs" at Nov 20, 95 04:49:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 790 Sender: owner-questions@FreeBSD.org Precedence: bulk > 2. What ever happened to "lost+found"? Do I need to do anything > special to create it (special inode number, etc)? How come it's > not created by the normal install process? Or is there another > directory somewhere serving the same purpose? The "lost+found" directory is created as necessary by fsck on the (potentially bogus) assumption that there will be room for it. The fsck code is cruddy in this regard, and you may need several fscks to restore the FS to sanity. This is a pretty trivial but annoying bug. There is code there to support creating the lost+found statically. See the newfs/fsck utility sources. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.