https://bugzilla.kernel.org/show_bug.cgi?id=201823 --- Comment #7 from Eric Sandeen (sandeen@xxxxxxxxxxx) --- So, the frag command emits these warnings under a debug build: # xfs_db -c frag -r /dev/sde1 bad inode magic/vsn daddr 8366784 #0 (magic=5844) Metadata corruption detected at 0x4289c3, xfs_inode block 0x7faac0/0x8000 bad inode magic/vsn daddr 34386688 #0 (magic=0) Metadata corruption detected at 0x4289c3, xfs_inode block 0x20cb300/0x8000 bad inode magic/vsn daddr 36967232 #0 (magic=0) Metadata corruption detected at 0x4289c3, xfs_inode block 0x2341340/0x8000 If we look at each of those blocks (daddr) after a blockget -n, xfs_db> daddr 8366784 xfs_db> blockuse block 1045848 (0/1045848) type dir inode 8366719 xfs_db> daddr 34386688 xfs_db> blockuse block 5292640 (1/1098336) type free2 xfs_db> daddr 36967232 xfs_db> blockuse block 5615208 (1/1420904) type data inode 44934228 The "inode" corruption it's finding isn't actually in inode blocks... -- You are receiving this mail because: You are watching the assignee of the bug.
