From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 15:09:54 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B419916A412 for ; Wed, 27 Sep 2006 15:09:54 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BE7843D77 for ; Wed, 27 Sep 2006 15:09:53 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mbcncv@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8RF9kgd023505 for ; Wed, 27 Sep 2006 17:09:52 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8RF9kWg023504; Wed, 27 Sep 2006 17:09:46 +0200 (CEST) (envelope-from olli) Date: Wed, 27 Sep 2006 17:09:46 +0200 (CEST) Message-Id: <200609271509.k8RF9kWg023504@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 27 Sep 2006 17:09:52 +0200 (CEST) Cc: Subject: File systems clean after crash? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 15:09:54 -0000 Hi, Yesterday a machine of mine crashed because of a bad power supply (not FreeBSD's fault); its running 6.2-PRERELEASE as of 2006-09-20. I've disabled background fsck in rc.conf. So, when rebooting I expected it to report all filesystems to be unclean and run fsck on them. Instead, three filesystems were reported as being clean (the root FS, /var and /usr), and only the forth one (/home) was actually fsck'ed. Now I wonder why three of the file systems were reported as being clean. It's my understanding that file systems are only marked clean when they're unmounted. Did that change recently? The system was idle at the time of the crash, and soft-updates was enabled, so it's possible that there weren't any write accesses to the file systems within some time frame (a few minutes, I guess). Does the UFS code mark a mounted file system as clean if there wasn't any write operation for a certain time? Best regards Oliver PS: I'm paranoid, so I rebooted again into single-user mode and forced fsck on all file systems, just to be sure. Everything seems to be OK. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "In My Egoistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton