From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug.
Date: Mon, 31 Oct 2011 11:56:20 +0100 [thread overview]
Message-ID: <201110311156.20421.arekm@maven.pl> (raw)
xfs_repair version 3.1.6
disconnected inode 17491441754, moving to lost+found
disconnected inode 17491441755, moving to lost+found
disconnected inode 17491441756, moving to lost+found
disconnected inode 17491441757, moving to lost+found
corrupt dinode 17491441757, 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=0x21450c90)
fatal error -- 117 - couldn't iget disconnected inode
30GB metadump image, 6.1GB compressed of ~7TB real partition
http://ixion.pld-linux.org/~arekm/lv_storage1.metadump.xz
You need ~8-12GB of memory for xfs_repair on this.
I can also provide ssh access to the system with this image and all needed
stuff, so you don't need to download it or waste own resources.
In meantime I'll probably make ugly hack by making "couldn't iget disconnected
inode" non fatal, so repair will be able to finish.
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-10-31 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 10:56 Arkadiusz Miśkiewicz [this message]
2011-11-03 10:26 ` xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug Christoph Hellwig
2011-11-03 10:40 ` Arkadiusz Miśkiewicz
2011-11-03 10:48 ` Christoph Hellwig
2011-11-03 10:57 ` Arkadiusz Miśkiewicz
2011-11-03 11:03 ` Christoph Hellwig
2011-11-03 11:54 ` Christoph Hellwig
2011-11-03 20:02 ` Arkadiusz Miśkiewicz
2011-11-03 20:21 ` Arkadiusz Miśkiewicz
2011-11-06 22:19 ` Arkadiusz Miśkiewicz
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=201110311156.20421.arekm@maven.pl \
--to=arekm@maven.pl \
--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