mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: efault@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: multi-second freezes with current GIT?
Date: Tue, 08 May 2007 23:23:26 -0700 (PDT)	[thread overview]
Message-ID: <20070508.232326.44096869.davem@davemloft.net> (raw)
In-Reply-To: <1178681360.7487.59.camel@Homer.simpson.net>

From: Mike Galbraith <efault@gmx.de>
Date: Wed, 09 May 2007 05:29:20 +0200

> On Tue, 2007-05-08 at 18:44 -0700, David Miller wrote:
> > I've been noticing this off and on for the past week or so.
> > 
> > The system seems to jam up for several seconds, anything that would
> > need to read from disk just sits there during this time.  I think it's
> > correlated with generating a lot of dirty write data.
> > 
> > My mouse moves around in X etc. so it really is only processes that
> > need to read from disk that get stuck.
> > 
> > Perhaps it's a side effect of those dirty ratio changes Linus made to
> > start off the 2.6.22 merge cycle?
> 
> Uhoh, that seems highly likely.
> 
> I think those changes may have been triggered by my repeatable and truly
> horrible system stalls when writing to an ext3 data=ordered nearly full
> filesystem.  Anything that does fdatasync() and/or fsync() can cause
> very bad experiences indeed.  KDE's little menu/program launcher
> doohickey does fdatasync() for some odd reason, which has utterly killed
> my entire GUI for up to and including 20 minutes at a whack.
> 
> Switching to data=writeback cured those horrors.  Lowering the dirty
> ratio reduced the agony of data=ordered tremendously, but didn't make it
> even remotely acceptable.

I'm using data=ordered on my partitions too.

  reply	other threads:[~2007-05-09  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  1:44 David Miller
2007-05-09  3:29 ` Mike Galbraith
2007-05-09  6:23   ` David Miller [this message]
2007-05-09  8:43     ` Andrew Morton
2007-05-09  8:45       ` David Miller

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=20070508.232326.44096869.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=efault@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®