From: Diane Trout <diane@caltech.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Corrupted file system
Date: Wed, 24 Sep 2014 13:38:27 -0700 [thread overview]
Message-ID: <705802842.F0QjhfVGQR@myrada> (raw)
In-Reply-To: <20140924120840.1be78240@harpe.intellique.com>
On Wednesday, September 24, 2014 12:08:40 Emmanuel Florac wrote:
> Le Tue, 23 Sep 2014 15:02:57 -0700
>
> Diane Trout <diane@caltech.edu> é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)
Diane
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-24 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 22:02 Corrupted file system Diane Trout
2014-09-23 22:12 ` Sean Caron
2014-09-23 22:29 ` Diane Trout
2014-09-23 23:12 ` Eric Sandeen
2014-09-24 10:08 ` Emmanuel Florac
2014-09-24 20:38 ` Diane Trout [this message]
2014-09-24 20:57 ` Eric Sandeen
2014-09-25 0:25 ` Diane Trout
2014-09-25 0:50 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=705802842.F0QjhfVGQR@myrada \
--to=diane@caltech.edu \
--cc=eflorac@intellique.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox