From: Joakim Ziegler <joakim@terminalmx.com>
To: 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 13:40:42 -0500 [thread overview]
Message-ID: <540760AA.4060900@terminalmx.com> (raw)
In-Reply-To: <53F87552.6050000@terminalmx.com>
On 23/08/14, 6:04, Joakim Ziegler wrote:
> I'm using ext4 on quite large filesystems, for large image sequences. Some times
> these file systems fill up, and things get fragmented and a lot slower.
>
> When reading this presentation from Linuxcon Japan 2010:
>
> https://events.linuxfoundation.org/slides/2010/linuxcon_japan/linuxcon_jp2010_fujita.pdf
>
>
> I see references to "relevant file defrag", which would be useable for me to
> defrag image sequences to get them in sequence, specifically:
>
> "Patches related to relevant file defrag (e4defrag -r) are under review."
>
> 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."
>
> Both of these, but especially relevant file defrag, would be very useful to
> solve the problems I'm facing. What happened to the patches that were under
> review? Was anything done? Was development of these features abandoned? Is there
> any chance of any of them being implemented in the relatively near future?
Bumping this, does anyone have any idea? Also copying Akira Fujita.
--
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
next prev parent reply other threads:[~2014-09-03 18:40 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 [this message]
2014-09-03 19:02 ` Theodore Ts'o
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=540760AA.4060900@terminalmx.com \
--to=joakim@terminalmx.com \
--cc=a-fujita@rs.jp.nec.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).