What happened to e4defrag relevant file and free space defrag?
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?
Signature · 6 lines
Joakim Ziegler - Supervisor de postproducción - Terminal [email protected] - 044 55 2971 8514 - 5264 0864 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 15 lines · Joakim Ziegler
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:
Quoted 7 lines
"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.
Signature · 6 lines
Joakim Ziegler - Supervisor de postproducción - Terminal [email protected] - 044 55 2971 8514 - 5264 0864 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Joakim Ziegler
Quoted 5 lines · Joakim Ziegler
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
Quoted 15 lines · Theodore Ts'o
Quoted 6 lines · Joakim Ziegler
Quoted 5 lines · Joakim Ziegler
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).
Quoted 4 lines
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.
Signature · 6 lines
Joakim Ziegler - Supervisor de postproducción - Terminal [email protected] - 044 55 2971 8514 - 5264 0864 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html