Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 09 Sep 2004 08:37:02 -0700 (PDT) Received: from mail.linux-sxs.org (mail.linux-sxs.org [207.218.156.196]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i89FavdP000899 for ; Thu, 9 Sep 2004 08:36:57 -0700 Received: from mail.linux-sxs.org (localhost [127.0.0.1]) by mail.linux-sxs.org (8.12.11/8.12.11/Debian-5) with ESMTP id i89FRN4B017795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2004 10:27:24 -0500 Received: from localhost (netllama@localhost) by mail.linux-sxs.org (8.12.11/8.12.11/Debian-5) with ESMTP id i89FRM3M017792; Thu, 9 Sep 2004 10:27:23 -0500 X-Authentication-Warning: mail.linux-sxs.org: netllama owned process doing -bs Date: Thu, 9 Sep 2004 10:27:22 -0500 (EST) From: Net Llama! To: Anastas Giokov cc: linux-xfs@oss.sgi.com Subject: Re: Problem repairing XFS In-Reply-To: <20040909090323.DE1791BCFC@xprdmailfe23.nwk.excite.com> Message-ID: References: <20040909090323.DE1791BCFC@xprdmailfe23.nwk.excite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: milter-sender/0.60.818 (localhost [127.0.0.1]); Thu, 09 Sep 2004 10:27:24 -0500 X-archive-position: 4084 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs I believe that you need to purge the contents of lost+found after running xfs_repair, or it will keep trying to repair the same thing over & over again. So purge (or at least move) the contents of lost+found, then run xfs_repair again. On Thu, 9 Sep 2004, Anastas Giokov wrote: > > Hi! > > After a disk problem (bad sectors) I have the following problem: > > Using xfs_repair on the device I receive the following message: > > corrupt inode XXXXX (btree). Unmount and run xfs_repair. > fatal error -- 990 - couldn't iget disconnected inode > > The device is unmounted at this point and re-running xfs_repair dives the same output. The resulting fs is mountable, but part of it is not recovered. > > Is there a way to "skip" the corrupt inode, so the repair can finish, even losing some data? > > Anastas > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com