Subject: fsck == no-op on reboot after crash?
To: None <current-users@netbsd.org>
From: Jon Buller <jon@bullers.net>
List: current-users
Date: 06/05/2003 18:20:31
My Sparc20 doesn't go down very often, but lately it has not been
cleaning the disks after the local power company decides I can be
without for a few seconds.

So what just about always happens in this case is that the machine
comes up, and I get stuff like this:

Jun  5 17:45:37 ra /netbsd: /dev/sd0a: file system not clean (fs_clean=4); please fsck(8)

Rebooting the machine into single-user and typing fsck -p results
in no output, no appearent actions, and a quick new shell prompt.
Then typing fsck /dev/sd0a goes through the whole process of actually
checking, asking my what I want to do with all those blocks and
files, etc.  Then everything is fine.  Note that I do not get
messages saying the disk(s) is clean, not checking...

Ident on /sbin/fsck returns this:

     $NetBSD: crt0.c,v 1.10 2002/02/11 06:08:23 mrg Exp $
     $NetBSD: fsck.c,v 1.29 2002/08/23 03:17:18 lukem Exp $
     $NetBSD: fsutil.c,v 1.11 2001/11/09 07:50:19 lukem Exp $
     $NetBSD: preen.c,v 1.24 2002/07/20 08:36:26 grant Exp $

Any suggestions would be appreciated, as this is starting to be a
real pain.  Oh, and before I forget, this all started after my 1.6
-> current+SMP upgrade.  Don't know if it's related, but I did that
shortly before it got turned on by default (and not just spinning up
the other CPUs and leaving them idle).

Jon