Your disk was corrupted for some reason - fsck should be run
	automatically on every boot, but if it thimks the disk is 'clean'
	it will skip the check for speed reasons. '-f' 'forces' it to make
	the check.

	'lost+found' is where files/dirs recovered from a corrupted disk
	are stored. If lost+found is corrupted then... well, anything
	could happen I think :)

	As to which of the above was the problem... who knows? :)

		David/abs

  -- "Its hard to say it... I hate to say it... but its probably me..." --

On Sun, 17 Aug 1997, Armen Babikyan wrote:

> At 6:44 PM -0700 8/16/97, David Brownlee wrote:
> >	Rename lost+found (to say lost2), shut down to single user and
> >	run 'fsck -f, then boot up & delete lost2
> >
> 
> interesting
> this fixed the problem. why did this work?
> thanks a lot!
>   - a
> 
>  Armen Babikyan - armenb@moof.ai.mit.edu
>     ----<insert lame quote here>----
> 
>