From owner-freebsd-questions  Sun Nov  3 17:00:44 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA17954
          for questions-outgoing; Sun, 3 Nov 1996 17:00:44 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17719
          for <questions@FreeBSD.org>; Sun, 3 Nov 1996 16:58:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id QAA25077; Sun, 3 Nov 1996 16:56:55 -0800 (PST)
Message-Id: <199611040056.QAA25077@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Suresh Rao <suresh.rao@nswcc.org.au>
cc: questions@FreeBSD.org
Subject: Re: Help requested for FreeBSD site experiencing 'fsck' errors 
In-reply-to: Your message of "Mon, 04 Nov 1996 11:15:18 PST."
             <327E40C6.1FFF@nswcc.org.au> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 03 Nov 1996 16:56:55 -0800
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>We are an organisation running FreeBSD 2.0 for our Web servers. We have 
>been experiencing errors reported by the 'fsck' utility during a nightly 
>integrity run for a while, and we would like to correct these errors but 
>are unsure whether this will cause any instability in the servers. The 
>nightly run automatically says 'no' to all fsck questions. The servers 
>appear to be running normally but the number of errors seems to be 
>increasing. Errors are of types such as 'CLEAN FLAG IS WRONG IN 
>SUPERBLOCK', 'INCORRECT BLOCK COUNT', 'UNALLOCATED', DIRECTORY 
>CORRUPTED', 'UNREF FILE', etc.
>
>We would like any information relating to the correction of 'fsck' 
>errors, and your advice as to whether it should be safe to say 'yes' to 
>all of the 'fsck' prompts for corrections.

   The nightly run of "fsck" was a mistake. Please comment it out in your
/etc/daily script. That has been removed in later versions of FreeBSD (which I
strongly recommend that you upgrade to - 2.0 was very buggy). Running fsck
on an active filesystem will always generate various errors and thus tells
you nothing.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project