Corrupted file system

[Sean Caron]

Hi Diane,

Probably best to reformat and restore from a backup at this point. I'm
notorious for my views on xfs_repair but most folks here will agree that in
the case where there has been a major underlying array failure, there is
not much it can do to help. Better to just mount ro,noreplaylog and get
what you can in these sorts of scenarios, IMO.

"Did you try the latest copy of xfs_repair"? Sometimes it will get further
or not crash, but it likely will still maul whatever's left of your
filesystem.

Best of luck,

Sean


On Tue, Sep 23, 2014 at 6:02 PM, Diane Trout <diane at caltech.edu> wrote:

> 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 at oss.sgi.com.
> cache_node_purge: refcount was 1, not zero (node=0x7f369883e6f0)
>
> fatal error -- 117 - couldn't iget disconnected inode
>
>
> _______________________________________________
> xfs mailing list
> xfs at oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20140923/428bbf08/attachment.html>