Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-lcc!lll-winken!uunet!toro!nick
From: nick@toro.UUCP (Nicholas Jacobs)
Newsgroups: comp.unix.wizards
Subject: fsck's & lost+found directory question
Message-ID: <359@toro.UUCP>
Date: 2 May 89 16:49:39 GMT
Reply-To: nick@toro.UUCP (Nicholas Jacobs)
Distribution: usa
Organization: MTS - Merrill Lynch Capital Markets Information Systems
Lines: 18

We are running SysV.2 on an NCR Tower 32/650 here and came up with
a strange situation the other day. Our machine crashed and when I
went to do fsck's on the various file systems, fsck complained about
the directory "lost+found" not existing. After a lengthy discussion
with an NCR analyst, we discovered that the lost+found directory
must exist in each file system. 

Since this was not documented under fsck (NCR's documentation comes
from AT&T), I was wondering if this is the case with all ports of
SysV (and/or BSD)?  Does this mean that fsck goes into the device file
and tries to find the actual directory (I would assume yes...)?

Please email any comments and/or suggestions concerning this matter.
Thanks,

Nicholas Jacobs
UUCP: ...!uunet!toro!nick Internet: toro!nick@uunet.uu.net
AT&T: (212) 236-3230