Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932072AbVIWVqZ@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932072AbVIWVqZ (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 23 Sep 2005 17:46:25 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932073AbVIWVqZ
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 23 Sep 2005 17:46:25 -0400
Received: from e35.co.us.ibm.com ([32.97.110.153]:59029 "EHLO
	e35.co.us.ibm.com") by vger.kernel.org with ESMTP id S932072AbVIWVqY
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 23 Sep 2005 17:46:24 -0400
Subject: Re: 2.6.14-rc2-mm1 - ext3 wedging up
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Valdis.Kletnieks@vt.edu, Con Kolivas <kernel@kolivas.org>,
       linux-kernel@vger.kernel.org
In-Reply-To: <1127509155.8875.6.camel@kleikamp.austin.ibm.com>
References: <200509221959.j8MJxJsY010193@turing-police.cc.vt.edu>
	 <200509231036.16921.kernel@kolivas.org>
	 <200509230720.j8N7KYGX023826@turing-police.cc.vt.edu>
	 <20050923153158.GA4548@x30.random>
	 <1127509047.8880.4.camel@kleikamp.austin.ibm.com>
	 <1127509155.8875.6.camel@kleikamp.austin.ibm.com>
Content-Type: text/plain
Date: Fri, 23 Sep 2005 16:46:19 -0500
Message-Id: <1127511979.8875.11.camel@kleikamp.austin.ibm.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1124
Lines: 28

On Fri, 2005-09-23 at 15:59 -0500, Dave Kleikamp wrote:
> On Fri, 2005-09-23 at 15:57 -0500, Dave Kleikamp wrote:
> > On Fri, 2005-09-23 at 17:31 +0200, Andrea Arcangeli wrote:
> > > Hello,
> > > 
> > > Can you try this updated patch? I believe the blk_congestion_wait is
> > > just wrong there, since there may be just one page being flushed. That
> > > sounds like a longstanding bug except it normally wouldn't trigger
> > > because the dirty levels never goes down near zero during heavy writes.
> > 
> > fsx is now stuck in a loop somewhere, using 100% cpu.
> 
> I hit send a little early.  It eventually responded to a ^C.  I'll try
> to get some more info.

I'd guess that it's spinning in balance_dirty_pages.
/proc/<pid>/future_dirty is 25650 for fsx.  It appears that
nr_reclaimable is not going to zero for some reason.

-- 
David Kleikamp
IBM Linux Technology Center

-
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/