From: Paolo Ornati <ornati@fastwebnet.it>
To: Brice Figureau <brice+lklm@daysofwonder.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sluggish system while copying large files.
Date: Fri, 13 Oct 2006 16:14:21 +0200 [thread overview]
Message-ID: <20061013161421.7ecba339@localhost> (raw)
In-Reply-To: <1160747774.7929.53.camel@localhost.localdomain>
On Fri, 13 Oct 2006 15:56:14 +0200
Brice Figureau <brice+lklm@daysofwonder.com> wrote:
> I have a brand new Dell 2850 biXeon x86_64 with a Perc4e/Di (megaraid)
> RAID card with two hardware RAID1 volumes (sda and sdb, ext3 on top of
> LVM2, io scheduler deadline).
>
> This machine runs 2.6.18 and is used as a mysql server.
>
> Whenever I cp large files (for instance during backup) from one volume
> to the other, the system becomes really sluggish.
I used to have this problem and it seems that 2.6.19-rc1 and later
kernels are better (at least for me).
--
Paolo Ornati
Linux 2.6.19-rc1-g9eb20074 on x86_64
next prev parent reply other threads:[~2006-10-13 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 13:56 Sluggish system while copying large files Brice Figureau
2006-10-13 14:14 ` Paolo Ornati [this message]
2006-10-18 15:09 ` Chris Mason
2006-10-23 9:40 ` Brice Figureau
2006-10-23 11:29 ` Chris Mason
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=20061013161421.7ecba339@localhost \
--to=ornati@fastwebnet.it \
--cc=brice+lklm@daysofwonder.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