Hi,<br>
<br>
I have tried the patch provided in that link but unfortunately it doesn't solve that problem.<br>
I have run xfs_repair on the corrupted partition and got the following output.<br>
<i><br>
Phase 1 - find and verify superblock...<br>
Phase 2 - using internal log<br>
- zero log...<br>
- scan filesystem freespace and inode maps...<br>
- found root inode chunk<br>
Phase 3 - for each AG...<br>
- scan and clear agi unlinked lists...<br>
- process known inodes and perform inode discovery...<br>
- agno = 0<br>
data fork in regular inode 159 claims used block 667542<br>
bad data fork in inode 159<br>
cleared inode 159<br>
data fork in regular inode 6228245 claims used block 667569<br>
bad data fork in inode 6228245<br>
cleared inode 6228245<br>
- agno = 1<br>
- agno = 2<br>
- agno = 3<br>
- process newly discovered inodes...<br>
Phase 4 - check for duplicate blocks...<br>
- setting up duplicate extent list...<br>
- check for inodes claiming duplicate blocks...<br>
- agno = 0<br>
entry "Masoom7.avi" at block 0 offset 1824 in directory inode 128 references free inode 159<br>
clearing inode number in entry at offset 1824...<br>
entry "Gandhi4.avi" at block 2 offset 664 in directory inode 128 references free inode 6228245<br>
clearing inode number in entry at offset 664...<br>
data fork in ino 133 claims dup extent, off - 0, start - 667542, cnt 333765<br>
bad data fork in inode 133<br>
cleared inode 133<br>
- agno = 1<br>
- agno = 2<br>
- agno = 3<br>
Phase 5 - rebuild AG headers and trees...<br>
- reset superblock...<br>
Phase 6 - check inode connectivity...<br>
- resetting contents of realtime bitmap and summary inodes<br>
- traversing filesystem ...<br>
entry "3.avi" in directory inode 128 points to free inode 133<br>
bad hash table for directory inode 128 (no data entry): rebuilding<br>
rebuilding directory inode 128<br>
- traversal finished ...<br>
- moving disconnected inodes to lost+found ...<br>
Phase 7 - verify and correct link counts...<br>
done<br>
</i><br>
<br>
Please let me know in case any other fix is available.<br>
<br>
Thanks <br>
:)<br><br><br><br><div class="gmail_quote">
On Wed, Jun 24, 2009 at 6:53 PM, Eric Sandeen <span dir="ltr"><<a href="mailto:sandeen@sandeen.net" target="_blank">sandeen@sandeen.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Nitin Arora wrote:<br>
> Hi,<br>
><br>
> I am using linux kernel 2.6.18 with XFS support.<br>
> I have formatted USB hard drive with XFS. When I try to copy<br>
> (i.e. cp 1.avi 2.avi) a big file (size : 1.3 GB) from one<br>
> location to another on the same hard drive It corrupts the<br>
> hard drive with the following back trace.<br>
<br>
</div><a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=71a8c87fb300b601eacf7a86cc6c6322fe827bfd" target="_blank">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=71a8c87fb300b601eacf7a86cc6c6322fe827bfd</a><br>
<br>
fixed a longstanding in-memory extent corruption, but that's my only<br>
guess at this point. As Michael said, 2.6.18 is getting very old, and<br>
unless you have a vendor supporting it (in which case you should<br>
probably ask them...) you will probably have trouble getting help with<br>
problems in it, I'm afraid, because it is several years old.<br>
<br>
(however, if this is mission critical we could point you to people who<br>
can do contract work to help)<br>
<br>
-Eric<br>
<br>
> /XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1588 of file<br>
<div>> fs/xfs/xfs_alloc.c. Caller 0xc0131a70<br>
> [<c0024618>] (dump_stack+0x0/0x14) from [<c0158ae0>]<br>
> (xfs_error_report+0x54/0x64)<br>
> [<c0158a8c>] (xfs_error_report+0x0/0x64) from [<c012fcf0>]<br>
> (xfs_free_ag_extent+0xec/0x768)<br>
> [<c012fc04>] (xfs_free_ag_extent+0x0/0x768) from [<c0131a70>]<br>
> (xfs_free_extent+0xa0/0xbc)<br>
> [<c01319d0>] (xfs_free_extent+0x0/0xbc) from [<c0140dd0>]<br>
> (xfs_bmap_finish+0xec/0x184)<br>
> r7 = CBF826F8 r6 = 00000000 r5 = 000357B8 r4 = CB7CF708<br>
> [<c0140ce4>] (xfs_bmap_finish+0x0/0x184) from [<c01633b8>]<br>
> (xfs_itruncate_finish+0x1c8/0x2fc)<br>
> [<c01631f0>] (xfs_itruncate_finish+0x0/0x2fc) from [<c01814b0>]<br>
> (xfs_inactive+0x278/0x89c)/<br>
><br>
> I have searched on the internet about and found that many people are<br>
> facing the same problem,<br>
> But no solution is found.<br>
><br>
> Can you guide me Or answer the following questions.<br>
> *<br>
> 1. Is there any patch available which solves this problem.<br>
> 2. If there is no patch available so far then can you give me<br>
> some pointers which will help in solving the problem.*<br>
><br>
> Thanks in advance<br>
><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> xfs mailing list<br>
> <a href="mailto:xfs@oss.sgi.com" target="_blank">xfs@oss.sgi.com</a><br>
> <a href="http://oss.sgi.com/mailman/listinfo/xfs" target="_blank">http://oss.sgi.com/mailman/listinfo/xfs</a><br>
<br>
</blockquote></div><br>