mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "James Stevenson" <mistral@stev.org>
To: "Andrew Morton" <akpm@zip.com.au>
Cc: "Roy Sigurd Karlsbakk" <roy@karlsbakk.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: temporarily system freeze with high I/O write to ext2 fs
Date: Fri, 7 Dec 2001 09:47:54 -0000	[thread overview]
Message-ID: <016501c17f04$3f5730c0$0cfea8c0@ezdsp.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0112061458360.15516-100000@mustard.heime.net> <3C0FD78D.F567ECBD@zip.com.au> <00e601c17eb0$25e20d80$0801a8c0@Stev.org> <3C1006C3.895EEE9F@zip.com.au>


> >
> > > > why is it that Linux 'hangs' while doing heavy I/O operations (such
as
> > dd)
> > > > to (and perhaps from?) ext2 file systems? I can't see the same
behaivour
> > > > when using other file systems, such as ReiserFS
> > > >
> > >
> > > A partial fix for this went into 2.4.17-pre2.  What kernel are you
> > > using?
> >
> > i have always had with problem normally during disk writes.
> > currently on 2.4.x-14 + 2.4.16
>
> Please try 2.4.17-pre2 or later.
>

ok i should have some time to try that at the weekend.

> > its not that it hangs but it gets extremely laggy eg 2/3 seconds pause
> > for keyboard input to appear on a console.
>
> Your app got paged out, and the enormous read latencies in 2.4.16
> caused it to remain there.

why would it have been paged out there was loads of free
ram. there is 192MB in the machine and no X windows or
anything and the app was bash and there are not many other processes.

    James






      reply	other threads:[~2001-12-07  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 14:03 Roy Sigurd Karlsbakk
2001-12-06 20:39 ` Andrew Morton
2001-12-06 23:45   ` James Stevenson
2001-12-07  0:01     ` Andrew Morton
2001-12-07  9:47       ` James Stevenson [this message]

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='016501c17f04$3f5730c0$0cfea8c0@ezdsp.com' \
    --to=mistral@stev.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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

Powered by JetHome