Re: 2.6.13.2 amd64: XFS: xlog_recover_process_data: bad clientid

[linux@xxxxxxxxxxx]

Just some more info... I ran xfs_repair -L, but then ran xfs_check, and it found
a lot of problems remaining, in particular a lot of:

link count mismatch for inode 514608143 (name ?), nlink 4, counted 3
link count mismatch for inode 514608156 (name ?), nlink 4, counted 3
link count mismatch for inode 514608168 (name ?), nlink 4, counted 3
link count mismatch for inode 514608172 (name ?), nlink 4, counted 3
link count mismatch for inode 514608180 (name ?), nlink 4, counted 3
link count mismatch for inode 514964512 (name ?), nlink 18, counted 17
link count mismatch for inode 514964526 (name ?), nlink 18, counted 17
link count mismatch for inode 514964528 (name ?), nlink 18, counted 17
link count mismatch for inode 514964531 (name ?), nlink 18, counted 17
link count mismatch for inode 514964532 (name ?), nlink 18, counted 17
link count mismatch for inode 514964533 (name ?), nlink 18, counted 17
link count mismatch for inode 514964535 (name ?), nlink 18, counted 17
link count mismatch for inode 514939937 (name ?), nlink 26, counted 25
link count mismatch for inode 515270699 (name ?), nlink 4, counted 3
link count mismatch for inode 515270700 (name ?), nlink 4, counted 3
link count mismatch for inode 515270701 (name ?), nlink 4, counted 3
link count mismatch for inode 515270703 (name ?), nlink 4, counted 3
link count mismatch for inode 515270704 (name ?), nlink 4, counted 3
link count mismatch for inode 514965508 (name ?), nlink 16, counted 15
link count mismatch for inode 514610208 (name ?), nlink 3, counted 4
link count mismatch for inode 514610209 (name ?), nlink 3, counted 4
link count mismatch for inode 523361301 (name ?), nlink 17, counted 16
link count mismatch for inode 523361312 (name ?), nlink 0, counted 2

So I'm running xfs_repair again, and it's not coming up clean.
Is this supposed to happen?  I didn't see a message about "re-run xfs_repair"
anywhere...

# xfs_repair /dev/md4
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
        - agno = 1
        - agno = 2
        - agno = 3
imap claims a free inode 129571903 is in use, correcting imap and clearing inode
cleared inode 129571903
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
(in progress as I write this)