Date: Thu, 21 Mar 1996 10:58:03 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: j@uriah.heep.sax.de (J Wunsch) Cc: freebsd-current@freebsd.org Subject: Re: lost+found ??? Message-ID: <199603211758.KAA00406@phaeton.artisoft.com> In-Reply-To: <199603211259.NAA13192@uriah.heep.sax.de> from "J Wunsch" at Mar 21, 96 01:59:43 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> As Michael Smith wrote: > > > > What do I need to do? > > > > Nothing, fsck creates them as it needs them. > > ...thereby happily destroying arbitrary disk data if it has to extend > the root directory and fails to find free space to do so. > > newfs should create it. I argued this one and lost. I think you are right, though, in the basis that the files may be coming from directories with sufficient free space, requiring additional directory blocks to be allocated to recover name information. Such blocks are not necessarily freed by the process causing files to end up in lost+found. Even in the case where blocks are freed, the names in lost+found are based on the inode number and may cause less entries per block than were in the block before the names were "lost" if the files all had short names (ie: 3 characters or less is 8 bytes per name in the directory entry block). While we are on the subject, did anyone commit my fix so that fsck doesn't have to be run twice in the case that it's creating lost+found? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603211758.KAA00406>