public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jeremy Sanders <jeremy@jeremysanders.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5)
Date: Tue, 20 Dec 2011 09:11:37 +1100	[thread overview]
Message-ID: <20111219221137.GR23662@dastard> (raw)
In-Reply-To: <jcn0ip$hsk$1@dough.gmane.org>

On Mon, Dec 19, 2011 at 09:36:24AM +0000, Jeremy Sanders wrote:
> Hello - this was just produced in kernel 3.1.5 (Fedora 16, x86-64, 
> kernel-3.1.5-1.fc16.x86_64).
> 
> Jeremy
> 
> 
> Dec 19 00:56:06 xback2 kernel: [374538.665353] ------------[ cut here ]------------

There was a line above this about an assert failure? What was it?

> Dec 19 00:56:06 xback2 kernel: [374538.665431] kernel BUG at 
> fs/xfs/xfs_aops.c:959!
> Dec 19 00:56:06 xback2 kernel: [374538.665504] invalid opcode: 0000 [#1] SMP 
> Dec 19 00:56:06 xback2 kernel: [374538.665578] CPU 1 
> Dec 19 00:56:06 xback2 kernel: [374538.665581] Modules linked in: btrfs 
.....
Pid: 22689, comm: flush-9:0 Not tainted 3.1.5-1.fc16.x86_64 #1 WinFast C51GM03/C51MCP51
RIP: 0010: [<ffffffffa02ec7e2>]  [<ffffffffa02ec7e2>] xfs_vm_writepage+0x4c2/0x4f0 [xfs]

 [<ffffffff8111dec7>] __writepage+0x17/0x40
 [<ffffffff8111e32d>] write_cache_pages+0x20d/0x460
 [<ffffffff8111e5ca>] generic_writepages+0x4a/0x70
 [<ffffffffa02eb8fd>] xfs_vm_writepages+0x4d/0x60 [xfs]
 [<ffffffff8111f8d1>] do_writepages+0x21/0x40
 [<ffffffff81198af9>] writeback_single_inode+0x149/0x3e0
 [<ffffffff81198f30>] writeback_sb_inodes+0x1a0/0x240
 [<ffffffff8119906e>] __writeback_inodes_wb+0x9e/0xd0
 [<ffffffff8119a25b>] wb_writeback+0x25b/0x340
 [<ffffffff8119a7b3>] wb_do_writeback+0x1c3/0x200
 [<ffffffff8119a873>] bdi_writeback_thread+0x83/0x2a0
 [<ffffffff8108ddbc>] kthread+0x8c/0xa0
 [<ffffffff815d9974>] kernel_thread_helper+0x4/0x10

If it tripped the assert I think it did, it looks like the system
was trying to do write IO into a hole in the file. What workload
were you running, and what are the details of your machine + storage
config?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-12-19 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19  9:36 bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5) Jeremy Sanders
2011-12-19 22:11 ` Dave Chinner [this message]
2011-12-20  9:54   ` Jeremy Sanders
2011-12-28 17:16 ` Christoph Hellwig
2011-12-29 11:07   ` Jeremy Sanders

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=20111219221137.GR23662@dastard \
    --to=david@fromorbit.com \
    --cc=jeremy@jeremysanders.net \
    --cc=linux-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