From owner-freebsd-questions@FreeBSD.ORG Tue Mar 14 04:54:36 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 005F916A401 for ; Tue, 14 Mar 2006 04:54:35 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DC2143D45 for ; Tue, 14 Mar 2006 04:54:35 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id ACF633133D; Mon, 13 Mar 2006 23:54:34 -0500 (EST) Date: Mon, 13 Mar 2006 23:54:34 -0500 (EST) From: Ensel Sharon To: "illoai@gmail.com" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-questions@freebsd.org Subject: Re: how does a system come up if you disable background fsck ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 04:54:36 -0000 On Mon, 13 Mar 2006, illoai@gmail.com wrote: > On 3/13/06, Ensel Sharon wrote: > > > > I have disabled background fsck in my /etc/rc.conf with: > > > > background_fsck="no" > > > > But I am curious - what does this mean for the system if the system > > crashes ? > > > > Does this mean that the system will wait for all non root partitions to > > fully fsck before coming up into multi-user mode ? > > > > OR > > > > Does it mean the system will boot up quickly into multi-user mode, but the > > non-root partitions will just not be mounted and/or usable until I fsck > > them by hand ? > > Hit the power button and see for yourself. Ok, I did. The fsck on the filesystem, if I do it manually while in multi-user mode, ususally takes two hours. This time, the machine took about 20 minutes to come back up from my ungraceful power cycle. I also notice that /var/run/dmesg.boot is a zero byte file, and /var/log/messages has nothing about the boot cycle in it. So, two questions: - is the lack of data in /var because it was a non-root filesystem and was busy fscking when dmesg.boot and messages would normally be written ? - why did the machine come up 20 minutes later ? I would htink either it would come up right away, or come up two hours later ... perhaps / and /var were fsck'd at boot, and my big partition is actually mounted dirty ? Thanks.