From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id pBJMBhFf100925 for ; Mon, 19 Dec 2011 16:11:43 -0600 Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by cuda.sgi.com with ESMTP id rShHdgTwMC3EUpCG for ; Mon, 19 Dec 2011 14:11:40 -0800 (PST) Date: Tue, 20 Dec 2011 09:11:37 +1100 From: Dave Chinner Subject: Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5) Message-ID: <20111219221137.GR23662@dastard> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Jeremy Sanders Cc: linux-xfs@oss.sgi.com 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: [] [] xfs_vm_writepage+0x4c2/0x4f0 [xfs] [] __writepage+0x17/0x40 [] write_cache_pages+0x20d/0x460 [] generic_writepages+0x4a/0x70 [] xfs_vm_writepages+0x4d/0x60 [xfs] [] do_writepages+0x21/0x40 [] writeback_single_inode+0x149/0x3e0 [] writeback_sb_inodes+0x1a0/0x240 [] __writeback_inodes_wb+0x9e/0xd0 [] wb_writeback+0x25b/0x340 [] wb_do_writeback+0x1c3/0x200 [] bdi_writeback_thread+0x83/0x2a0 [] kthread+0x8c/0xa0 [] 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