From: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
To: Micah Anderson <micah@riseup.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.6 grinds to a halt with moderate I/O
Date: Wed, 16 Jun 2004 09:43:22 +0200 [thread overview]
Message-ID: <20040616094322.559b951d@philou.gramoulle.local> (raw)
In-Reply-To: <20040615154745.GD22650@riseup.net>
Hello Micah,
Could you give more information on the Megaraid part of your setup ?
Are the i/o made on a disk/partition controlled by the megaraid ?
If no, does the same behavior occur on a plain scsi disk ?
If yes, what kind of RAID level do you use ? how many disks ?
Could you give megaraid firmware information as well as logical volume settings regarding
read,write and cache policy.
Also, is it a regression over previous kernels, like 2.6.5 or even earlier kernels ?
I've been using 2.6.3-mm3 for weeks now with DELL hardware and a megaraid controller
doing intensive i/o around the clock without any problems. The box has been just rock solid.
Thanks,
Philippe
On Tue, 15 Jun 2004 10:47:45 -0500
Micah Anderson <micah@riseup.net> wrote:
|
| Following the format from REPORTING-BUGS please see the below information.
| I unfortunately cannot subscribe to the list, but will follow the thread. I
| have searched high and low, read a number of threads somewhat tangential to
| this problem, and asked a few times in #kernelnewbies before I got to my
| wits end and now will try here. I really appreciate any insight anyone has,
| and will be happy to provide more information or additional tests
| [snip]
prev parent reply other threads:[~2004-06-16 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 15:47 Micah Anderson
2004-06-15 16:00 ` William Lee Irwin III
2004-06-15 18:19 ` Micah Anderson
2004-06-15 18:30 ` William Lee Irwin III
2004-06-16 7:43 ` Philippe Gramoullé [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=20040616094322.559b951d@philou.gramoulle.local \
--to=philippe.gramoulle@mmania.com \
--cc=linux-kernel@vger.kernel.org \
--cc=micah@riseup.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 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®