From: Andrew Morton <andrewm@uow.edu.au>
To: Collectively Unconscious <swarm@warpcore.provalue.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O problem with sustained writes
Date: Sat, 03 Mar 2001 10:57:08 +1100 [thread overview]
Message-ID: <3AA03354.A07F5179@uow.edu.au> (raw)
In-Reply-To: <3AA00D5A.44FA21D0@mandrakesoft.com> <Pine.LNX.4.10.10103021455500.29369-100000@warpcore.provalue.net>
Collectively Unconscious wrote:
>
> We are having a problem with writes.
> They start at 14 M/s for the first hour and then drop to 2.5 M/s and stay
> that way. Reads do not seem effected and we've noticed this on the 2.2.16,
> 2.2.17, 2.2.18 and now the 2.2.19pre11 kernels.
>
> These are SMP P-IIIs from 450 to 800 MHz. Redhat 6.2
I've seen something similar on Seagate ST313021A IDE drives.
After a few minutes their read throughput falls from 20
megs/sec to about 5. Issuing *any* drive-setting command
brings the throughput back. Even a command which the disk
doesn't support.
So I have a cron job which runs `hdparm -A1' once per minute.
-
next prev parent reply other threads:[~2001-03-02 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 10:32 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-02-26 20:10 ` Jeff Garzik
2001-02-26 20:58 ` Manfred Spraul
2001-03-02 21:15 ` Jeff Garzik
2001-03-02 21:03 ` I/O problem with sustained writes Collectively Unconscious
2001-03-02 23:57 ` Andrew Morton [this message]
2001-03-02 22:20 ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-03-02 22:48 ` Donald Becker
2001-02-27 6:16 ` Pat Verner
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=3AA03354.A07F5179@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=swarm@warpcore.provalue.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.