Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757267AbXIUKfO (ORCPT ); Fri, 21 Sep 2007 06:35:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755565AbXIUKfB (ORCPT ); Fri, 21 Sep 2007 06:35:01 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:37207 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753420AbXIUKfA (ORCPT ); Fri, 21 Sep 2007 06:35:00 -0400 Date: Fri, 21 Sep 2007 03:33:36 -0700 From: Andrew Morton To: richard kennedy Cc: Chuck Ebbert , Matthias Hensler , linux-kernel , Thomas Gleixner , Peter Zijlstra Subject: Re: Processes spinning forever, apparently in lock_timer_base()? Message-Id: <20070921033336.c327ffd9.akpm@linux-foundation.org> In-Reply-To: <1190370341.3121.35.camel@castor.rsk.org> References: <46B10BB7.60900@redhat.com> <20070803113407.0b04d44e.akpm@linux-foundation.org> <20070804084426.GA20464@kobayashi-maru.wspse.de> <20070809095943.GA7763@kobayashi-maru.wspse.de> <20070809095534.25ae1c42.akpm@linux-foundation.org> <46F2E103.8000907@redhat.com> <20070920142927.d87ab5af.akpm@linux-foundation.org> <46F2EE76.4000203@redhat.com> <20070920153654.b9e90616.akpm@linux-foundation.org> <1190370341.3121.35.camel@castor.rsk.org> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1044 Lines: 21 On Fri, 21 Sep 2007 11:25:41 +0100 richard kennedy wrote: > > That's all a bit crappy if the wrong races happen and some other task is > > somehow exceeding the dirty limits each time this task polls them. Seems > > unlikely that such a condition would persist forever. > > > > So the question is, why do we have large amounts of dirty pages for one > > disk which appear to be sitting there not getting written? > > The lockup I'm seeing intermittently occurs when I have 2+ tasks copying > large files (1Gb+) on sda & a small read-mainly mysql db app running on > sdb. The lockup seems to happen just after the copies finish -- there > are lots of dirty pages but nothing left to write them until kupdate > gets round to it. Then what happens? The system recovers? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/