linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joakim Ziegler <joakim@terminalmx.com>
To: Theodore Ts'o <tytso@mit.edu>
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, 03 Sep 2014 14:26:07 -0500	[thread overview]
Message-ID: <54076B4F.4020003@terminalmx.com> (raw)
In-Reply-To: <20140903190207.GJ2504@thunk.org>

On 03/09/14, 14:02, Theodore Ts'o wrote:
> 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.

Yeah, I was mostly curious about the relevant file defrag, since Akira's 
presentation from a few years back said that there were patches in review, and 
it would, I think, largely solve my problem.

-- 
Joakim Ziegler  -  Supervisor de postproducción  -  Terminal
joakim@terminalmx.com   -   044 55 2971 8514   -   5264 0864
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-09-03 19:26 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
2014-09-03 19:26     ` Joakim Ziegler [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=54076B4F.4020003@terminalmx.com \
    --to=joakim@terminalmx.com \
    --cc=a-fujita@rs.jp.nec.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).