Xref: utzoo unix-pc.general:203 comp.sys.att:2198
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!rutgers!mtune!icus!lenny
From: lenny@icus.UUCP (Lenny Tropiano)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Recommendation to mkdir /lost+found on UNIX pc
Message-ID: <214@icus.UUCP>
Date: 16 Jan 88 03:01:25 GMT
Organization: ICUS Computer Group, Islip, NY
Lines: 28
Keywords: /lost+found, fsck, filesystem, crash

I noticed when the system crashes and the fsck is run at boot time
that it says this:

  /dev/fp002   UNREF FILE  I=2650  OWNER=lenny MODE=100755
  /dev/fp002   SIZE=5190 MTIME=Jan 14 20:45 1988  (NOT EMPTY)
 (RECONNECTED)
  /dev/fp002   1 BLK(S) MISSING
  /dev/fp002   BAD FREE LIST
  /dev/fp002   SALVAGED
  /dev/fp002   10452 files 101334 blocks 17718 free

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 :-)

							-Lenny
-- 
============================ US MAIL:   Lenny Tropiano, ICUS Computer Group
 IIIII   CCC   U   U   SSSS             PO Box 1
   I    C   C  U   U  S                 Islip Terrace, New York  11752
   I    C      U   U   SSS   PHONE:     (516) 968-8576 [H] (516) 582-5525 [W] 
   I    C   C  U   U      S  AT&T MAIL: ...attmail!icus!lenny  TELEX: 154232428
 IIIII   CCC    UUU   SSSS   UUCP:
============================    ...{uunet!godfre, harvard!talcott}!\
                   ...{ihnp4, boulder, mtune, bc-cis, ptsfa, sbcs}! >icus!lenny 
"Usenet the final frontier"        ...{cmcl2!phri, hoptoad}!dasys1!/