From owner-freebsd-stable@FreeBSD.ORG Tue Jan 4 10:22:39 2005 Return-Path: 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 0741316A4CE for ; Tue, 4 Jan 2005 10:22:39 +0000 (GMT) Received: from lp1001.snu.ac.kr (lp1001.snu.ac.kr [147.46.70.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606EE43D1F for ; Tue, 4 Jan 2005 10:22:38 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [IPv6:::1] (localhost [127.0.0.1]) (authenticated (0 bits)) by lp1001.snu.ac.kr (8.13.1/8.11.6) with ESMTP id j04AKJ3j002631 for ; Tue, 4 Jan 2005 19:20:20 +0900 Message-ID: <41DA6E6C.8030505@yahoo.com> Date: Tue, 04 Jan 2005 19:22:36 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20041226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: fsck: broken file system with background check remains broken after bootup X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 10:22:39 -0000 Hi, I had following situation: Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr filesystem in a very broken state. During next bootup, there was indeed the message telling 'not properly unmounted', but boot continued with background fsck after 60 seconds; although I have fsck_y_enable="YES" in /etc/rc.conf. Because /usr was bad, the system hang immediately after bootup. I had to hit the power button (grump) to get a reboot....causing possibly more problems. I fixed it, by going into single user mode and do a manual fsck on all the filesystems. This way /usr got fixed and the system rebooted fine. This scared me. What if /usr was such broken that even single user mode would hang!?! Moreover, the main user of this PC is not a Unix guru and I hoped that the configuration setting in /etc/rc.conf of fsck_y_enable would do an automatic fix at bootup, like it used to do with 4.10. However, that apparently does not happen anymore. What can I do to enforce an immediate fix of the filesystems at bootup with FreeBSD 5.3, when a filesystem is not properly unmounted at shutdown? I suppose I should not change default background_fsck ("YES"). How about the background_fsck_delay? Should I set this to "0"? Thanks, Rob.