public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Erik Elmore <lk@bigsexymo.com>
Cc: Mike Fedyk <mfedyk@matchmail.com>, linux-kernel@vger.kernel.org
Subject: Re: EXT3 - freeze ups during disk writes
Date: Sat, 01 Dec 2001 13:08:23 -0800	[thread overview]
Message-ID: <3C0946C7.798208C3@zip.com.au> (raw)
In-Reply-To: <20011130235414.E489@mikef-linux.matchmail.com> <Pine.LNX.4.33.0112011209190.3893-100000@localhost.localdomain>

Erik Elmore wrote:
> 
> ahhhh... woops... every official kernel since ext3 made it into the
> official tree, 2.4.14 if memory serves.  I'm using gcc 2.95.3.  And to
> clarify the bug, say on a large disk write, the pause isn't constant,
> it just pauses for a second every few seconds during the write.  For
> smaller writes, it will pause only once, I assume while performing the
> actual write to disk.
> 

I've seen a couple of reports where ext3 appears to exacerbate
the effects of poor hdparm settings.  What is your raw disk
throughput, from `hdparm -t /dev/hda'?

  reply	other threads:[~2001-12-01 21:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  6:47 EXT3 - freeze ups during disk writes Erik Elmore
2001-12-01  7:54 ` Mike Fedyk
2001-12-01 18:14   ` Erik Elmore
2001-12-01 21:08     ` Andrew Morton [this message]
2001-12-02 17:17       ` Erik Elmore
2001-12-02 18:15         ` Mark Hahn
2001-12-02 22:37           ` Ivanovich
2001-12-03 18:57             ` Erik Elmore
2001-12-02 13:55     ` Bernd Eckenfels
2001-12-02 17:25       ` Erik Elmore
2001-12-03  7:52       ` Jan-Hendrik Palic
2001-12-04  0:17         ` Andrew Morton
2001-12-04 21:53           ` Jan-Hendrik Palic
2001-12-05  2:43             ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01 17:56 Stephane Chauveau

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=3C0946C7.798208C3@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@bigsexymo.com \
    --cc=mfedyk@matchmail.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