Return to BSD News archive
#! rnews 1691 sserve.cc.adfa.oz.au Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoknor.edu!news.ecn.uoknor.edu!paladin.american.edu!gatech!news.sprintlink.net!helena.MT.net!nate From: nate@trout.sri.MT.net (Nate Williams) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: fsck *always* complains 'CLEAN FLAG IS WRONG IN SUPERBLOCK' Date: 16 May 1995 18:27:01 GMT Organization: SRI Intl. - Montana Operations Lines: 25 Message-ID: <3paqpl$bmk@helena.MT.net> References: <betts.20.14F77F52@onramp.net> Reply-To: "Nate Williams" <nate@sneezy.sri.com> NNTP-Posting-Host: trout.sri.mt.net In article <betts.20.14F77F52@onramp.net>, Jeff Betts <betts@onramp.net> wrote: >Just reinstalled FreeBSD 2.0 from CD to see if that made a difference, but the >problem persists. > >Whenever /etc/daily runs, *every* partition generates the same CLEAN FLAG IS >WRONG IN SUPERBLOCK error (output from /etc/daily is included below). The >same is true if I run fsck manually. The problem is that fsck should *not* be run on mounted filesystems, and will always complain about the error since the clean flag is sent when the file system is unmounted. The fsck commands have been removed from the master sources, and I suggest you remove them from your local copy of /etc/daily as well. It is no longer necessary to use fsck to check for possible corruptions since in the past it was used to signify a disk slowly going bad, but you had to know what to look for. Nate -- nate@sneezy.sri.com | Research Engineer, SRI Intl. - Montana Operations nate@trout.sri.MT.net | work #: (406) 449-7662 | Loving life in God's country, the great state of home #: (406) 443-7063 | Montana.