public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Roman Hlynovskiy <roman.hlynovskiy@gmail.com>, xfs@oss.sgi.com
Subject: Re: xfs_repair
Date: Thu, 14 Nov 2013 12:04:09 -0600	[thread overview]
Message-ID: <52851099.2050707@sandeen.net> (raw)
In-Reply-To: <CAD5ewrp2X_CyffUt6KUCd9bRE-BJ9_Q2OmZuzPv+d1VBf09OyA@mail.gmail.com>

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@oss.sgi.com <mailto:xfs@oss.sgi.com>.
> 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?

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-11-14 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 17:51 xfs_repair Roman Hlynovskiy
2013-11-14 18:04 ` Eric Sandeen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19 19:27 xfs_repair Ashley Oviatt

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=52851099.2050707@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=roman.hlynovskiy@gmail.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