Hi,
xfs/032 trigger xfs(v4/v5) corruption after run it several times:
[root@dhcp-13-149 xfstests-dev]# xfs_repair -n ~/xfs-032.img
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
sb_icount 64, counted 256
sb_ifree 61, counted 242
sb_fdblocks 1038280, counted 1035431
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
entry "d8" in shortform directory 1572896 references free inode 38
would have junked entry "d8" in directory inode 1572896
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
entry "d8" in shortform directory inode 1572896 points to free inode 38
would junk entry
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected dir inode 524320, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 1069090 nlinks from 2 to 1
would have reset inode 1572896 nlinks from 4 to 3
No modify flag set, skipping filesystem flush and exiting.
xfs/032 try to test different sectorsize and blocksize, I hit this bug
on different size everytime. V4 and V5 XFS all can trigger this bug.
Test on upstream linux 4.8-rc7, xfsprogs v4.8.0-rc1.
Even merged Eric's patch:
[PATCH] xfs_copy: Fix meta UUID handling on multiple copies
I still can reproduce this bug.
Thanks,
Zorro
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
