xfs_repair fails with corrupt dinode 17491441757, extent total = 1, nblocks = 0. This is a bug.
Arkadiusz Miśkiewicz
arekm at maven.pl
Mon Oct 31 05:56:20 CDT 2011
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 at 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/
More information about the xfs
mailing list