On Friday 17 July 2009 23:14:44 Andreas Dilger wrote: > > Yeah, but even the file in /tmp/nd got 3 extents. my file is 1142 blocks > > and my mb_groups says 2**9 is the highest possible value. So I guess I > > will indeed try to create the file system from scratch to test the > > allocator for real. > > The defrag code needs to become smarter, so that it finds small files > in the middle of freespace and migrates those to fit into a small gap. > That will allow larger files to be defragged once there is large chunks > of free space. Is there a way that user space can hint the allocator to fill these gaps? I don't see any obvious way. Relying on the allocator not to make matters worse might be enough, but it doesn't sound ideal. Unless something urgent comes up I might actually continue experiment next week :) My resize2fs defrag worked pretty well actually, but then again I did it on an offline copy and it won't work for online that way. Greetings, Stephan -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
