Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!mtuxo!jlw
From: jlw@mtuxo.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: help with missing lost+found!
Message-ID: <555@mtuxo.UUCP>
Date: Tue, 18-Aug-87 18:16:07 EDT
Article-I.D.: mtuxo.555
Posted: Tue Aug 18 18:16:07 1987
Date-Received: Fri, 21-Aug-87 05:22:17 EDT
References: <180@LOGICON.LOGICON.UUCP> <142700015@tiger.UUCP>
Organization: AT&T, Middletown NJ
Lines: 34
Summary: No block allocation involved

In article <142700015@tiger.UUCP>, authorplaceholder@tiger.UUCP.UUCP writes:
> 
> > >> 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!
> 
>   Are you sure I am wrong?  At least for Unix system V on the AT&T 3B2, 3B5,
> 3B15 computers, the ones I have most experience with, all that needs to be
> there is the directory.  I have lost BIG files and have them reappear properly
> after having "rm -r lost+found ; mkdir lost+found" it to get rid of trash.

Note that no blocks were allocated from the file system to create one file.
In fact any fsck should be able to save in lost+found up to 30 files since
mkdir automatically creates the . and .. entries.  This allocates the entire
first block of the directory and thus the addition of a small number of
file names/inumbers to the directory doesn't make it overflow into the next
block.

Joe Wood
lznv!jlw

a
b
c
d
e
f
g
h