mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "James Stevenson" <mail-lists@stev.org>
To: "Andrew Morton" <akpm@zip.com.au>,
	"Roy Sigurd Karlsbakk" <roy@karlsbakk.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: temporarily system freeze with high I/O write to ext2 fs
Date: Thu, 6 Dec 2001 23:45:54 -0000	[thread overview]
Message-ID: <00e601c17eb0$25e20d80$0801a8c0@Stev.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0112061458360.15516-100000@mustard.heime.net> <3C0FD78D.F567ECBD@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

> For how long does it "hang"?   What exactly are you doing when it
> occurs?

its not that it hangs but it gets extremely laggy eg 2/3 seconds pause
for keyboard input to appear on a console.

> Is your disk system well-tuned?  What throughput do you get with
> `hdparm -t /dev/hdXX'?

i have tuned with hdparm as much as i can. but i cannot tune the
VM because the files in /proc/sys/vm do not seem to make any difference
to the system at all and the documents dont seem to be correct inn
procfs.txt
if docs are wrong for a kernel version would it not be better to either say
they are wrong
or remove them alll together. but i assume this is todo with the latest VM
change.

are there going to be new documents for these files ?

    James



  reply	other threads:[~2001-12-06 23: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 [this message]
2001-12-07  0:01     ` Andrew Morton
2001-12-07  9:47       ` James Stevenson

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='00e601c17eb0$25e20d80$0801a8c0@Stev.org' \
    --to=mail-lists@stev.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mistral@stev.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