From owner-freebsd-current  Tue Apr 18 11:25:13 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA14034
          for current-outgoing; Tue, 18 Apr 1995 11:25:13 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA14023
          for <freebsd-current@freebsd.org>; Tue, 18 Apr 1995 11:25:10 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA26856; Tue, 18 Apr 1995 11:24:56 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA01700; Tue, 18 Apr 1995 11:24:56 -0700
Message-Id: <199504181824.LAA01700@corbin.Root.COM>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: fenner@parc.xerox.com (Bill Fenner), freebsd-current@FreeBSD.org
Subject: Re: fsck trashes / if no /lost+found? 
In-reply-to: Your message of "Tue, 18 Apr 95 20:06:19 +0200."
             <199504181806.UAA04362@uriah.heep.sax.de> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Tue, 18 Apr 1995 11:24:44 -0700
Sender: current-owner@FreeBSD.org
Precedence: bulk

>As Bill Fenner wrote:
>> 
>> I am running SNAP-950322.  I crashed hard, and on the way up, fsck tried to
>> reconnect a file when fsck'ing /usr.  Apparently, for some reason there was
>> no /usr/lost+found, and fsck printed an error something like "no room in /"
>> when it said it was trying to create it.  The fsck failed, and when I fsck'd
>> manually it said there was no /, and it ended up reconnecting all the
>> directories in /lost+found (after creating /lost+found).
>
>Terry tells about this every second day. :-)
>
>Time to add the appropriate part to newfs(8)?

   I asked Kirk about this and he said "no". I might still have the email
around somewhere.

-DG