From: Eric Sandeen <sandeen@sandeen.net>
To: Nitin Arora <nitin.arora.del@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Wed, 24 Jun 2009 08:23:42 -0500 [thread overview]
Message-ID: <4A4228DE.6040104@sandeen.net> (raw)
In-Reply-To: <409bd82b0906240456m44d95343vdd62f0c3ad7bcdac@mail.gmail.com>
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@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-24 13:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:56 XFS internal error XFS_WANT_CORRUPTED_GOTO Nitin Arora
2009-06-24 12:40 ` Michael Monnerie
2009-06-24 13:18 ` Nitin Arora
2009-06-24 13:23 ` Eric Sandeen [this message]
2009-06-25 10:06 ` Nitin Arora
2009-06-25 13:45 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2011-07-22 4:52 Amit Sahrawat
2011-07-22 5:23 ` Amit Sahrawat
2011-07-22 6:59 ` Amit Sahrawat
2011-07-22 8:34 ` Dave Chinner
2011-07-22 10:33 ` Amit Sahrawat
2011-07-24 1:34 ` Dave Chinner
2011-07-25 5:26 ` Amit Sahrawat
2011-07-26 3:33 ` Dave Chinner
2011-07-26 9:47 ` Ajeet Yadav
2011-07-26 10:27 ` Christoph Hellwig
2011-07-27 4:33 ` Amit Sahrawat
2008-05-29 13:48 Louis-David Mitterrand
2007-04-19 13:28 Burbidge, Simon A
2007-04-19 14:18 ` David Chinner
2007-04-19 14:36 ` Burbidge, Simon A
2007-04-19 22:10 ` David Chinner
2006-08-10 16:42 cache_purge: shake on cache 0x5880a0 left 8 nodes!? Paul Slootman
2006-08-11 1:30 ` Barry Naujok
2006-08-11 9:02 ` Paul Slootman
2006-08-12 9:14 ` Paul Slootman
2006-08-14 14:17 ` XFS internal error XFS_WANT_CORRUPTED_GOTO Paul Slootman
2006-08-15 11:54 ` Paul Slootman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4228DE.6040104@sandeen.net \
--to=sandeen@sandeen.net \
--cc=nitin.arora.del@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox