xfs
[Top] [All Lists]

Re: XFS internal error XFS_WANT_CORRUPTED_GOTO

To: xfs@xxxxxxxxxxx
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
From: Nitin Arora <nitin.arora.del@xxxxxxxxx>
Date: Thu, 25 Jun 2009 15:36:23 +0530
Cc: xfs-masters@xxxxxxxxxxx, felixb@xxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=qgrGwm9ZAPDYXle/8rG74Krxk8+NfQrcoHjNvXDeSKs=; b=E8W13YHsJcfSYlHt5divvOR6uAkwpDZthkDF3Io71xrpso/GXNptyqS4+2/CuRzzPC Z5E/p1vhVyb2g0liYq6AAIyysL6xuTDHbfxyG6/fMkRU+O9IiQBj4E/Em6wp/1m3Vv3d wyCG7Rc2dFIYYUMJHgps8vSZeA2c0wmYZXxCY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=v7dEoPQTGGQ9zwUTNjyvs9cek5ptRDb50I882zjkfVh74+2I90RfPuEPs7pyyfPyzK ucM9E8lmbCkZC23zvDjH2YKujhLhkOiO3w5nkNBfMuRGvHJ7V72wuFmn8bRoQrQQfBD7 irAqKaOwF7eRl9Z/eGqdAs/bdsMdfYIdnAhFY=
In-reply-to: <4A4228DE.6040104@xxxxxxxxxxx>
References: <409bd82b0906240456m44d95343vdd62f0c3ad7bcdac@xxxxxxxxxxxxxx> <4A4228DE.6040104@xxxxxxxxxxx>
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.

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


Please let me know in case any other fix is available.

Thanks
:)



On Wed, Jun 24, 2009 at 6:53 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
Nitin Arora wrote:
> Hi,
>
> I am using linux kernel 2.6.18 with XFS support.
> I have formatted USB hard drive with XFS. When I try to copy
> (i.e. cp 1.avi 2.avi) a big file (size : 1.3 GB) from one
> location to another on the same hard drive It corrupts the
> hard drive with the following back trace.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=71a8c87fb300b601eacf7a86cc6c6322fe827bfd

fixed a longstanding in-memory extent corruption, but that's my only
guess at this point.  As Michael said, 2.6.18 is getting very old, and
unless you have a vendor supporting it (in which case you should
probably ask them...) you will probably have trouble getting help with
problems in it, I'm afraid, because it is several years old.

(however, if this is mission critical we could point you to people who
can do contract work to help)

-Eric

> /XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1588 of file
> fs/xfs/xfs_alloc.c.  Caller 0xc0131a70
> [<c0024618>] (dump_stack+0x0/0x14) from [<c0158ae0>]
> (xfs_error_report+0x54/0x64)
> [<c0158a8c>] (xfs_error_report+0x0/0x64) from [<c012fcf0>]
> (xfs_free_ag_extent+0xec/0x768)
> [<c012fc04>] (xfs_free_ag_extent+0x0/0x768) from [<c0131a70>]
> (xfs_free_extent+0xa0/0xbc)
> [<c01319d0>] (xfs_free_extent+0x0/0xbc) from [<c0140dd0>]
> (xfs_bmap_finish+0xec/0x184)
> r7 = CBF826F8  r6 = 00000000  r5 = 000357B8  r4 = CB7CF708
> [<c0140ce4>] (xfs_bmap_finish+0x0/0x184) from [<c01633b8>]
> (xfs_itruncate_finish+0x1c8/0x2fc)
> [<c01631f0>] (xfs_itruncate_finish+0x0/0x2fc) from [<c01814b0>]
> (xfs_inactive+0x278/0x89c)/
>
> I have searched on the internet about and found that many people are
> facing the same problem,
> But no solution is found.
>
> Can you guide me Or answer the following questions.
> *
> 1. Is there any patch available which solves this problem.
> 2. If there is no patch available so far then can you give me
>   some pointers which will help in solving the problem.*
>
> Thanks in advance
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs


<Prev in Thread] Current Thread [Next in Thread>