Timeline for How to defrag an ext4 filesystem
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2016 at 22:44 | comment | added | Tino |
@RichardMichael FYI: e2defrag -c /path only prints the first 5 fragmented files found (not even the most fragmented ones). Run e2defrag -v /path to see how it reduces extent counts.
|
|
| Dec 18, 2015 at 15:59 | vote | accept | CommunityBot | ||
| Dec 18, 2015 at 15:59 | |||||
| Dec 28, 2013 at 0:30 | comment | added | Richard Michael |
@dobey Ubuntu 12.04(.3) LTS contains extent in the ext4 stanza of the [fs_types] section in /etc/mke2fs.conf - thus, it is a "default". Though, regardless of the create-time configuration of the machine to which the filesystem is connected, you're best off to inspect the filesystem itself: tune2fs -l </dev/with/ext4> | grep extent (or look at the "Filesystem features" line in the complete tune2fs output). Mind you, I just ran e4defrag -c ... on a 100% full 1TB filesystem with extent, and there are only 5 fragmented files, and "fragmentation score" 0. YMMV.
|
|
| Apr 27, 2013 at 11:54 | vote | accept | CommunityBot | ||
| Apr 27, 2013 at 11:55 | |||||
| Jan 8, 2013 at 23:25 | comment | added | Felipe Alcacibar | The guy answes about defrag, it could be posible with e4defrag, the cuestion not specity an external journaling or not, he don't deserve a -1. | |
| Nov 23, 2012 at 20:43 | comment | added | dobey | This is really only useful on ext4 file systems that were created with -O extent, which is not the default. | |
| Nov 23, 2012 at 20:13 | history | answered | TIIUNDER | CC BY-SA 3.0 |