From owner-freebsd-questions Tue Feb 14 03:05:41 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA17706 for questions-outgoing; Tue, 14 Feb 1995 03:05:41 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id DAA17694 for ; Tue, 14 Feb 1995 03:05:37 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id DAA18812; Tue, 14 Feb 1995 03:05:29 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id DAA02615; Tue, 14 Feb 1995 03:05:28 -0800 Message-Id: <199502141105.DAA02615@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Andreas Schulz cc: tsai@server.keck.lmu.edu, questions@FreeBSD.org Subject: Re: Clear Flag in SUPERBLOCK? In-reply-to: Your message of "Tue, 14 Feb 95 11:47:09 +0059." <199502141047.LAA23197@g386bsd.first.gmd.de> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 14 Feb 1995 03:05:25 -0800 Sender: questions-owner@FreeBSD.org Precedence: bulk > >> After I install the FreeBSD 2.0. I use fsck to ckeck my hard drive, but it >> always tell me that "clear flag in superblock is incorrect". I press y to cleanthis, but it still the same when I run fsck again. I also use fsck -p to clean this error, but it still give me the same message. I really don't know what is going on. > >You should only use fsck, if you are in single user mode. I suspect you >have your machine booted into multi-user mode. Then fsck will always >tell you that for all the mounted filesystems. You can boot into single >user mode at the Boot: prompt with the "-s" flag. We need to write a >boot man page :-). You should never set the clean flag on a mounted filesystem...for that matter, you should never run fsck on a mounted filesystem without the -n (nowrite) flag. If fsck does write to the mounted filesystem, it can destroy data and/or cause the machine to panic because of the corruption it causes. There is no synchronization between the changes that fsck makes and the changes the kernel makes. -DG