From owner-freebsd-questions Tue Apr 25 18:32:02 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA28771 for questions-outgoing; Tue, 25 Apr 1995 18:32:02 -0700 Received: from mg1.cdsnet.net (mrcpu@mg1.cdsnet.net [204.118.244.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA28725 for ; Tue, 25 Apr 1995 18:31:25 -0700 Received: (from mrcpu@localhost) by mg1.cdsnet.net (8.6.10/8.6.10) id SAA13457; Tue, 25 Apr 1995 18:31:17 -0700 Date: Tue, 25 Apr 1995 18:31:16 -0700 (PDT) From: Jaye Mathisen To: Allyn Hardyck cc: freebsd-questions@FreeBSD.org Subject: Re: fsck In-Reply-To: <199504251510.LAA01926@jupiter.avsi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.org Precedence: bulk Because on reboot, the file systems aren't mounted, so there are no processes out there with files open on the disk, nothing is being modified (no file creation, deletion, etc). When /etc/daily runs, processes are accessing the disk, and things are changing out from underneath fsck even as it checks. On Tue, 25 Apr 1995, Allyn Hardyck wrote: > I'm wondering why on reboot fsck seems to think the filesystems are > clean, yet in the /etc/daily output there seem to be a lot of > incorrect clean flags and unreferenced files. > > Thanks - Allyn Hardyck >