mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Oktay Akbal <oktay.akbal@s-tec.de>
Cc: Sasha Pachev <sasha@mysql.com>,
	linux-kernel@vger.kernel.org,
	Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Suspected bug - System slowdown under unexplained excessive disk I/O - 2.4.13
Date: Thu, 8 Nov 2001 15:15:43 +0300	[thread overview]
Message-ID: <15338.30575.374302.718516@beta.reiserfs.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0111080627320.12430-100000@omega.hbh.net>
In-Reply-To: <Pine.LNX.4.40.0111080546030.12366-100000@omega.hbh.net> <Pine.LNX.4.40.0111080627320.12430-100000@omega.hbh.net>

Oktay Akbal writes:
 > I just did a quick retest with  sql-bench on my machine and found that
 > reiserfs seems to be a source for that problem.
 > I did not reproduce the whole problem, since i stopped
 > test-create before the system was to unresponsive.
 > 
 > But I started test-create on a partition with
 > reiserfs. After much files were created the system to very
 > long for bash command-completion or doing simple thing
 > free, top etc. this was even after test-create was stopped.
 > It took about 30 seconds till the system responded normally.
 > 
 > Same test with ext2 on the same partition showed no problems.
 > 
 > Reran the test with reiserfs and the system got unresponsive
 > again.

It doesn't seem that you have the same problem as Sasha. Reiserfs has
known problem with dealing with large holes, so may be this explains
situation. We'll try to reproduce your results.

 > 
 > Did you use reiserfs ?
 > 
 > Oktay
 > 

Nikita.

 > 
 > On Thu, 8 Nov 2001, Oktay Akbal wrote:
 > 
 > > On Wed, 7 Nov 2001, 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.
 > 

  parent reply	other threads:[~2001-11-08 12:18 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 [this message]
2001-11-08  6:11 ` David Rees
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=15338.30575.374302.718516@beta.reiserfs.com \
    --to=nikita@namesys.com \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oktay.akbal@s-tec.de \
    --cc=sasha@mysql.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

all inboxes | Powered by JetHome®