From: Marcel van Beurden <marcel_linux-ext4@marsnix.nl>
To: linux-ext4@vger.kernel.org
Subject: Shrinking ext3 partition takes long and high CPU usage
Date: Fri, 19 Oct 2012 11:34:26 +0200 [thread overview]
Message-ID: <50811EA2.6030603@marsnix.nl> (raw)
Hi,
I'm in the process of shrinking a 900 GB ext3 partition on a USB2
connected disk using Gparted (0.5.1-1ubuntu3). The whole thing has been
running for 2 days now and I'm curious whether it will ever finish.
Right now the resize2fs (sub)process is using 99% of one 3.2GHz Xeon
core (totalling up to 32 hours of CPU time so far).
Is resize2fs being stuck and hanging forever, or is it just taking a lot
of time? I wouldn't expect resizing to be so CPU intensive.
Is there any way to check whether it is still doing anything and to
estimate when it will be done?
How corrupt will be filesystem be when I press ctrl-C?
Version of resize2fs is: 1.41.11 (14-Mar-2010)
Version of linux kernel: 2.6.32-40-generic-pae
Regards,
Marcel
next reply other threads:[~2012-10-19 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 9:34 Marcel van Beurden [this message]
2012-10-19 14:36 ` Shrinking ext3 partition takes long and high CPU usage Carlos Maiolino
2012-10-22 9:42 ` Marcel van Beurden
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=50811EA2.6030603@marsnix.nl \
--to=marcel_linux-ext4@marsnix.nl \
--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).