From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: 2.6.19-rc2-mm1 warning in invalidate_inode_pages2_range() Date: Thu, 19 Oct 2006 16:02:25 -0700 Message-ID: <20061019160225.fee4c25f.akpm@osdl.org> References: <1161297546.26843.33.camel@dyn9047017100.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Zach Brown , ext4 , lkml Return-path: Received: from smtp.osdl.org ([65.172.181.4]:30404 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1946648AbWJSXCh (ORCPT ); Thu, 19 Oct 2006 19:02:37 -0400 To: Badari Pulavarty In-Reply-To: <1161297546.26843.33.camel@dyn9047017100.beaverton.ibm.com> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Thu, 19 Oct 2006 15:39:06 -0700 Badari Pulavarty wrote: > Hi Zach, > > While running IO tests I get following messages on 2.6.19-rc2-mm1 > > BUG: warning at mm/truncate.c:400/invalidate_inode_pages2_range() > > Call Trace: > [] show_trace+0x41/0x70 > [] dump_stack+0x12/0x20 > [] invalidate_inode_pages2_range+0x297/0x2e0 > [] generic_file_direct_IO+0xf5/0x130 > [] generic_file_direct_write+0x74/0x140 > [] __generic_file_aio_write_nolock+0x36c/0x4b0 > [] generic_file_aio_write+0x67/0xd0 > [] :ext4dev:ext4_file_write+0x23/0xc0 > DWARF2 unwinder stuck at ext4_file_write+0x23/0xc0 [ext4dev] > Leftover inexact backtrace: > [] do_sync_write+0xcf/0x120 > [] cp_new_stat+0xe7/0x100 > [] autoremove_wake_function+0x0/0x30 > [] __mutex_lock_slowpath+0x1df/0x1f0 > [] vfs_write+0xbd/0x180 > [] sys_write+0x53/0x90 > [] system_call+0x7e/0x83 > that's warning that we weren't able to invalidate some pagecache. That's not really suprising. Perhaps we should be more careful in deciding when to fail the call (ie: leaving behind a clean page is ok, leaving behind a dirty page is bad). Probably it's leaving behind dirty pagecache and you're about to lose your data. Which I bet is your own darn fault for doing silly things. What workload was in use?