From: Theodore Ts'o <tytso@mit.edu>
To: Joakim Ziegler <joakim@terminalmx.com>
Cc: linux-ext4@vger.kernel.org, Akira Fujita <a-fujita@rs.jp.nec.com>
Subject: Re: What happened to e4defrag relevant file and free space defrag?
Date: Wed, 3 Sep 2014 15:02:07 -0400 [thread overview]
Message-ID: <20140903190207.GJ2504@thunk.org> (raw)
In-Reply-To: <540760AA.4060900@terminalmx.com>
On Wed, Sep 03, 2014 at 01:40:42PM -0500, Joakim Ziegler wrote:
> On 23/08/14, 6:04, Joakim Ziegler wrote:
> >
> >Also, about free space defrag, it says:
> >
> >"Implement free space defragmentation (e4defrag -f). We might implement this
> >feature when the relevant defrag development is completed."
The e4defrag is in e2fsprogs, and the code is still getting maintained
and improved. Dmitry Monakhov has in particular added a lot of
"torture tests", and found a number of race conditions in the
underlying kernel code. He recently also sent a code refactor of the
kernel code which significantly improved it and (shrank the size of
ext4 by 550 lines of code).
That being said, there hasn't been any real feature development for
e4defrag in quite some time. There has been some discussion about
what the kernel API's might be to support this feature, but there has
never been a finalized API proposal, let alone an implementation.
Cheers,
- Ted
next prev parent reply other threads:[~2014-09-03 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 11:04 What happened to e4defrag relevant file and free space defrag? Joakim Ziegler
2014-09-03 18:40 ` Joakim Ziegler
2014-09-03 19:02 ` Theodore Ts'o [this message]
2014-09-03 19:26 ` Joakim Ziegler
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=20140903190207.GJ2504@thunk.org \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.com \
--cc=joakim@terminalmx.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).