All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Valdis.Kletnieks@vt.edu
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc2-mm1 - ext3 wedging up
Date: Fri, 23 Sep 2005 19:45:36 +1000	[thread overview]
Message-ID: <200509231945.37057.kernel@kolivas.org> (raw)
In-Reply-To: <200509230720.j8N7KYGX023826@turing-police.cc.vt.edu>

On Fri, 23 Sep 2005 17:20, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 23 Sep 2005 10:36:16 +1000, Con Kolivas said:
>
> (Adding Andrea to the To: list...)
>
> > On Fri, 23 Sep 2005 05:59, Valdis.Kletnieks@vt.edu wrote:
> > > Am seeing reproducible wedging up when writing large (20M+) files to an
> > > ext3 file system.  Oddly enough, if something *else* writes files to
> > > the file system as well, it will unwedge for a while and make progress.
> > >  Also, a 'sync' command will relieve things temporarily - but after a
> > > few megabytes it comes to a halt again.  Looks like a borkage someplace
> > > not causing it to actually finish pushing dirty file pages out -
> > > gkrellm reports little/no disk activity in progress. File activity on
> > > *other* filesystems continues unimpeded.
> >
> > Could be the write throttling patches.
> >
> > Try backing these out (in this order I think):
> >
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc2
> >/2.6
>
> .14-rc2-mm1/broken-out/per-task-predictive-write-throttling-1-tweaks.patch
>
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc2
> >/2.6
>
> .14-rc2-mm1/broken-out/per-task-predictive-write-throttling-1.patch
>
> Bingo.  I haven't built a kernel with these excluded, but writing 0 to
> /proc/sys/vm/dirty_ratio_centisecs fixes the problem, so I'm pretty sure
> this is it.
>
> (For the record, I've noticed the starvation issue that Andrea is trying to
> address, where one process can lock out others, so I *do* think work is
> needed here...)

I don't disagree, which is why I was excited by this work as well. Like all 
things in the kernel it always ends up being more complicated than the 
original plan, requiring reworking. So I do not remotely see this as a 
problem at this early stage.

Cheers,
Con

  parent reply	other threads:[~2005-09-23  9:45 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 [this message]
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
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=200509231945.37057.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.