Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mimsy!cvl!decuac!macom1!michael
From: michael@macom1.UUCP (Michael Mullins)
Newsgroups: comp.unix.wizards
Subject: Re: help with missing lost+found!
Message-ID: <251@macom1.UUCP>
Date: Thu, 13-Aug-87 17:07:44 EDT
Article-I.D.: macom1.251
Posted: Thu Aug 13 17:07:44 1987
Date-Received: Sat, 15-Aug-87 11:58:48 EDT
References: <142700014@tiger.UUCP>
Organization: CENTEL Business Information Systems INC.,Rockville, MD.
Lines: 33

in article <142700014@tiger.UUCP>, rjd@tiger.UUCP says:
> Nf-ID: #R:LOGICON.LOGICON.UUCP:-18000:tiger.UUCP:142700014:000:277
> Nf-From: tiger.UUCP!rjd    Aug 11 09:03:00 1987
> 
> 
> 
>> Do any of you wizards out there in netland have a quick and easy way
>> (BESIDES running mkfs) to recreate an accidentally deleted lost+found
>> directory? Using mkdir() doesn't cut it...
> 
>    Why not?  Mkdir() works on my machine....   What kind of machine are
> you on?

Wrong!

Just making a new lost+found directory is not sufficient.  The typical
procedure is to mkdir lost+found and then use some kind of script to make
about 2000 NULL files, then remove them.  This provides enough entries in
the directory database to link a whole bunch of lost files to that directory
when fsck finds them.  If fsck discovers 500 unreferenced files, and the 
maximum number of files that had ever been created at one time was 10, guess
what?  You just lost 490 files forever!

Maybe some of you Guru's out there could map out the disk and trace every 
single sector by hand, but that will take more time than I can possibly 
spend on something like that, and you will still loose data if UN*X has marked
these blocks as avail. and some other file decides to use the space.

-- 
John Michael Mullins
CENTEL Business Information Systems, Inc.
5515 Security Lane, Rockville, Maryland, 20852, (301) 984-3636
UUCP:   michael@macom1.UUCP 	or	decuac!macom9@tly (the