From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: xfs@oss.sgi.com
Subject: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Thu, 29 May 2008 15:48:38 +0200 [thread overview]
Message-ID: <20080529134837.GA4241@apartia.fr> (raw)
Hi,
I found this in a server's dmesg:
XFS internal error XFS_WANT_CORRUPTED_GOTO at line 4518 of file fs/xfs/xfs_bmap.c. Caller 0xffffffff803fc46b
Pid: 28612, comm: rsync Not tainted 2.6.25.4-1-pyrrhus64 #1
Call Trace:
[<ffffffff803fc46b>] xfs_iread_extents+0xac/0xc8
[<ffffffff803dd413>] xfs_bmap_read_extents+0x328/0x34b
[<ffffffff803fc46b>] xfs_iread_extents+0xac/0xc8
[<ffffffff803dc279>] xfs_bmap_last_offset+0x91/0xd5
[<ffffffff803ebb3a>] xfs_dir2_isblock+0x19/0x4a
[<ffffffff803e9084>] xfs_da_brelse+0x70/0x9d
[<ffffffff803ec1fe>] xfs_dir_lookup+0xb9/0x12b
[<ffffffff803d690b>] xfs_attr_leaf_get+0x76/0x99
[<ffffffff807c10a3>] __down_write_nested+0x12/0x93
[<ffffffff8040f898>] xfs_dir_lookup_int+0x2c/0xc3
[<ffffffff803f9730>] xfs_ilock+0x4c/0x70
[<ffffffff80411c7c>] xfs_lookup+0x44/0x70
[<ffffffff8041c991>] xfs_vn_lookup+0x29/0x5f
[<ffffffff8027a641>] do_lookup+0xc5/0x1af
[<ffffffff8027c321>] __link_path_walk+0x874/0xd1e
[<ffffffff8028583c>] file_update_time+0x30/0xd4
[<ffffffff8027c828>] path_walk+0x5d/0xba
[<ffffffff8027cb2b>] do_path_lookup+0x14c/0x16f
[<ffffffff8027b897>] getname+0x140/0x181
[<ffffffff8027d34a>] __user_walk_fd+0x37/0x53
[<ffffffff802765b1>] vfs_lstat_fd+0x18/0x47
[<ffffffff8022a6e9>] hrtick_set+0x88/0xf6
[<ffffffff807c0189>] thread_return+0x68/0xac
[<ffffffff802767a3>] sys_newlstat+0x19/0x31
[<ffffffff80274492>] sys_write+0x45/0x6e
[<ffffffff8020af3b>] system_call_after_swapgs+0x7b/0x80
next reply other threads:[~2008-05-29 13:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 13:48 Louis-David Mitterrand [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-22 4:52 XFS internal error XFS_WANT_CORRUPTED_GOTO 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
2009-06-24 11:56 Nitin Arora
2009-06-24 12:40 ` Michael Monnerie
2009-06-24 13:18 ` Nitin Arora
2009-06-24 13:23 ` Eric Sandeen
2009-06-25 10:06 ` Nitin Arora
2009-06-25 13:45 ` Eric Sandeen
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=20080529134837.GA4241@apartia.fr \
--to=vindex+lists-xfs@apartia.org \
--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