From: Badari Pulavarty <pbadari@us.ibm.com>
Subject: Re: 2.6.19-rc2-mm1 warning in invalidate_inode_pages2_range()
Date: Thu, 19 Oct 2006 16:12:25 -0700
Message-ID: <1161299545.26843.41.camel@dyn9047017100.beaverton.ibm.com>
References: <1161297546.26843.33.camel@dyn9047017100.beaverton.ibm.com>
	 <20061019160225.fee4c25f.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Zach Brown <zach.brown@oracle.com>,
	ext4 <linux-ext4@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Return-path: <linux-ext4-owner@vger.kernel.org>
Received: from e33.co.us.ibm.com ([32.97.110.151]:28052 "EHLO
	e33.co.us.ibm.com") by vger.kernel.org with ESMTP id S1946657AbWJSXMh
	(ORCPT <rfc822;linux-ext4@vger.kernel.org>);
	Thu, 19 Oct 2006 19:12:37 -0400
To: Andrew Morton <akpm@osdl.org>
In-Reply-To: <20061019160225.fee4c25f.akpm@osdl.org>
Sender: linux-ext4-owner@vger.kernel.org
List-Id: linux-ext4.vger.kernel.org

On Thu, 2006-10-19 at 16:02 -0700, Andrew Morton wrote:
> On Thu, 19 Oct 2006 15:39:06 -0700
> Badari Pulavarty <pbadari@us.ibm.com> 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:
> >  [<ffffffff8020b481>] show_trace+0x41/0x70
> >  [<ffffffff8020b4c2>] dump_stack+0x12/0x20
> >  [<ffffffff80257f17>] invalidate_inode_pages2_range+0x297/0x2e0
> >  [<ffffffff8024fcb5>] generic_file_direct_IO+0xf5/0x130
> >  [<ffffffff8024fd64>] generic_file_direct_write+0x74/0x140
> >  [<ffffffff802507cc>] __generic_file_aio_write_nolock+0x36c/0x4b0
> >  [<ffffffff80250977>] generic_file_aio_write+0x67/0xd0
> >  [<ffffffff8808f6d3>] :ext4dev:ext4_file_write+0x23/0xc0
> > DWARF2 unwinder stuck at ext4_file_write+0x23/0xc0 [ext4dev]
> > Leftover inexact backtrace:
> >  [<ffffffff8027379f>] do_sync_write+0xcf/0x120
> >  [<ffffffff802772b7>] cp_new_stat+0xe7/0x100
> >  [<ffffffff8023db90>] autoremove_wake_function+0x0/0x30
> >  [<ffffffff804805bf>] __mutex_lock_slowpath+0x1df/0x1f0
> >  [<ffffffff8027408d>] vfs_write+0xbd/0x180
> >  [<ffffffff802747b3>] sys_write+0x53/0x90
> >  [<ffffffff80209c1e>] 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?

Running fsx and fsstress.

- Badari