From: Jason Schoonover <jasons@pioneer-pra.com>
To: linux-kernel@vger.kernel.org
Subject: High load average on disk I/O on 2.6.17-rc3
Date: Fri, 5 May 2006 10:10:19 -0700 [thread overview]
Message-ID: <200605051010.19725.jasons@pioneer-pra.com> (raw)
Hi all,
I'm not sure if this is the right list to post to, so please direct me to the
appropriate list if this is the wrong one.
I'm having some problems on the latest 2.6.17-rc3 kernel and SCSI disk I/O.
Whenever I copy any large file (over 500GB) the load average starts to slowly
rise and after about a minute it is up to 7.5 and keeps on rising (depending
on how long the file takes to copy). When I watch top, the processes at the
top of the list are cp, pdflush, kjournald and kswapd.
I just recently upgraded the box, it used to run Redhat 9 with kernel 2.4.20
just fine. This problem did not show up with 2.4.20. I just recently
installed Debian/unstable on it and that's when the problems started showing
up.
Initially the problem showed up on debian's 2.6.15-1-686-smp kernel pkg, so I
upgraded to 2.6.16-1-686; same problem, I then downloaded 2.6.16.12 from
kernel.org and finally ended up downloading and compiling 2.6.17-rc3 and same
problem occurs.
The hardware is a Dell PowerEdge 2650 Dual Xeon 2.4GHZ/2GB RAM, the hard drive
controller is (as reported by lspci):
0000:04:08.1 RAID bus controller: Dell PowerEdge Expandable RAID Controller
3/Di (rev 01)
0000:05:06.0 SCSI storage controller: Adaptec RAID subsystem HBA (rev 01)
0000:05:06.1 SCSI storage controller: Adaptec RAID subsystem HBA (rev 01)
The PERC RAID configuration is four 136GB SCSI drives RAID5'd together.
Can anybody help me out here? Maybe I'm doing something wrong with the
configuration. Any help/suggestions would be great.
Thanks,
Jason Schoonover
next reply other threads:[~2006-05-05 17:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 17:10 Jason Schoonover [this message]
2006-05-06 23:03 ` bert hubert
2006-05-07 1:02 ` Jason Schoonover
2006-05-07 10:54 ` bert hubert
2006-05-07 16:50 ` Andrew Morton
2006-05-07 17:24 ` Jason Schoonover
2006-05-08 11:13 ` Erik Mouw
2006-05-08 11:22 ` Arjan van de Ven
2006-05-08 11:28 ` Russell King
2006-05-08 11:38 ` Avi Kivity
2006-05-08 12:37 ` Arjan van de Ven
2006-05-09 14:37 ` Bill Davidsen
2006-05-08 14:24 ` Martin J. Bligh
2006-05-08 14:55 ` Arjan van de Ven
2006-05-08 15:22 ` Erik Mouw
2006-05-08 15:25 ` Martin J. Bligh
2006-05-08 15:31 ` Arjan van de Ven
2006-05-08 15:42 ` Erik Mouw
2006-05-08 16:02 ` Martin J. Bligh
2006-05-08 16:02 ` Miquel van Smoorenburg
2006-05-08 16:47 ` Russell King
2006-05-08 17:04 ` Gabor Gombas
2006-05-08 17:18 ` Mike Galbraith
2006-05-09 1:57 ` Nick Piggin
2006-05-09 2:02 ` Martin Bligh
2006-05-09 2:16 ` Nick Piggin
2006-05-09 4:36 ` Arjan van de Ven
2006-05-09 4:46 ` Nick Piggin
2006-05-09 5:27 ` Hua Zhong
2006-05-09 5:03 ` David Lang
2006-05-15 7:46 ` Sander
2006-05-08 22:24 ` Bernd Eckenfels
2006-05-08 22:39 ` Lee Revell
2006-05-09 0:08 ` Peter Williams
2006-05-09 18:33 ` Bill Davidsen
[not found] <69c8K-3Bu-57@gated-at.bofh.it>
2006-05-05 23:12 ` Robert Hancock
2006-05-06 4:39 ` Jason Schoonover
2006-05-06 17:20 ` Robert Hancock
2006-05-06 18:23 ` Jason Schoonover
2006-05-06 20:01 ` Robert Hancock
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=200605051010.19725.jasons@pioneer-pra.com \
--to=jasons@pioneer-pra.com \
--cc=linux-kernel@vger.kernel.org \
/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®