Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ll-xn!mit-eddie!husc6!hao!oddjob!gargoyle!ihnp4!cbosgd!mandrill!hal!ncoast!axcess!allbery
From: allbery@axcess.UUCP (Brandon S. Allbery)
Newsgroups: comp.sys.att
Subject: Re: Recommendation to mkdir /lost+f
Message-ID: <144@axcess.UUCP>
Date: 29 Jan 88 13:24:54 GMT
References: <178@shlepper.ATT.COM> <144800017@occrsh.ATT.COM> <2700@pbhyf.UUCP>
Organization: aXcess Company, Mentor, Ohio
Lines: 20
Summary: the problem is what happens when the free list is corrupted

In article <2700@pbhyf.UUCP>, tlh@pbhyf.UUCP (Lee Hounshell) writes:
+---------------
| In article <144800017@occrsh.ATT.COM> rjd@occrsh.ATT.COM writes:
|  >  On the same note: I was a little fuzzy why fsck required already-made
|  >but empty directory entries or allocated blocks.  I seem to recall that
| 
| Yeah.. so was mine, and fsck reconnected about 10 files for me with no
| problems about 3 weeks ago.  I suspect that the directory slot stuff is
| only specific to Berkeley unix.. it certainly isn't needed for the 3B1.
+---------------

The reason you want preallocated blocks is that fsck has to allocate blocks
from the free list otherwise.  But free list repairs are the LAST thing
done... so if a block is on the free list by mistake (i.e. also allocated to a
file) you'll end up with even worse corruption.
-- 
 ___  ________________,	Brandon S. Allbery	       cbosgd \
'   \/  __   __,  __,	aXcess Company		       mandrill|
 __  | /__> <__  <__	6615 Center St. #A1-105		       !ncoast!
/  ` | \__. .__> .__>	Mentor, OH 44060-4101	       necntc  | axcess!allbery
\___/\________________.	Moderator, comp.sources.misc   hoptoad/