>Number:         1173
>Category:       bin
>Synopsis:       the only way to ignore FS clean flag is to fsck w/o -p
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 29 06:35:00 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:
	'fsck -p' won't check file systems whose 'clean' flags are set.
	Indeed, there's no way to make it check 'clean' file systems.

	On some systems (or in the presence of file system bugs), one
	might want to be sure that file systems are checked regardless
	of whether or not they think they're clean.  Most (all?) other
	systems which support 'clean' flags in file systems supply
	a way to do this (SunOS: '-f', ULTRIX (i think) & DEC
	UNIX: '-o').

	It's vitally important to be able to force preening of clean
	file systems, because one can't safely use 'fsck' (i.e.
	not just preening) from /etc/rc.

>How-To-Repeat:
	try to preen a 'clean' file system

>Fix:
	add a flag to force preening of clean file systems.  I'm more
	used to '-o' (because i tend to live on DEC hardware), but
	'-f' would be more intuitive.
>Audit-Trail:
>Unformatted: