From owner-freebsd-questions@FreeBSD.ORG Thu Apr 19 00:10:19 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 772C416A402 for ; Thu, 19 Apr 2007 00:10:19 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from pizzabox.cyberleo.net (alpha.cyberleo.net [198.145.45.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3D75513C43E for ; Thu, 19 Apr 2007 00:10:19 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: (qmail 61812 invoked from network); 19 Apr 2007 00:10:16 -0000 Received: from adsl-75-3-93-223.dsl.chcgil.sbcglobal.net (HELO ?172.16.44.14?) (cyberleo@cyberleo.net@75.3.93.223) by alpha.cyberleo.net with ESMTPA; 19 Apr 2007 00:10:16 -0000 Message-ID: <4626B36C.5030506@cyberleo.net> Date: Wed, 18 Apr 2007 19:09:57 -0500 From: CyberLeo Kitsana User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Roland Smith , FreeBSD Questions References: <4623843B.40006@cyberleo.net> <20070416170825.GA91459@slackbox.xs4all.nl> <462449C2.9000302@cyberleo.net> <20070416222437.GA1924@slackbox.xs4all.nl> <46268919.1080301@cyberleo.net> <20070418213717.GB74368@slackbox.xs4all.nl> In-Reply-To: <20070418213717.GB74368@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: dump/restore corrupted filesystems 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: Thu, 19 Apr 2007 00:10:19 -0000 Roland Smith wrote: >> --8<-- >> ** Phase 2 - Check Pathnames >> DIRECTORY CORRUPTED I=93409222 OWNER=1002 MODE=40755 >> SIZE=512 MTIME=Feb 10 00:49 2007 >> DIR=? >> >> UNEXPECTED SOFT UPDATE INCONSISTENCY > > Did these problems start after a crash? It's possible, but I cannot be absolutely certain. The machine is supposed to start itself up and shut itself down every day, running a total of about 4 hours a day, during the span when all other machines dump their backups. The only reason I noticed this failure was because it didn't power down one day. Investigation revealed that FSCK had failed and dropped to single user, with errors seen in the log. > >> SALVAGE? no > > What happens if you tell it to try and salvage? This was a dry-run to get the error log. When I actually tried to repair the filesystem, fsck aborts shortly after, complaining that it cannot fix the filesystem, and cannot continue. Hence the current path of removing everything and re-newfs'ing. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/