Got this error in phase 6 when running xfs_repair 2.8.18 on ~1.2TB
partition over the weekend (it took around 60 hours to get to this
point :). On earlier versions xfs_repair aborted after ~15-20 hours with
"invalid inode type" error.
...
disconnected inode 4151889519, moving to lost+found
disconnected inode 4151889543, moving to lost+found
corrupt inode 4151889543 (btree). This is a bug.
Please report it to xfs@xxxxxxxxxxxx
cache_node_purge: refcount was 1, not zero (node=0x132650d0)
fatal error -- 117 - couldn't iget disconnected inode
I've got the full log (both stderr and stdout) and can put that
somewhere if needed. It's about 80MB uncompressed and around 7MB
gzipped. Running the xfs_repair without multithreading and with -v might
also be possible if that's going to help.
--
Jyrki Muukkonen
Futurice Oy
jyrki.muukkonen@xxxxxxxxxxx
+358 41 501 7322
|