From: Dave Chinner <david@fromorbit.com>
To: Shaun Adolphson <shaun@adolphson.net>
Cc: xfs@oss.sgi.com
Subject: Re: CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO)
Date: Wed, 7 Jul 2010 09:18:57 +1000 [thread overview]
Message-ID: <20100706231856.GC25018@dastard> (raw)
In-Reply-To: <AANLkTimKKEvfJx6EQZeQF_HnlBLj6B8Kjfy6jUHGPnz5@mail.gmail.com>
On Tue, Jul 06, 2010 at 08:57:45PM +1000, Shaun Adolphson wrote:
> Hi,
>
> We have been able to repeatably produce xfs internal errors
> (XFS_WANT_CORRUPTED_GOTO) on one of our fileservers. We are attempting
> to locally copy a 248Gig file off a usb drive formated as NTFS to the
> xfs drive. The copy gets about 96% of the way through and we get the
> following messages:
>
> Jun 28 22:14:46 terrorserver kernel: XFS internal error
> XFS_WANT_CORRUPTED_GOTO at line 2092 of file fs/xfs/xfs_bmap_btree.c.
> Caller 0xffffffff8837446f
Interesting. That's a corrupted inode extent btree - I haven't seen
one of them for a long while. Were there any errors (like IO errors)
reported before this?
However, the first step is to determine if the error is on disk or an
in-memory error. Can you post output of:
- xfs_info <mntpt>
- xfs_repair -n after a shutdown
Can you upgrade xfsprogs (i.e. xfs_repair) to the latest version
(3.1.2) before you do this as well?
> We have reproduced the condition 3 times and each time we have been
> able to remount the drive ( to replay the transaction log ) and then
> preform and xfs_repair.
>
> We are just using cp to copy the file.
>
> Some further details about the system:
>
> Software:
> - Fresh install of CentOS 5.5 64bit all patches up to date
> - Kernel 2.6.18-194.3.1.el5.centos.plus
I've got no idea exactly what version of XFS that has in it, so I
can't say off the top of my head whether this is a fixed bug or not.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-06 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 10:57 CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO) Shaun Adolphson
2010-07-06 16:17 ` Stan Hoeppner
2010-07-06 22:00 ` Shaun Adolphson
2010-07-06 23:18 ` Dave Chinner [this message]
2010-07-07 1:51 ` Eric Sandeen
2010-07-08 11:21 ` Shaun Adolphson
2010-07-11 11:44 ` Shaun Adolphson
2010-07-11 11:47 ` Shaun Adolphson
2010-07-12 1:08 ` Dave Chinner
2010-07-12 5:45 ` Dave Chinner
2010-08-16 10:32 ` Shaun Adolphson
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=20100706231856.GC25018@dastard \
--to=david@fromorbit.com \
--cc=shaun@adolphson.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.