From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030397AbWGTW5O (ORCPT ); Thu, 20 Jul 2006 18:57:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030398AbWGTW5N (ORCPT ); Thu, 20 Jul 2006 18:57:13 -0400 Received: from lucidpixels.com ([66.45.37.187]:47752 "EHLO lucidpixels.com") by vger.kernel.org with ESMTP id S1030397AbWGTW5N (ORCPT ); Thu, 20 Jul 2006 18:57:13 -0400 Date: Thu, 20 Jul 2006 18:57:11 -0400 (EDT) From: Justin Piszcz X-X-Sender: jpiszcz@p34.internal.lan To: Nathan Scott cc: Chris Wedgwood , David Greaves , Kasper Sandberg , Torsten Landschoff , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, ml@magog.se, radsaq@gmail.com Subject: Re: FAQ updated (was Re: XFS breakage...) In-Reply-To: Message-ID: References: <20060718222941.GA3801@stargate.galaxy> <20060719085731.C1935136@wobbly.melbourne.sgi.com> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@wobbly.melbourne.sgi.com> <44BF8500.1010708@dgreaves.com> <20060720161121.GA26748@tuatara.stupidest.org> <20060721081452.B1990742@wobbly.melbourne.sgi.com> <20060721082448.C1990742@wobbly.melbourne.sgi.com> <20060721085230.F1990742@wobbly.melbourne.sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Erm, the xfs_repair -n only prints out what it needs to fix, I read somewhere that xfs_repair may make things worse? What is the 'correct' fix? On Thu, 20 Jul 2006, Justin Piszcz wrote: > Nasty! > > - agno = 37 > No modify flag set, skipping phase 5 > Phase 6 - check inode connectivity... > - traversing filesystem starting at / ... > free block 16777216 for directory inode 2684356622 bad nused > free block 16777216 for directory inode 2147485710 bad nused > - traversal finished ... > - traversing all unattached subtrees ... > - traversals finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify link counts... > No modify flag set, skipping filesystem flush and exiting. > p34:~# > > I applied the "one line fix" - I should be ok now? > > > > On Fri, 21 Jul 2006, Nathan Scott wrote: > >> On Thu, Jul 20, 2006 at 06:43:34PM -0400, Justin Piszcz wrote: >>> p34:~# xfs_check -v /dev/md3 >>> xfs_check: out of memory >>> p34:~# >>> >>> D'oh... >> >> xfs_repair -n is another option, it has a cheaper (memory wise, >> usually) checking algorithm. >> >>> As long as it mounted ok with the patched kernel, should one be ok? >> >> Not necessarily, no - mount will only read the root inode. >> >> cheers. >> >> -- >> Nathan >> - >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> >