From: Dave Chinner <david@fromorbit.com>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: Pavel Machek <pavel@suse.cz>,
Chris Mason <chris.mason@oracle.com>,
linux-kernel@vger.kernel.org, npiggin@yahoo.com.au,
xfs@oss.sgi.com
Subject: Corrupted XFS log replay oops. (was Re: Warning and BUG with btrfs and corrupted image)
Date: Wed, 21 Jan 2009 14:57:03 +1100 [thread overview]
Message-ID: <20090121035703.GH10158@disturbed> (raw)
In-Reply-To: <20090120173455.GC21339@alice>
[drop btrfs list from this thread]
On Tue, Jan 20, 2009 at 06:34:55PM +0100, Eric Sesterhenn wrote:
> * Dave Chinner (david@fromorbit.com) wrote:
> > Sure I am. It would be good if you could start testing XFS along
> > with all the other filesystems and report anything you find.
>
> Ok, i wont report stuff with only xfs-internal backtraces from
> xfs_error_report() or are they interesting to you?
If it catches the corruption and shuts down then that's a valid
response to corruption. Mostly they are not interesting.
> This occurs during mount, box is dead afterwards
> Image can be found here :
> http://www.cccmz.de/~snakebyte/xfs.11.img.bz2
> I see this every ~10 images, which makes further testing hard :)
For future bugs, can you start a new thread on xfs@oss.sgi.com
for each report?
> [ 235.250167] ------------[ cut here ]------------
> [ 235.250354] kernel BUG at mm/vmalloc.c:164!
> [ 235.250478] invalid opcode: 0000 [#1] PREEMPT DEBUG_PAGEALLOC
> [ 235.250869] last sysfs file: /sys/block/ram9/range
> [ 235.250998] Modules linked in:
> [ 235.251037]
> [ 235.251037] Pid: 5352, comm: mount Not tainted
> (2.6.29-rc2-00021-gd84d31c #216) System Name
> [ 235.251037] EIP: 0060:[<c0182af1>] EFLAGS: 00010246 CPU: 0
> [ 235.251037] EIP is at vmap_page_range+0x19/0x112
> [ 235.251037] EAX: d1000000 EBX: d1000000 ECX: 00000163 EDX: d1000000
> [ 235.251037] ESI: 00000003 EDI: d1000000 EBP: cbbd2c08 ESP: cbbd2be8
> [ 235.251037] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
> [ 235.251037] Process mount (pid: 5352, ti=cbbd2000 task=cbb85b00
> task.ti=cbbd2000)
> [ 235.251037] Stack:
> [ 235.251037] 00000246 cbb85b00 00000163 c01414cf cbbd2c0c d1000000
> 00000003 cba0f810
> [ 235.251037] cbbd2c40 c018367c c848e280 00100000 00000000 c848e280
> 00000000 00000014
> [ 235.251037] d1000000 cba0f944 00000000 c848e160 00000000 c848e160
> cbbd2c54 c03b2e1e
> [ 235.251037] Call Trace:
> [ 235.251037] [<c01414cf>] ? trace_hardirqs_on+0xb/0xd
> [ 235.251037] [<c018367c>] ? vm_map_ram+0x36e/0x38a
> [ 235.251037] [<c03b2e1e>] ? _xfs_buf_map_pages+0x42/0x6d
> [ 235.251037] [<c03b3773>] ? xfs_buf_get_noaddr+0xbc/0x11f
> [ 235.251037] [<c03a2406>] ? xlog_get_bp+0x5a/0x5d
> [ 235.251037] [<c03a28fa>] ? xlog_find_verify_log_record+0x26/0x208
> [ 235.251037] [<c03a3521>] ? xlog_find_zeroed+0x1d6/0x214
> [ 235.251037] [<c03a3584>] ? xlog_find_head+0x25/0x358
.....
Ok, that's crashing in the new vmap code. It might take a couple
of days before I get a chance to look at this, but I've cc'd Nick Piggin
in case he has a chance to look at it before that. It's probably
an XFS bug, anyway.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2009-01-21 3:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 14:21 Warning and BUG with btrfs and corrupted image Eric Sesterhenn
2009-01-13 14:40 ` Chris Mason
2009-01-13 14:43 ` Eric Sesterhenn
2009-01-15 2:13 ` Chris Mason
2009-01-18 17:40 ` Pavel Machek
2009-01-20 6:31 ` Eric Sesterhenn
2009-01-20 9:34 ` Pavel Machek
2009-01-20 10:11 ` Dave Chinner
2009-01-20 10:15 ` Eric Sesterhenn
2009-01-20 12:59 ` Dave Chinner
2009-01-20 13:28 ` Christoph Hellwig
2009-01-20 22:20 ` Pavel Machek
2009-01-21 4:00 ` Dave Chinner
2009-01-26 16:27 ` Pavel Machek
2009-02-01 1:40 ` Dave Chinner
2009-02-04 18:29 ` Pavel Machek
2009-02-05 8:59 ` Dave Chinner
2009-02-05 9:02 ` Pavel Machek
2009-02-05 13:02 ` Chris Mason
2009-02-05 13:50 ` Pavel Machek
2009-02-05 14:19 ` jim owens
2009-02-25 19:54 ` Pavel Machek
2009-01-20 17:34 ` Eric Sesterhenn
2009-01-20 22:18 ` Pavel Machek
2009-01-21 9:36 ` Eric Sesterhenn
2009-01-21 3:57 ` Dave Chinner [this message]
2009-01-21 4:03 ` Corrupted XFS log replay oops. (was Re: Warning and BUG with btrfs and corrupted image) Nick Piggin
2009-01-22 4:37 ` [PATCH] Re: Corrupted XFS log replay oops Dave Chinner
2009-01-22 5:50 ` Felix Blyakher
2009-01-22 6:11 ` Christoph Hellwig
2009-01-22 8:35 ` Eric Sesterhenn
2009-01-22 10:06 ` Eric Sesterhenn
2009-01-22 23:37 ` Dave Chinner
2009-01-23 1:10 ` Dave Chinner
2009-01-22 23:35 ` Dave Chinner
2009-01-23 0:02 ` Dave Chinner
2009-01-23 0:06 ` Christoph Hellwig
2009-01-23 6:20 ` Felix Blyakher
2009-01-21 4:03 ` Corrupted XFS log replay oops. (was Re: Warning and BUG with btrfs and corrupted image) Dave Chinner
2009-01-20 13:11 ` Warning and BUG with btrfs and corrupted image Chris Mason
2009-01-20 16:51 ` Eric Sesterhenn
2009-01-22 2:15 ` Phillip Lougher
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=20090121035703.GH10158@disturbed \
--to=david@fromorbit.com \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@yahoo.com.au \
--cc=pavel@suse.cz \
--cc=snakebyte@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).