Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!ucbcad!ucbvax!unisoft!mtxinu!ed From: ed@mtxinu.UUCP (Ed Gould) Newsgroups: comp.unix.wizards Subject: Re: help with missing lost+found! Message-ID: <475@mtxinu.UUCP> Date: Sat, 22-Aug-87 16:08:27 EDT Article-I.D.: mtxinu.475 Posted: Sat Aug 22 16:08:27 1987 Date-Received: Sun, 23-Aug-87 15:04:04 EDT References: <180@LOGICON.LOGICON.UUCP> <2836@phri.UUCP> <657@hplabsz.HPL.HP.COM> Reply-To: ed@mtxinu.UUCP (Ed Gould) Organization: mt Xinu, Berkeley Lines: 19 >I vaguely know what the lost+found directory does for a disk partition. Can >someone explain the reason for needing 100 empty files in the directory? >What happens if you just do mkdir /lost+found and leave it at that? The lost+found directory is used by fsck to recover "lost" files and directories. When it finds an allocated file with no name, it will (potentially) link it into the lost+found directory. However, since fsck does not yet know that the filesystem is in a consistent state, it doesn't want to allocate any new space to lost+found. Hence the need to create lots of empty slots. The fsck that comes with 4.3bsd has been improved in this regard, but newfs (mkfs) still creates 4K- or 8K-byte lost+found directories. -- Ed Gould mt Xinu, 2560 Ninth St., Berkeley, CA 94710 USA {ucbvax,decvax}!mtxinu!ed +1 415 644 0146 "A man of quality is not threatened by a woman of equality."