Activity log for bug #911529

Date Who What changed Old value New value Message
2012-01-04 00:11:51 Sworddragon bug added bug
2012-05-14 16:28:19 Adam Porter bug added subscriber Adam Porter
2013-12-01 23:19:25 Launchpad Janitor e2fsprogs (Ubuntu): status New Confirmed
2013-12-01 23:45:28 GRbit bug added subscriber GRbit
2015-10-08 19:34:36 Ken Sharp tags i386 precise
2015-10-08 21:14:23 GRbit description I'm using Ubuntu 12.04 dev with e2fsprogs 1.42~WIP-2011-10-16-1ubuntu1. I wanted to defragment a big file (~9 GB) but sometimes e4defrag does nothing because it thinks the file is optimized and a few seconds later it defragments the file and is reducing the most times the extents of this file. Here is an example: Command: e4defrag -v '/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi' Result: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 71 -> 71 [ OK ] The file was'nt defragmented and directly after this I used the same command again and got: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 71 -> 69 [ OK ] The file was now defragmented. I tried the command again: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 69 -> 69 [ OK ] The file wasn't defragmented but on the next try: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 69 -> 68 [ OK ] The file was defragmented and the behaviour on the last try was a little different: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 68 -> 68 [ OK ] The extents wasn't reduced but the file was defragmented which needed some minutes. I don't know why e4defrag is sometimes defragmenting an already previously defragmented file and sometimes not. And why aren't the extents reduced to the minimum size possible on the first try? I'm using Ubuntu 12.04 dev with e2fsprogs 1.42~WIP-2011-10-16-1ubuntu1. I wanted to defragment a big file (~9 GB) but sometimes e4defrag does nothing because it thinks the file is fully optimized (I guess). But a few seconds later, when I try to run defragmetation again, it decrease number of fragments. Here is an example: ~ $ e4defrag -v '/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi' Result: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 71 -> 71 [ OK ] The file wasn't defragmented at all, but immediately after this I used the same command again and here what I've got: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 71 -> 69 [ OK ] The file now was defragmented a little. I tried the command again: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 69 -> 69 [ OK ] The file wasn't defragmented but on the next try: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 69 -> 68 [ OK ] The file was defragmented. After the next try: [1/1]/virtualbox/VirtualBox VMs/Ubuntu 32 Bit/Ubuntu 32 Bit.vdi: 100% extents: 68 -> 68 [ OK ] The number of extents wasn't reduced but as the programm says the file was defragmented, and it needs couple minutes to run. I don't know why e4defrag is sometimes defragmenting an already previously defragmented file and sometimes not. And why aren't the extents reduced to the minimum size possible on the first try? It think at least there must be an option to fully defrag. Or, for example, option to set minimum size of fragmented slice or something like that