From owner-freebsd-hackers Sat Sep 23 04:55:52 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA01095 for hackers-outgoing; Sat, 23 Sep 1995 04:55:52 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA01084 for ; Sat, 23 Sep 1995 04:55:50 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id EAA03373; Sat, 23 Sep 1995 04:54:24 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id EAA00307; Sat, 23 Sep 1995 04:56:54 -0700 Message-Id: <199509231156.EAA00307@corbin.Root.COM> To: joshk@tanisys.com (Josh Karnes) cc: hackers@freebsd.org Subject: Re: trouble In-reply-to: Your message of "Fri, 22 Sep 95 09:48:58 GMT." <199509220948.JAA00261@hoover.tanisys.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 23 Sep 1995 04:56:54 -0700 Sender: owner-hackers@freebsd.org Precedence: bulk >that was months ago. We still get the same nagging error message every day: > >"CLEAN FLAG IS WRONG IN SUPERBLOCK" >"FIX? [yn]" > >We say "y", then reboot, then fsck and get the same error message. I'm not sure I understand. Are you running fsck every day or something? If so, don't do that. fsck is not intended to be run on mounted filesystems. If you run it and then answer 'yes' to any of the questions, you will certainly cause some form of filesystem corruption (although not probably serious). We used to run fsck in the /etc/daily script with the '-n' (nowrite), but when the foolishness of this was revealed (i.e. when lots of people started complaining about the bogus output), we removed it. It was never useful very useful, often lead to undo concern, and had significant amounts of overhead for people with lots of filesystems. Anyway, fsck should only be run on *unmounted* filesystems - such as the case during system startup. -DG