All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sylvain COUTANT <sylvain.coutant@illicom.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: High CPU usage (up to server hang) under heavy I/O load
Date: Fri, 13 Aug 2004 23:16:05 +0100	[thread overview]
Message-ID: <1092435364.24960.35.camel@localhost.localdomain> (raw)
In-Reply-To: <20040813140229.4F48B2FC2C@illicom.com>

On Gwe, 2004-08-13 at 15:01, Sylvain COUTANT wrote:
> I have a problem with one server (DELL, 1 TB RAID5 + RAID0, Bi-Xeon, 8 GB
> RAM) which, sometimes, goes mad when the I/O pressure gets too high. We use
> this server as a VMWare server and as a backup server (200 GB are dedicated
> to the backup part). We have run full hardware diags and checked every
> software that runs on the system. We have been able to reproduce the problem
> once without having launched the VMWare server (so I believe this software
> is not responsible for the problem).
> 
> We have tested kernels 2.4.22 and 2.4.26. The server is running under Debian
> Woody.

Is your raid controller 64bit capable ? If you can I'd also go to a 2.6
kernel for anything > 1Gb, and definitely > 4Gb of RAM. The differences
are astounding although if your PCI I/O hardware cant do 64bit access
your box will suck whatever kernel 8)


  parent reply	other threads:[~2004-08-13 23:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 14:01 High CPU usage (up to server hang) under heavy I/O load Sylvain COUTANT
2004-08-13 15:36 ` Matt Domsch
2004-08-13 15:46   ` Sylvain COUTANT
2004-08-14  3:39     ` Tom Sightler
2004-08-15  9:11       ` Lenar Lõhmus
2004-08-15 20:30       ` Sylvain COUTANT
2004-08-16 12:43         ` Matt Domsch
2004-08-13 16:20 ` Marcelo Tosatti
2004-08-13 17:53   ` Sylvain COUTANT
2004-08-16 10:11   ` Sylvain COUTANT
2004-08-16 11:49     ` Sylvain COUTANT
2004-08-13 22:16 ` Alan Cox [this message]
2004-08-16  9:13   ` Mark Watts
2004-08-16 10:57     ` Alan Cox
2004-08-16 12:10       ` Mark Watts

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=1092435364.24960.35.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sylvain.coutant@illicom.com \
    /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.