Xref: utzoo unix-pc.general:177 comp.sys.att:2118
Path: utzoo!utgpu!water!watmath!clyde!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
Summary: Oops, it's the thought that counts
Keywords: /lost+found, fsck, filesystem, crash
Message-ID: <179@shlepper.ATT.COM>
Date: 19 Jan 88 15:27:49 GMT
References: <214@icus.UUCP> <178@shlepper.ATT.COM>
Organization: AT&T Bell Laboratories, Middletown, NJ
Lines: 44

In article <178@shlepper.ATT.COM>, I wrote:
> 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*
> 



Hey, what can I say, I blew it.  The correct script should be:

mkdir /lost+found
cd /lost+found
for i in 1 2 3 4 5 6 7 8
do
for j in 1 2 3 4 5 6 7 8
do
cat >tmp$i$j <<FUNKYSTUFF
dummy line
FUNKYSTUFF
done
done
rm tmp*

Some one has pointed out that you don't need to actually allocate
space in the tmp$i$j files so that "cat >tmp$i$j" would probably do
it instead of all the funky stuff.

Flames to /dev/null...
-- 
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