From owner-freebsd-current  Fri Mar 22 17:56:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA19864
          for current-outgoing; Fri, 22 Mar 1996 17:56:16 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19857
          for <freebsd-current@freefall.freebsd.org>; Fri, 22 Mar 1996 17:56:13 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA02055; Sat, 23 Mar 1996 12:50:33 +1100
Date: Sat, 23 Mar 1996 12:50:33 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603230150.MAA02055@godzilla.zeta.org.au>
To: mrm@sceard.com, terry@lambert.org
Subject: Re: lost+found ???
Cc: freebsd-current@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>On the subject of the 8k, Bruce is wrong about the requirements: the
>most you have to deal with is the number of files allowed to be a
>problem with properly ordered updates: basically, one directory
>worth of names... and in that case, you'll get blocks back from
>the directory that died.  It's still possible to overflow the 16
>additional (reserved) blocks, but it's unlikely.

>Of course if you mount async, all bets are off. 8-(.

I.e., lost+found only works when it is least needed :-).

I think you can lose more than one directory if an inode block for a
directory becomes unreadable.

I wonder if fsck handles huge directories better than ufs.

Bruce