>Number:         2447
>Category:       bin
>Synopsis:       fsck doesn't "dirty" file systems with weird errors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon May 20 12:20:15 1996
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
Kernel Hackers 'r' Us
>Release:        NetBSD-current as of May 20, 1996
>Environment:
System: NetBSD bunnahabhain.pdl.cs.cmu.edu 1.1B NetBSD 1.1B (BUNNY) #41: Sun May 19 17:34:11 EDT 1996 cgd@bunnahabhain.pdl.cs.cmu.edu:/usr/src/sys/arch/alpha/compile/BUNNY alpha


>Description:
	If fsck -p finds an 'unexpected inconsistency' in a file system,
	it doesn't mark the file system as dirty.  I'd say that it should.

>How-To-Repeat:

	clri an inode on a file system.  unmount it.  run 'fsck -fp' then
	run 'fsck'.  You'll get messages like:

	balvenie# fsck -fp /dev/rsd2a
	/dev/rsd2a: UNALLOCATED  I=3302  OWNER=root MODE=0
	/dev/rsd2a: SIZE=0 MTIME=Dec 31 19:00 1969 
	/dev/rsd2a: NAME=/root/.klogin
	
	/dev/rsd2a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
	balvenie# fsck /dev/rsd2a 
	** /dev/rsd2a
	** File system is clean; not checking

	This isn't necessarily a bug, however, it seems ... a bit odd
	for fsck to discard useful information like this, especially
	when the information points to a problem which could cause
	file system corruption or a system panic in the future.

>Fix:
	None supplied.
>Audit-Trail:
>Unformatted: