From: Emmanuel Florac <eflorac@intellique.com>
To: Christophe Baegert <c.baegert@lixium.fr>
Cc: xfs@oss.sgi.com
Subject: Re: bug during xfs_repair -L on 1TB of strategic data
Date: Thu, 10 Sep 2015 13:46:57 +0200 [thread overview]
Message-ID: <20150910134657.4cac43ec@harpe.intellique.com> (raw)
In-Reply-To: <55F116A4.5080106@lixium.fr>
Le Thu, 10 Sep 2015 07:35:32 +0200
Christophe Baegert <c.baegert@lixium.fr> écrivait:
> Hi,
>
> I see this message when repairing an XFS partition of 1TB of
> strategic data (on Debian Wheezy)
>
> What can I do ?
>
> corrupt dinode 1933282003, 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.
> cache_node_purge: refcount was 1, not zero (node=0x7f7c55b35220)
>
> fatal error -- 117 - couldn't iget disconnected inode
>
Don't use the ancient version of xfs_repair that comes with Wheezy, use
a more recent version, at least a 3.2.x release.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-10 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 5:35 bug during xfs_repair -L on 1TB of strategic data Christophe Baegert
2015-09-10 11:46 ` Emmanuel Florac [this message]
2015-09-10 11:53 ` Emmanuel Florac
2015-09-10 14:10 ` Christophe Baegert
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=20150910134657.4cac43ec@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=c.baegert@lixium.fr \
--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