Hello,

I've been fooling around with a 486 machine running NetBSD-1.2G (I
think, it's a current from early June), getting the machine in
power-saving, suspended mode and making its local ffs filessystems
operate synchronously (these things may be irrelevant, but while
changing these things fsck broke down, sooo...). Now on boottime fsck
fails with a `Bus Error'. Manual execution of fsck results in the same
behaviour except for the added core dump. A ktrace showed that fsck
reads the fstab file and core dumps shortly after that. It never comes
to start any actual filesystem check. When I empty fstab altogether
fsck does not coredump (it does not do much either, of course). Doing
a direct fsck_ffs (-p) on the filesystems in questions works fine, so
that's in my current /etc/rc. I tried several of the most obvious
stuff to get fsck up and running again, although I haven't rebuild
fsck with symbol info to see where it exactly goes wrong (is a bit
difficult for me to do at this moment). Anyone seen similar behaviour
or has a clue what's bugging fsck???

Just being a bit worried...

{ Feico Dillema,                                                        }
{ University of Twente, P.O. Box 217, 7500 AE Enschede, The Netherlands }
{ Install NetBSD as first step in your MS-ware 12-step recovery program }