[Top] [All Lists]

Re: Corrupted file system

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: Corrupted file system
From: Diane Trout <diane@xxxxxxxxxxx>
Date: Wed, 24 Sep 2014 13:38:27 -0700
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140924120840.1be78240@xxxxxxxxxxxxxxxxxxxx>
References: <5839367.DyqsVHbRuQ@myrada> <20140924120840.1be78240@xxxxxxxxxxxxxxxxxxxx>
User-agent: KMail/4.14 (Linux/3.14-2-amd64; KDE/4.14.1; x86_64; ; )
On Wednesday, September 24, 2014 12:08:40 Emmanuel Florac wrote:
> Le Tue, 23 Sep 2014 15:02:57 -0700
> Diane Trout <diane@xxxxxxxxxxx> écrivait:
> > I had a raid failure at work that ended up corrupting an xfs
> > filesystem the tail of the xfs_repair command looks like the below. I
> > was able to generate a metadata dump but is there a point to making
> > it available?
> > 
> > It does crash repeatedly at the same place
> Did you try the very latest xfs_repair?

I grabbed the one out of debian unstable (3.2.1), verified that it was your 
latest release and used that. I didn't try building the version in git.

It did get much further than version 3.1.7+b1 (debian stable)


Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
entry "lymphoblastoid" in dir ino 256 doesn't have a .. entry, will set it in 
ino 2051.
bad hash table for directory inode 256 (no data entry): rebuilding
rebuilding directory inode 256
7f70c79c8700: Badness in key lookup (length)
bp=(bno 0x3480, len 4096 bytes) key=(bno 0x3480, len 8192 bytes)
Metadata corruption detected at block 0x4000070/0x1000
xfs_da_do_buf(2): XFS_CORRUPTION_ERROR

fatal error -- can't read block 8388608 for directory inode 259, error 117

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