From: Mike Galbraith <efault@gmx.de>
To: david@dworf.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad command responsiveness Proliant DL 585
Date: Wed, 14 Jun 2006 11:42:41 +0200 [thread overview]
Message-ID: <1150278161.7994.13.camel@Homer.TheSimpsons.net> (raw)
In-Reply-To: <448FC1CE.9090108@dworf.com>
On Wed, 2006-06-14 at 09:59 +0200, David Osojnik wrote:
> Hello,
>
> We have a problem with four HP Proliant DL 585 servers with 4 AMD
> Opteron processors and 16Gb of memory and 3x 300Gb U320 SCSI disks and
> with all the latest firmware. we noticed bad command responsiveness in
> an production environment and poor performance (web server and mysql)
> The problem is good reproducible if creating a large file 30Gb in size with:
>
> time dd if=/dev/zero of=test.file bs=3072 count=10240000
>
> on the root partition no matter which one reiserfs, ext3
>
> what happens is I open three more console windows and do random commands
> like: "ls, w, route -n, ifconfig" but the commands freezes for random
> time (this time is from 1 minute to 15minutes!! per command execution
> time) when the command starts working (after 5minutes) i try it again
> and the command freezes again for a random time... the strange thing is
> that if one command freezes all other commands freeze too when one
> starts to work others work too. (if running top it stops refreshing for
> the lockup period)
Does top freeze if started from an mlockall(MCL_PRESENT|MCL_FUTURE)
shell running at realtime priority?
Try SysRq-T and SysRq-M during freezes to gather info about VM and task
state during freeze.
-Mike
next prev parent reply other threads:[~2006-06-14 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 7:59 David Osojnik
2006-06-14 9:42 ` Mike Galbraith [this message]
2006-06-14 19:18 ` David Osojnik
2006-06-15 6:44 ` Mike Galbraith
2006-06-15 7:38 ` David Osojnik
[not found] ` <44910E5B.50704@dworf.com>
2006-06-15 8:00 ` Mike Galbraith
2006-06-15 11:18 ` David Osojnik
2006-06-15 12:14 ` Mike Galbraith
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=1150278161.7994.13.camel@Homer.TheSimpsons.net \
--to=efault@gmx.de \
--cc=david@dworf.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®