On Thu, 27 Aug 1998, Jeff Woolley wrote:

> >> During the compile of GhostScript, the machine crashed.
> >> 
> >>     panic: cleaned vnode isn't stopped at _Debugger+0x6: unlk a6
> >>     db>trace
> >>     _Debugger(0,8b7ccc,3f6b4,3f59c,3f58e) + 6
> >>     _panic(3f58e,6c43380,0,408) + 40
> >>     _getnewvnode(1,6c0ee00,6bf9200,8b7d0c) + e0
> >>     _ffs_vget(6c0ee00,2443,8b7d90) 60
> >>     _ufs_lookup(8b7e00) a46
> >>     _lookup(8b7e9c) + 23e
> >>     _namei(8b7e9c) + 152
> >>     _sys___lstat13(6c3a200,8b7f88,8b7f80) + 2c
> >>     _syscall(118) + 13e
> >>     _trap0() + e
> >>     db>
> >> 
> >> What happened?
> >
> >I'm not sure but this is weird...  The panic message isn't even
> >complete.  However, if fsck after reboot finds nothing wrong with your
> >filesystem, it's probably OK.
> 
> I copied it from the screen, but that's all that was there.
> 
> It stopped in single user and said run fsck_ffs manually. I did, and 
> answered yes for everything that was messed up.

Be sure to re-run fsck until it doesn't find any more errors. If you've
already marked the file-system clean, do that with 'fsck -f'.

You might like to know that work is being done on a a "pkgtools' package,
which is to allow folks with older systems to use the - current pkgsrc. 
Is that what you're doing? If so, it's possible that you would have better
luck with the pkgsrc in the 1.3.2 distribution.