Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!ames!coherent!next!mmeyer
From: mmeyer@next.com (Morris Meyer)
Newsgroups: comp.sys.next
Subject: Re: fsck messages on a reboot
Message-ID: <79@next.com>
Date: 11 Dec 89 16:46:27 GMT
References: <11993@phoenix.Princeton.EDU> <309@kgw2.UUCP> <1989Dec10.223805.17331@agate.berkeley.edu>
Reply-To: mmeyer@entropy.next.com (Morris Meyer)
Organization: NeXT, Inc.
Lines: 18

In article <1989Dec10.223805.17331@agate.berkeley.edu> izumi@violet.berkeley.edu (Izumi Ohzawa) writes:
>However, I don't think full fsck is performed on normal reboots
>(if any), because boot messages say something like "filesystem clean --
>skipping fsck ...".
>I think there's probably a "filesystem dirty" flag in the
>battery backed CMOS RAM which is cleared upon orderly shutdown, and
>unless this bit indicates otherwise fsck is not done on subsequent
>reboots.
>
>Izumi Ohzawa, izumi@violet.berkeley.edu

The filesystem dirty bit is stored in the superblock.  It is set
on shutdown by the UFS code after every local inode is determined
to be unreferenced and sync'd on the disk.

		morris meyer (mmeyer@next.com)
		software engineer
		NeXT OS Group