xfs
[Top] [All Lists]

Re: xfs_repair fatal error in phase 6

To: Tupshin Harper <tupshin@xxxxxxxxx>
Subject: Re: xfs_repair fatal error in phase 6
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Mon, 2 Aug 2004 09:46:30 -0500 (CDT)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <2bd6037a04080204201903e8fe@xxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Mon, 2 Aug 2004, Tupshin Harper wrote:

> I have an xfs partition that xfs_repair refuses to fix. It always dies
> with the following:
> 
> Phase 6 - check inode connectivity...
>         - resetting contents of realtime bitmap and summary inodes
>         - ensuring existence of lost+found directory
>         - traversing filesystem starting at / ...
> rebuilding directory inode 128
> empty data block 9 in directory inode 54540222: junking block
> 
> fatal error -- can't read block 8388608 for directory inode 54540222

maybe stracing xfs_repair would tell us what the real error was, although
the output will be quite large - the option "-etrace=read" might catch
only the read calls, and see if one fails.  Or, maybe some creative
printf debugging in phase6.c to find the underlying error.

> I have tried dd'ing it to a file on another filesystem, and I get the
> same results. I've tried running it a few times, and no change. Mount
> doesn't recognize it.

What does mount say?

-Eric


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