Subject: Re: LFS Crash Behavior
To: Gary Duzan <>
From: Frederick Bruckman <>
List: current-users
Date: 05/14/1999 06:36:01
On Fri, 14 May 1999, Gary Duzan wrote:

>    After my 1.4 system crashed (for unknown reasons) while attempting
> to build Mozilla on an LFS disk I get this:
> wheel { ~ } % ls -l /disk1/mozilla/layout/build
> ls: nsBoxFrame.o: No such file or directory
> ls: nsCaret.o: No such file or directory
> Is this the expected behavior? How do I get rid of these phantom files
> without making things worse? The data isn't vital (or I wouldn't have
> it on an LFS) but it could take a bit to restore everything, and I'd
> rather not if I don't have to.

I tried using an LFS directory for /home for about a month on my desktop
system, under -current and then 1.4beta and 1.4. It never failed to wig
out after a while. `fsck -n /home' would give "unreferenced file" errors,
and then lfs_cleanerd would emit errors periodically. The only fix was to
to tar up all the files, newfs_lfs, and then untar them back.

> p.s. fsck_lfs isn't referenced from the fsck(8) man page. I'm not
> sure if this is a bug or a feature.