From: John Reiser <jreiser@bitwagon.com>
To: linux-ext4@vger.kernel.org
Subject: resize2fs shrink ext3 can be CPU limited
Date: Thu, 10 Feb 2011 19:23:54 -0800 [thread overview]
Message-ID: <4D54ABCA.9020700@bitwagon.com> (raw)
Hi,
When I use resize2fs to shrink a 153GB ext3 from about 53% full
to about 55% of its original size (thus becoming about 98% full),
then Pass 3, Scanning inode table, is CPU limited and a significant
fraction of elapsed wall-clock time (tens of minutes out of more than
an hour). Being CPU-limited for such a duration seems peculiar to me.
The behavior is reproducible. The details are at
https://bugzilla.redhat.com/show_bug.cgi?id=676683
including reports from oprofile.
resize2fs 1.41.12 (17-May-2010)
input: 1071971/9863168 files (0.1% non-contiguous), 21597266/39423744
output: The filesystem on /dev/sdc2 is now 22989038 blocks long.
real 69m52.167s
user 26m29.431s
sys 2m3.456s
[I'm not subscribed to this mailing list.]
--
John Reiser, jreiser@BitWagon.com
reply other threads:[~2011-02-11 3:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D54ABCA.9020700@bitwagon.com \
--to=jreiser@bitwagon.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).