Xref: utzoo unix-pc.general:204 comp.sys.att:2199
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!rutgers!gatech!ufcsv!codas!mtune!shlepper!andys
From: andys@shlepper.ATT.COM (a.b.sherman)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: Recommendation to mkdir /lost+found on UNIX pc
Message-ID: <178@shlepper.ATT.COM>
Date: 16 Jan 88 19:44:58 GMT
References: <214@icus.UUCP>
Organization: AT&T Bell Laboratories, Middletown, NJ
Lines: 30
Keywords: /lost+found, fsck, filesystem, crash
Summary: You must put some files in there too

In article <214@icus.UUCP>, lenny@icus.UUCP (Lenny Tropiano) writes:
> [Description of fsck output on reboot after crash]
> Now the "RECONNECTED" message only is good if a directory /lost+found
> is created on each filesystem.  The UNIX PC/3B1 doesn't have one, so
> I would suggest creating one.  This means that the file at i-node 2650
> was being modified at the crash time, and it went to place it's contents
> in /lost+found/<i-node>!  After you fsck is run, I would check that
> directory's contents for missing or corrupted file :-)


In order for fsck to put something in /lost+found the directory must
have some block allocated to it.  In order to accomplish that you
should create a bunch of files and then delete them.  Like this:


mkdir /lost+found
cd /lost+found
for i in 1 to 64
do
cat >tmp$i <<FUNKYSTUFF
dummy line
FUNKYSTUFF
done
rm tmp*

If you don't allocate the space, fsck won't reconnect your files.
-- 
Andy Sherman / AT&T Bell Laboratories (Medical Diagnostic Systems)
480 Red Hill Road / Middletown NJ 07748 / (201) 615-5708
UUCP: {ihnp4,allegra,akgua,cbosgd,mtune....}!shlepper!andys
INTERNET: andys@shlepper.ATT.COM