On Wed, Jun 06, 2001 at 01:29:40PM -0400, Will Waites wrote:
> On Wed, Jun 06, 2001 at 12:25:02PM -0500, John Valdes wrote:
> > 
> > I just noticed that when I newfs a ffs, newfs doesn't create a
> > lost+found.
> 
> fsck will create a lost+found directory itself if it encounters
> anything that it should put in there.

In that case, isn't there a danger that fsck may overwrite recoverable
blocks when it creates lost+found?  On other OSes, lost+found is
created by newfs and allocated extra blocks (it's typically 8K or so
in size instead of the initial 512 bytes) with the rationale that if
files have been orphaned in the filesystem, one doesn't want to
allocate disk blocks while fsck is running (and in particular, blocks
for the lost+found directory) for fear of allocating blocks which are
part of a recoverable file.  Admittedly, I don't know much about
filesystem internals, so it could be that any block which would be
allocated to lost+found is beyond recovery by fsck anyway.

Just curious.

John