NetBSD Problem Report #2447

From gnats  Mon May 20 12:14:16 1996
Received: from bunnahabhain.pdl.cs.cmu.edu by pain.lcs.mit.edu (8.7.4/8.6.12) with ESMTP id LAA18949 for <[email protected]>; Mon, 20 May 1996 11:44:16 -0400 (EDT)
Message-Id: <[email protected]>
Date: Mon, 20 May 1996 11:43:40 -0400 (EDT)
From: [email protected]
Reply-To: [email protected]
To: [email protected]
Subject: clean file systems with 'unexpected inconsistencies' not dirtied
X-Send-Pr-Version: 3.95

>Number:         2447
>Category:       bin
>Synopsis:       fsck doesn't "dirty" file systems with weird errors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon May 20 12:20:15 +0000 1996
>Closed-Date:    
>Last-Modified:  Mon Jun 05 22:15:05 +0000 2000
>Originator:     Chris G. Demetriou
>Release:        19960520
>Organization:
Kernel Hackers 'r' Us
>Environment:
System: NetBSD bunnahabhain.pdl.cs.cmu.edu 1.1B NetBSD 1.1B (BUNNY) #41: Sun May 19 17:34:11 EDT 1996 [email protected]:/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.
>Release-Note:
>Audit-Trail:

From: der Mouse <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re:  bin/2447: clean file systems with 'unexpected inconsistencies' not dirtied
Date: Tue, 21 May 1996 06:22:31 -0400

 > 	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.

 I'm not so sure; if the filesystem is clean (well, is marked clean),
 fsck -p won't even run on it.  If you use -f with -p, well, you should
 also use -f with the manual run, no?  (I Hate Clean Bits...I Hate Clean
 Bits...I Hate Clean Bits... :-)

 On a side note, I would say that clri _definitely_ should dirty the
 filesystem it operates on.

 					der Mouse

 			    [email protected]
>Unformatted:

Home	PR Database Search