xfs
[Top] [All Lists]

Re: FAQ updated (was Re: XFS breakage...)

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: FAQ updated (was Re: XFS breakage...)
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 21 Jul 2006 09:00:15 +1000
Cc: Chris Wedgwood <cw@xxxxxxxx>, David Greaves <david@xxxxxxxxxxxx>, Kasper Sandberg <lkml@xxxxxxxxxxx>, Torsten Landschoff <torsten@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, ml@xxxxxxxx, radsaq@xxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0607201855270.2652@p34.internal.lan>; from jpiszcz@lucidpixels.com on Thu, Jul 20, 2006 at 06:55:51PM -0400
References: <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> <Pine.LNX.4.64.0607201817450.23697@p34.internal.lan> <20060721082448.C1990742@wobbly.melbourne.sgi.com> <Pine.LNX.4.64.0607201843020.2619@p34.internal.lan> <20060721085230.F1990742@wobbly.melbourne.sgi.com> <Pine.LNX.4.64.0607201855270.2652@p34.internal.lan>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Thu, Jul 20, 2006 at 06:55:51PM -0400, Justin Piszcz wrote:
> 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 ...
> ...
> I applied the "one line fix" - I should be ok now?

You have two corrupt directory inodes (caused by this bug, that
is exactly the signature I'd expect - it was a nused field that
was affected by the dodgey endian change).  The two inodes need
to be fixed - consult the FAQ for details.

Once fixed, and with a patched kernel, you're set.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>