[Top] [All Lists]

Re: xfs_repair

To: Roman Hlynovskiy <roman.hlynovskiy@xxxxxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: xfs_repair
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 14 Nov 2013 12:04:09 -0600
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAD5ewrp2X_CyffUt6KUCd9bRE-BJ9_Q2OmZuzPv+d1VBf09OyA@xxxxxxxxxxxxxx>
References: <CAD5ewrp2X_CyffUt6KUCd9bRE-BJ9_Q2OmZuzPv+d1VBf09OyA@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
On 11/14/13, 11:51 AM, Roman Hlynovskiy wrote:
> hello, after a server crush we are trying to get back access to data on 
> another server.
> out setup is the following:
> 4 disks in md-array, lvm over it and xfs
> xfs_check just stops with 'out of memory error'

xfs_check is deprecated & doesn't scale; don't bother.
Use xfs_repair -n if you want a readonly check.

> xfs_repair after a long list of complains says:
> corrupt dinode 2473604576, extent total = 1, nblocks = 0.  This is a bug.
> Please capture the filesystem metadata with xfs_metadump and
> report it to xfs@xxxxxxxxxxx <mailto:xfs@xxxxxxxxxxx>.
> cache_node_purge: refcount was 1, not zero (node=0xb43ab688)
> fatal error -- 117 - couldn't iget disconnected inode

Are you using latest xfsprogs?

> I captured this metadata file, but it's 2GB size.
> is there a chance to fix the fs?

how big is it if you compress it?


<Prev in Thread] Current Thread [Next in Thread>
  • xfs_repair, Roman Hlynovskiy
    • Re: xfs_repair, Eric Sandeen <=