>Number:         1172
>Category:       kern
>Synopsis:       'fs clean' code can cause system crash, bogus clean markings
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 29 06:20:01 1995
>Originator:     Chris G. Demetriou
>Organization:
Kernel Hackers 'r' Us
>Release:        6/27/95 -current
>Environment:
System: NetBSD sun-lamp.pc.cs.cmu.edu 1.0A NetBSD 1.0A (SUN_LAMP) #0: Sun Jun 18 16:41:02 EDT 1995 cgd@sun-lamp.pc.cs.cmu.edu:/usr/src/sys/arch/i386/compile/SUN_LAMP i386


>Description:
	FS unmounting/'clean' code can cause system to crash on reboot,
	and can leave file systems incorrectly marked 'clean.'

	This is probably the cause of some of the hangs on reboot
	that people have been reporting.

>How-To-Repeat:

	cd /usr/src/sbin/init ; make ; make install ; reboot

	note crash and/or trouble rebooting.  on reboot:

	fsck -p

	note that fsck says that root file system is clean.  then:

	fsck

	note that root file system (MARKED CLEAN!!!) was actually dirty.

>Fix:
	Dunno; if i'd had time to track it down, i would have.
>Audit-Trail:
>Unformatted: