Re: XFS: 2.6.26-rc6 link count mismatch for inode

[Marco Berizzi]

Dave Chinner wrote:

> Yeah, it sounds like the I/O subsystem hung somewhere. Without
> details I can't say what went wrong. If it happens again doing
> this:
>
> # echo w > /proc/sysrq-trigger

ok, thanks for the tip.

> To get a dump of all the blocked processes on the console. That
> may contain enough info to tell us what the problem is.
>
> Sure, go ahead and fix it up.

right now, I'm not able to reproduce the bug anymore.
Thanks for the support Dave.
BTW, this is the xfs_repair output:

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
b77dcb90: Badness in key lookup (length)
bp=(bno 5280, len 16384 bytes) key=(bno 5280, len 8192 bytes)
imap claims a free inode 70353 is in use, correcting imap and clearing
inode
cleared inode 70353
imap claims a free inode 98831 is in use, correcting imap and clearing
inode
cleared inode 98831
b5659b90: Badness in key lookup (length)
bp=(bno 5655872, len 16384 bytes) key=(bno 5655872, len 8192 bytes)
        - agno = 1
b4bffb90: Badness in key lookup (length)
bp=(bno 10238304, len 16384 bytes) key=(bno 10238304, len 8192 bytes)
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
imap claims a free inode 85450805 is in use, correcting imap and
clearing inode
cleared inode 85450805
imap claims a free inode 85450806 is in use, correcting imap and
clearing inode
cleared inode 85450806
imap claims a free inode 85450807 is in use, correcting imap and
clearing inode
cleared inode 85450807
imap claims a free inode 85450808 is in use, correcting imap and
clearing inode
cleared inode 85450808
imap claims a free inode 85450809 is in use, correcting imap and
clearing inode
cleared inode 85450809
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - 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
entry ".deps" in shortform directory 19893187 references free inode
70353
junking entry ".deps" in directory inode 19893187
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
entry "CVS" in shortform directory 67179727 references free inode
85450805
junking entry "CVS" in directory inode 67179727
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 10573, moving to lost+found
disconnected inode 18086534, moving to lost+found
disconnected inode 18086535, moving to lost+found
disconnected inode 34026152, moving to lost+found
Phase 7 - verify and correct link counts...
resetting inode 19893187 nlinks from 3 to 2
resetting inode 67179727 nlinks from 3 to 2
done


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/