From: Michael Buesch <fsdeveloper@yahoo.de>
To: Nuno Silva <nuno.silva@vgertech.com>
Cc: Jean-Yves LENHOF <jean-yves@lenhof.eu.org>,
insecure@mail.od.ua,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6] system is very slow during disk access
Date: Thu, 7 Aug 2003 11:53:02 +0200 [thread overview]
Message-ID: <200308071153.18361.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <3F31D205.2080008@vgertech.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 07 August 2003 06:13, Nuno Silva wrote:
> Hi!
Hi,
> There are some references to: hdparm -a 512 /dev/hda.
> For some folks this improves fs performance.
>
> Does it work for you?
Changing read-ahead doesn't work. Neither to 8 nor to 512.
I think it doesn't have something to do with read-ahead,
because the system-performance-drop occurs while
writing to the disk.
My dd-example wrote to disk:
dd if=/dev/zero of=./t.test
I just ran a few other tests:
dd if=/dev/hda of=/dev/null
doesn't drop system performance and the system is very usable
while dd is running.
So reading from a plain partition is OK.
dd if=/dev/zero of=/dev/hdc7
This slows down the system _very_ much, but it's still usable.
The mouse curser doesn't jump randomly over the screen, like it
did while
dd if=/dev/zero of=./t.test
So my guess, it may have something to do with reiserFS.
So I ran another test:
I did
mke2fs /dev/hdc7
mount /dev/hdc7 /mnt/data_1
cd /mnt/data_1
dd if=/dev/zero of=./t.test
And now the surprise. :)
Here the system-behaviour is exactly the same, as while
writing to the plain partition.
The cursor is not smooth, but it's usable and it doesn't
jump ramdonly over the screen.
So I think it has something to do with reiserFS.
Where can I start to track it down, why reiserFS
is doing this?
Hmm, I'll try to enable
CONFIG_REISERFS_CHECK
and
CONFIG_REISERFS_PROC_INFO
Can somebody tell me how to debug reiserFS with these
options enabled?
> Regards,
> Nuno Silva
Short note: hda and hdc are both exactly the same devices.
- --
Regards Michael Buesch [ http://www.8ung.at/tuxsoft ]
Penguin on this machine: Linux 2.6.0-test2 - i386
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/MiGKoxoigfggmSgRAt+PAJ9gI8Z5Osm4/DcnFZsPtR7x4UQpZACfZw7R
GxC2PwCVOAWFFE39Fw9ttKM=
=v0nD
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-08-07 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 18:51 [2.6] system is very slow during disk access Michael Buesch
2003-08-06 19:29 ` Frank Van Damme
2003-08-06 19:31 ` Michael Buesch
2003-08-06 22:19 ` Willy Gardiol
2003-08-06 22:27 ` Michael Buesch
2003-08-06 19:29 ` Michael Buesch
2003-08-06 22:04 ` Andrew Morton
2003-08-06 22:44 ` Michael Buesch
2003-08-06 22:56 ` Andrew Morton
2003-08-06 23:10 ` Michael Buesch
2003-08-06 23:01 ` Bartlomiej Zolnierkiewicz
2003-08-06 23:16 ` Michael Buesch
2003-08-06 23:30 ` Bartlomiej Zolnierkiewicz
[not found] ` <200308062331.08020.insecure@mail.od.ua>
2003-08-06 20:47 ` Michael Buesch
2003-08-07 4:13 ` Nuno Silva
2003-08-07 9:53 ` Michael Buesch [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=200308071153.18361.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=akpm@osdl.org \
--cc=insecure@mail.od.ua \
--cc=jean-yves@lenhof.eu.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.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;
as well as URLs for NNTP newsgroup(s).