From owner-freebsd-questions@FreeBSD.ORG Fri Feb 13 09:51:30 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 340A2106564A for ; Fri, 13 Feb 2009 09:51:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id E4D5D8FC1D for ; Fri, 13 Feb 2009 09:51:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-196-52-176.dynamic.qsc.de [92.196.52.176]) by mx01.qsc.de (Postfix) with ESMTP id 5767C3CFA9; Fri, 13 Feb 2009 10:51:21 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n1D9pEWt001734; Fri, 13 Feb 2009 10:51:15 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Fri, 13 Feb 2009 10:51:14 +0100 From: Polytropon To: Robert Huff Message-Id: <20090213105114.1cf2ed84.freebsd@edvax.de> In-Reply-To: <18836.61520.37080.844269@jerusalem.litteratus.org> References: <4994B999.1090307@networktest.com> <20090213004128.GA79335@gizmo.acns.msu.edu> <4994C29E.3020506@networktest.com> <20090212171653.3782fb82@gom.home> <20090213032150.GB79893@gizmo.acns.msu.edu> <18836.61520.37080.844269@jerusalem.litteratus.org> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: recovering from a power outage X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 09:51:30 -0000 On Thu, 12 Feb 2009 23:00:16 -0500, Robert Huff wrote: > 1) It was my understanding one has to force-mount a dirty > filesuystem. IF this sounds like a practice best left to senior > Jedi Masters ... it porbably is. Mounting possibly defective file systems is not a good idea. If it's possible, boot into SUM via boot -s first, check partitions (unmounted!) and then mount -a. Use "exit" to bring up MUM afterwards. Setting background_fsck="NO" in /etc/rc.conf may increase boot time if problems occur, but can be useful to first check for errors, and then bring up the system, instead of bringing up the system with maybe problems on the partitions. I think this delay is something you can affort. It's not good to fsck a mounted partition anyway, because fsck can repair minor defects on its own. > 2) I would _never_ let background fsck "take care of things" > after a crash, While hovering over the keyboard is a pain, I will > find out how badly things are damaged, rather than have boatloads of > files mysteriously vanish. That's a good concept which I do follow myself, too. I spend some minutes seeing fsck checking partitions after unclean shutdown, but when everything's okay, there's no problem running into MUM *afterwards*. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...