Re: XFS internal error XFS_WANT_CORRUPTED_GOTO

[Eric Sandeen <sandeen@sandeen.net>]

Nitin Arora wrote:
> Hi,
> 
> I have tried the patch provided in that link but unfortunately it
> doesn't solve that problem.
> I have run xfs_repair on the corrupted partition and got the following
> output.

Ah, well, if you had actual on-disk corruption, that's likely the reason
for the "internal error" - and finding out how it got corrupted after
the fact will be nigh impossible, I'm afraid.

-Eric

> 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
> data fork in regular inode 159 claims used block 667542
> bad data fork in inode 159
> cleared inode 159
> data fork in regular inode 6228245 claims used block 667569
> bad data fork in inode 6228245
> cleared inode 6228245
>         - 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
> entry "Masoom7.avi" at block 0 offset 1824 in directory inode 128
> references free inode 159
>         clearing inode number in entry at offset 1824...
> entry "Gandhi4.avi" at block 2 offset 664 in directory inode 128
> references free inode 6228245
>         clearing inode number in entry at offset 664...
> data fork in ino 133 claims dup extent, off - 0, start - 667542, cnt 333765
> bad data fork in inode 133
> cleared inode 133
>         - agno = 1
>         - agno = 2
>         - agno = 3
> Phase 5 - rebuild AG headers and trees...
>         - reset superblock...
> Phase 6 - check inode connectivity...
>         - resetting contents of realtime bitmap and summary inodes
>         - traversing filesystem ...
> entry "3.avi" in directory inode 128 points to free inode 133
> bad hash table for directory inode 128 (no data entry): rebuilding
> rebuilding directory inode 128
>         - traversal finished ...
>         - moving disconnected inodes to lost+found ...
> Phase 7 - verify and correct link counts...
> done

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs