* resize2fs shrink ext3 can be CPU limited
@ 2011-02-11 3:23 John Reiser
0 siblings, 0 replies; only message in thread
From: John Reiser @ 2011-02-11 3:23 UTC (permalink / raw)
To: linux-ext4
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-02-11 3:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-11 3:23 resize2fs shrink ext3 can be CPU limited John Reiser
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).