public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Valdis.Kletnieks@vt.edu, Con Kolivas <kernel@kolivas.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc2-mm1 - ext3 wedging up
Date: Mon, 26 Sep 2005 10:14:51 +0200	[thread overview]
Message-ID: <20050926081451.GA2785@x30.random> (raw)
In-Reply-To: <1127511979.8875.11.camel@kleikamp.austin.ibm.com>

On Fri, Sep 23, 2005 at 04:46:19PM -0500, Dave Kleikamp wrote:
> 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

Ok the good news is that this isn't a bug in the basic algorithm, but
just in the implementation of it.

> nr_reclaimable is not going to zero for some reason.

Exactly, the !nr_reclaimable check is what I thought would have
prevented an infinite loop to trigger...

Unfortunately I couldn't reproduce on my laptop, I was working from the
laptop the whole last week (I even did a presentation with this patch
applied ;), I'll try to reprouce with fsx now.

Thanks for the help!

  reply	other threads:[~2005-09-26  8:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 19:59 2.6.14-rc2-mm1 - ext3 wedging up Valdis.Kletnieks
2005-09-23  0:36 ` Con Kolivas
2005-09-23  7:20   ` Valdis.Kletnieks
2005-09-23  8:45     ` Andrea Arcangeli
2005-09-23 14:24       ` Dave Kleikamp
2005-09-23  9:45     ` Con Kolivas
2005-09-23 15:31     ` Andrea Arcangeli
2005-09-23 19:11       ` Valdis.Kletnieks
2005-09-23 20:57       ` Dave Kleikamp
2005-09-23 20:59         ` Dave Kleikamp
2005-09-23 21:46           ` Dave Kleikamp
2005-09-26  8:14             ` Andrea Arcangeli [this message]
2005-09-28 22:38             ` Andrea Arcangeli
2005-10-01  0:27               ` Dave Kleikamp
2005-10-02 10:27                 ` Andrea Arcangeli
2005-10-02 10:32                   ` Andrea Arcangeli
2005-10-02 13:51                   ` Dave Kleikamp
2005-10-03 18:06                     ` Dave Kleikamp
2005-10-03 18:31                       ` Valdis.Kletnieks
2005-10-10 17:15                         ` Andrea Arcangeli
2005-10-10 17:21                           ` Dave Kleikamp
2005-10-03  1:04                   ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050926081451.GA2785@x30.random \
    --to=andrea@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@austin.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox