From owner-freebsd-questions@FreeBSD.ORG Thu Apr 19 00:05:02 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 603E316A409 for ; Thu, 19 Apr 2007 00:05:02 +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 1E7CE13C46E for ; Thu, 19 Apr 2007 00:03:26 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: (qmail 61610 invoked from network); 19 Apr 2007 00:03:23 -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:03:23 -0000 Message-ID: <4626B1CE.4080904@cyberleo.net> Date: Wed, 18 Apr 2007 19:03:03 -0500 From: CyberLeo Kitsana User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Jerry McAllister , 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> <20070418212243.GA59177@gizmo.acns.msu.edu> In-Reply-To: <20070418212243.GA59177@gizmo.acns.msu.edu> Content-Type: text/plain; charset=us-ascii 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:05:02 -0000 Jerry McAllister wrote: >> Smart says that the drives are fine, as does the manufacturer's disk >> fitness tools. All the files that are readable contain correct data, but >> the files that are corrupt are totally not readable, and cannot even be >> removed manually: > > Given that, I would try to make a dump(8) of it. If dump dies on > a particular file, try to exclude that file from the dump either by > rm-ing it or setting a nodump flag and try again. You may not > actually be able to do the rm or nodump flag though if you cannot > mount it with write permission. You might be able to force it > mounted without doing the fsck in single user. > > Note that tar allows you to specify exclusions. I usually don't > suggest using tar for mass moves because it has weaknesses with > hard links and might also not transfer flags and permissions > correctly. But, if tar is what it takes, then use it. Force-mounting the filesystem works just fine. It's when I try to modify any munged file that it panics the box, with ufs_dirbad or somesuch. I have been using rsync to recover readable data, which handles hard-links, permissions, sparse files, and et cetera. I figure it's best, as that's what is used to drop the differential backups onto the box in the first place. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/