From owner-freebsd-questions@FreeBSD.ORG Tue Mar 14 05:40:35 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 DFF7416A401 for ; Tue, 14 Mar 2006 05:40: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 6E58843D45 for ; Tue, 14 Mar 2006 05:40:35 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 7D43D31311; Tue, 14 Mar 2006 00:40:34 -0500 (EST) Date: Tue, 14 Mar 2006 00:40:34 -0500 (EST) From: Ensel Sharon To: Micah In-Reply-To: <4416483E.70600@ywave.com> 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 05:40:36 -0000 On Mon, 13 Mar 2006, Micah wrote: > 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 ? > > > > thanks. > > The former, as I can say with ample experience this morning. (stupid USB > panic) That's kind of what I thought, but as I said, I just tested it, and what happened was: - system takes 20 mins or so to boot - partition that lives on system that takes 2 hours to fsck is mounted - I unmount it and fsck it by hand, and it is indeed dirty - meanwhile, a lot of /var logs and dmesg.boot are zero/missing So it looks like it fsck'd / and /var, and just mounted the big partition dirty. Is this expected ?