mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Suspected bug - System slowdown under unexplained excessive disk I/O - 2.4.13
Date: Wed, 7 Nov 2001 22:11:48 -0800	[thread overview]
Message-ID: <20011107221148.A7828@greenhydrant.com> (raw)
In-Reply-To: <200111080425.fA84Pdb04541@mysql.sashanet.com>
In-Reply-To: <200111080425.fA84Pdb04541@mysql.sashanet.com>; from sasha@mysql.com on Wed, Nov 07, 2001 at 09:25:38PM -0700

On Wed, Nov 07, 2001 at 09:25:38PM -0700, Sasha Pachev wrote:
> 
> Summary: 
> 
> System slowdown under unexplained excessive disk I/O 
> 
> Full description: 
> 
> While running X, KDE, having a few windows open, I ran make -j4 on MySQL 
> source tree. I do this all the time and it usually works just fine - the 
> system is a little bit unresponsive. However, occasionally the system becomes 
> completely unresponsive - the disk goes crazy, the machine pings but neither 
> ssh or telnet work - connection to the port is established, but nothing 
> further than that. It does respond to magic SysRQ. I was able to get a memory 
> info dump + stack traces into syslog, included below. The filesystem is 
> ReiserFS.
> 
> Keywords: 
> 
> vm, ReiserFS, heavy disk I/O,

Let me guess, IDE disks?  Anyway, this is a FAQ.  Go www.namesys.com, click
on the FAQ, and look at #15.

This issue really can be a problem as the entire machine will freeze up for
a good chunk of time while the disk churns away.  Strangely enough, I've
only noticed it on some machines, not all.  But it's enough of a problem to
cause me to switch to ext3.

-Dave

  parent reply	other threads:[~2001-11-08  6:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  4:25 Sasha Pachev
2001-11-08  4:55 ` Oktay Akbal
2001-11-08  5:33   ` Oktay Akbal
2001-11-08 14:50     ` Sasha Pachev
2001-11-08 12:15   ` Nikita Danilov
2001-11-08  6:11 ` David Rees [this message]
2001-11-08  7:45   ` Oktay Akbal
2001-11-08  8:10     ` David Rees

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=20011107221148.A7828@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --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®