Subject: Re: fsck clears non-empty files
To: Space Case <>
From: Chris G. Demetriou <cgd@postgres.Berkeley.EDU>
List: current-users
Date: 05/07/1994 21:32:55
> I think I'll try an experiment.  If I make a copy of a file, do a
> clri on the copy, then reboot, the ensuing fsck should put it in
> lost+found, right?

NO; if you clear a file's inode, that file is GONE.  period.

if you clear a file's directory's inode, or otherwise get it into
a state where it has no directory entry, THEN it goes into lost
and found.

blocks without inodes are not files.  inodes without names are lost.