xfs
[Top] [All Lists]

Corrupted file system

To: xfs@xxxxxxxxxxx
Subject: Corrupted file system
From: Diane Trout <diane@xxxxxxxxxxx>
Date: Tue, 23 Sep 2014 15:02:57 -0700
Delivered-to: xfs@xxxxxxxxxxx
User-agent: KMail/4.14 (Linux/3.14-2-amd64; KDE/4.14.0; x86_64; ; )
Hi,

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

(I'm not subscribed to the list, so could you reply directly as well?)

disconnected inode 15276, moving to lost+found
disconnected inode 15277, moving to lost+found
disconnected inode 15278, moving to lost+found
disconnected inode 15279, moving to lost+found
disconnected inode 15280, moving to lost+found
disconnected inode 15281, moving to lost+found
disconnected inode 15282, moving to lost+found
disconnected inode 15283, moving to lost+found
disconnected inode 15284, moving to lost+found
disconnected inode 15286, moving to lost+found
disconnected inode 15287, moving to lost+found
disconnected inode 15288, moving to lost+found
disconnected inode 15289, moving to lost+found
disconnected inode 15290, moving to lost+found
disconnected inode 15291, moving to lost+found
disconnected inode 15292, moving to lost+found
disconnected inode 15293, moving to lost+found
disconnected inode 15294, moving to lost+found
disconnected inode 15295, moving to lost+found
disconnected inode 15360, moving to lost+found
corrupt dinode 15360, extent total = 1, nblocks = 0.  This is a bug.
Please capture the filesystem metadata with xfs_metadump and
report it to xfs@xxxxxxxxxxxx
cache_node_purge: refcount was 1, not zero (node=0x7f369883e6f0)

fatal error -- 117 - couldn't iget disconnected inode


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