From: Theodore Tso <tytso@mit.edu>
To: Jonathan Bastien-Filiatrault <joe@x2a.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: tune2fs -I seems dangerous
Date: Thu, 4 Dec 2008 20:25:23 -0500 [thread overview]
Message-ID: <20081205012523.GD1323@mit.edu> (raw)
In-Reply-To: <4938645C.5010601@x2a.org>
On Thu, Dec 04, 2008 at 06:14:36PM -0500, Jonathan Bastien-Filiatrault wrote:
> I have had a similar experience converting from 128 to 256 bytes inodes.
> After a while, tune2fs -I would simply stop doing IO and using a lot of
> CPU with a few IO bursts every half-hour or so. This is on a recent/fast
> x86-64 computer. I had to cancel the thing after leaving it running for
> over 24 hours.
The speed problems have been reported and mostly addressed in the
e2fsprogs git repository. There's one more patch that should
completely solve the tune2fs -I performance problem, but I haven't had
time to audit the patch just yet. It is on my to do list.
- Ted
next prev parent reply other threads:[~2008-12-05 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 22:26 tune2fs -I seems dangerous Eric Sandeen
2008-12-04 23:14 ` Jonathan Bastien-Filiatrault
2008-12-05 1:25 ` Theodore Tso [this message]
2008-12-05 1:24 ` Theodore Tso
2008-12-05 3:08 ` Eric Sandeen
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=20081205012523.GD1323@mit.edu \
--to=tytso@mit.edu \
--cc=joe@x2a.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).