From owner-freebsd-questions@FreeBSD.ORG Wed Aug 19 07:59:34 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C9E410657F9 for ; Wed, 19 Aug 2009 07:59:34 +0000 (UTC) (envelope-from norgaard@locolomo.org) Received: from mail.locolomo.org (97.pool85-48-194.static.orange.es [85.48.194.97]) by mx1.freebsd.org (Postfix) with ESMTP id 35CD98FC69 for ; Wed, 19 Aug 2009 07:59:34 +0000 (UTC) Received: from beta.1-16-172-dyn.locolomo.org (beta.1-16-172-dyn.locolomo.org [172.16.1.127]) by mail.locolomo.org (Postfix) with ESMTPSA id C05D91C1A67; Wed, 19 Aug 2009 09:59:32 +0200 (CEST) Message-ID: <4A8BB0E4.2020806@locolomo.org> Date: Wed, 19 Aug 2009 09:59:32 +0200 From: Erik Norgaard User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Roland Smith References: <4A8A5887.1080304@locolomo.org> <20090818171528.GA35403@slackbox.xs4all.nl> In-Reply-To: <20090818171528.GA35403@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: questions@freebsd.org Subject: Re: Recovering files after a crash 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: Wed, 19 Aug 2009 07:59:34 -0000 Roland Smith wrote: > On Tue, Aug 18, 2009 at 09:30:15AM +0200, Erik Norgaard wrote: >> The problem is that I have no idea which files were affected. >> >> So, now some questions: >> >> First, how do I determine which files were corrupted? And how do I >> recover these files? > > From what you have shown it is impossible to tell. > > A short filesystem check (fsck -F) is run at boot time. If no major problems > are found, the complete filesystem check is done later in the background. > The result of that check will be visible in /var/log/messages. Thanks, I couldn't decipher these GEOM_LABEL messages, nice to know that I can stop worrying. But for future incidents, the second question remains: 1. How do I best protect my system from disk errors in case of a crash? I have a headless system with no spare head to attach and doing single-user blind-folded is further complicated by the fact that I'm not native to the US keyboard layout, so my top priority is that it boots. 2. When you have lost inodes or similar errors and stuff ends up in lost+found, how do you figure out what it was and recover the lost files? Is there a FBSD crash guide? Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org