From: Ted Ts'o <tytso@mit.edu>
To: "Mccauliff,
Sean D. (ARC-PX)[Lockheed Martin Space OPNS]"
<sean.d.mccauliff@nasa.gov>
Cc: linux-ext4@vger.kernel.org
Subject: Re: High CPU Utilization When Copying to Ext4
Date: Sun, 26 Jun 2011 23:05:39 -0400 [thread overview]
Message-ID: <20110627030539.GF3064@thunk.org> (raw)
In-Reply-To: <341DAA96EE3A8444B6E4657BE8A846EA4B3DA126FE@NDJSSCC06.ndc.nasa.gov>
On Sun, Jun 26, 2011 at 12:33:16PM -0500, Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS] wrote:
> Sorry if this is not the correct mailing list for ext4 questions.
-ext3-users, +linux-ext4
> I'm copying terabytes of data from an ext3 file system to a new ext4
> file system. I'm seeing high CPU usage from the processes
> flush-253:2, kworker-3:0, kworker-2:2, kworker-1:1, and kworker-0:0.
> Does anyone on the list have any idea what these processes do, why
> they are consuming so much cpu time and if there is something that
> can be done about it? This is using Fedora 15.
You're using Fedora 15, so you're using a 2.6.38 kernel, right?
How are you copying the files? Are you using cp? rsync? NFS? CIFS?
what sort of files are you copying? Are they large files, many of
small files? Are there lots of hard links? etc.
- Ted
next parent reply other threads:[~2011-06-27 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <341DAA96EE3A8444B6E4657BE8A846EA4B3DA126FE@NDJSSCC06.ndc.nasa.gov>
2011-06-27 3:05 ` Ted Ts'o [this message]
2011-06-27 9:24 ` High CPU Utilization When Copying to Ext4 Lukas Czerner
2011-06-28 18:37 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-28 20:14 ` Theodore Tso
2011-06-28 20:20 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-29 13:08 ` Theodore Tso
2011-06-30 0:01 ` Sean McCauliff
2011-06-30 2:33 ` Ted Ts'o
2011-07-08 17:08 ` Sean McCauliff
2011-07-08 17:17 ` Andi Kleen
2011-07-08 17:41 ` Sean McCauliff
2011-07-08 18:24 ` Ted Ts'o
2011-06-28 20:17 ` Andreas Dilger
2011-06-29 23:16 ` Sean McCauliff
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=20110627030539.GF3064@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sean.d.mccauliff@nasa.gov \
/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;
as well as URLs for NNTP newsgroup(s).