From: Theodore Tso <tytso@mit.edu>
To: Paul Collins <paul@burly.ondioline.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: tune2fs -I 256 -- kind of slow?
Date: Tue, 14 Oct 2008 07:17:59 -0400 [thread overview]
Message-ID: <20081014111759.GA8674@mit.edu> (raw)
In-Reply-To: <87d4i3lr3u.fsf@burly.wgtn.ondioline.org>
On Tue, Oct 14, 2008 at 05:48:05PM +1300, Paul Collins wrote:
> I just ran "tune2fs -I 256 /dev/sda3" and it took about an hour and
> forty minutes. The filesystem is about 33GiB, 3/4 full, ~85,000 inodes.
> The machine is a 2.13GHz Core 2 Duo, SATA disk. It seemed to be
> CPU-bound, soaking up a core for the whole run. Does this sound right?
>
> Running e2fsprogs 1.41.3-1 from Debian unstable.
You're not the first person to have reported this. I don't think
anyone has had a chance to look at it, but it's something we clearly
need to pay attention to --- 33 GB isn't that big of a filesystem, as
filesystems go, and an hour and a half and being CPU bound is not a
good thing.
- Ted
prev parent reply other threads:[~2008-10-14 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 4:48 tune2fs -I 256 -- kind of slow? Paul Collins
2008-10-14 11:17 ` Theodore Tso [this message]
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=20081014111759.GA8674@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=paul@burly.ondioline.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