From: barryn@pobox.com (Barry K. Nathan)
To: zlatko.calusic@iskon.hr
Cc: Linus Torvalds <torvalds@transmeta.com>,
Jens Axboe <axboe@suse.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: xmm2 - monitor Linux MM active/inactive lists graphically
Date: Sun, 28 Oct 2001 11:13:28 -0800 (PST) [thread overview]
Message-ID: <20011028191328.CCC828A6EA@pobox.com> (raw)
In-Reply-To: <87k7xfk6zd.fsf@atlas.iskon.hr> from "Zlatko Calusic" at Oct 28, 2001 06:30:14 PM
> Unfortunately, things didn't change on my first disk (IBM 7200rpm
> @home). I'm still getting low numbers, check the vmstat output at the
> end of the email.
>
> But, now I found something interesting, other two disk which are on
> the standard IDE controller work correctly (writing is at 17-22
> MB/sec). The disk which doesn't work well is on the HPT366 interface,
> so that may be our culprit. Now I got the idea to check patches
> retrogradely to see where it started behaving poorely.
>
> Also, one more thing, I'm pretty sure that under strange circumstances
> (specific alignment of stars) it behaves well (with appropriate
> writing speed). I just haven't yet pinpointed what needs to be done to
> get to that point.
I didn't read the entire thread, so this is a bit of a stab in the dark,
but:
This really reminds me of a problem I once had with a hard drive of
mine. It would usually go at 15-20MB/sec, but sometimes (under both
Linux and Windows) would slow down to maybe 350KB/sec. The slowdown, or
lack thereof, did seem to depend on the alignment of the stars. I lived
with it for a number of months, then started getting intermittent I/O
errors as well, as if the drive had bad sectors on disk.
The problem turned out to be insufficient ventilation for the controller
board on the bottom of the drive -- it was in the lowest 3.5" drive bay
in my case, so the bottom of the drive was snuggled next to a piece of
metal with ventilation holes. The holes were rather large (maybe 0.5"
diameter) -- and so were the areas without holes. Guess where one of the
drive's controller chips happened to be positioned, relative to the
holes? :( Moving the drive up a bit in the case, so as to allow 0.5"-1"
of space for air beneath the drive, fixed the problem (both the slowdown
and the I/O errors).
I don't know if this is your problem, but I'm mentioning it just in
case it is...
-Barry K. Nathan <barryn@pobox.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-10-28 19:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 10:42 Zlatko Calusic
2001-10-24 14:26 ` Marcelo Tosatti
2001-10-25 0:25 ` Zlatko Calusic
2001-10-25 4:19 ` Linus Torvalds
2001-10-25 4:57 ` Linus Torvalds
2001-10-25 12:48 ` Zlatko Calusic
2001-10-25 16:31 ` Linus Torvalds
2001-10-25 17:33 ` Jens Axboe
2001-10-26 9:45 ` Zlatko Calusic
2001-10-26 10:08 ` Zlatko Calusic
2001-10-26 14:39 ` Jens Axboe
2001-10-26 14:57 ` Zlatko Calusic
2001-10-26 15:01 ` Jens Axboe
2001-10-26 16:04 ` Linus Torvalds
2001-10-26 16:57 ` Linus Torvalds
2001-10-26 17:19 ` Linus Torvalds
2001-10-28 17:30 ` Zlatko Calusic
2001-10-28 17:34 ` Linus Torvalds
2001-10-28 17:48 ` Alan Cox
2001-10-28 17:59 ` Linus Torvalds
2001-10-28 18:22 ` Alan Cox
2001-10-28 18:46 ` Linus Torvalds
2001-10-28 19:29 ` Alan Cox
2001-10-28 18:56 ` Andrew Morton
2001-10-30 8:56 ` Jens Axboe
2001-10-30 9:26 ` Zlatko Calusic
2001-10-28 19:13 ` Barry K. Nathan [this message]
2001-10-28 21:42 ` Jonathan Morton
2001-11-02 5:52 ` Zlatko's I/O slowdown status Andrea Arcangeli
2001-11-02 20:14 ` Zlatko Calusic
2001-11-02 20:26 ` Rik van Riel
2001-11-02 21:22 ` Zlatko Calusic
2001-11-02 20:57 ` Andrea Arcangeli
2001-11-02 23:23 ` Simon Kirby
2001-10-27 13:14 ` xmm2 - monitor Linux MM active/inactive lists graphically Giuliano Pochini
2001-10-28 5:05 ` Mike Fedyk
2001-10-25 9:07 ` Zlatko Calusic
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=20011028191328.CCC828A6EA@pobox.com \
--to=barryn@pobox.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=zlatko.calusic@iskon.hr \
/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