Rename lost+found (to say lost2), shut down to single user and
	run 'fsck -f, then boot up & delete lost2


		David/abs

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

On Sat, 16 Aug 1997, Armen Babikyan wrote:

> okay, i've had this problem before, i figured i'd mention it instead of
> ignore it:
> ---cut here---
> friction:/lost+found# rm -rf *         (long wait goes here)
> /: bad dir ino 7168 at offset 632320: mangled entry
> panic: bad dir
> Stopped at       _Debugger+0x6:   unlk       a6
> db> t         (after this is typed, the system doesn't seem to want to
> work, so i hit the interrupt button)
> db> tPanic switch: PC ix 0x96e10.
> Stopped at  _Debugger+0x6:   unlk         a6
> db>
> ---cut here---
> after that message, the system does respond to any more commands, interrupt
> switch doesn't work either. i have a Mac IIvx 33Mhz 68030, 20MB RAM, 32MB
> swap,  quantum270MB hard drive, running NetBSD/mac68k 1.2 GENERIC#1 kernel.
> (???)
> i have a feeling this occured when a friend of mine ran a forkbomber on my
> system when he was frustrated about it's slowness or something ;-)
> i.e. main(){while(1), fork();}
> oh yeah, i did this whole escapade when  i was ls-ing for some files, and
> i'd get error messages about ls-ing them because of some filesystem
> problem. i can't remember what they were.
> if i left out any information, please tell me.
> thanks,
>   - a
> 
>  Armen Babikyan - armenb@moof.ai.mit.edu
>     ----<insert lame quote here>----
> 
>