|
Hello,
I'm a college student and was running some experiment with xfs checkers and I encountered a bug in xfs_repair. The repair log directs me to report it with filesystem metadata to this email.
The bug occurred at phase 6:
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
entry "2" in dir ino 128 doesn't have a .. entry, will set it in ino 4194432.
entry "F0.xtn" in shortform directory inode 128 points to free inode 132
entry "F1.nba" in shortform directory inode 128 points to free inode 133
entry "F8.jpg" in shortform directory inode 128 points to free inode 137
entry "F10.bqp" in shortform directory inode 128 points to free inode 138
setting .. in sf dir inode 4194432 to 128
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 141, moving to lost+found
disconnected inode 142, moving to lost+found
disconnected inode 145, moving to lost+found
disconnected inode 149, moving to lost+found
corrupt dinode 149, extent total = 1, nblocks = 0. This is a bug.
Please capture the filesystem metadata with xfs_metadump and
report it to xfs@xxxxxxxxxxxx
cache_node_purge: refcount was 1, not zero (node=0x182bfc0)
fatal error -- 117 - couldn't iget disconnected inode
I hope this helps.
Yanlei Zhao
Undergraduate Student at UW-Madison
Computer Science And Management of Information Systems
yanleizhao@xxxxxxx
|
