On Wed, Jan 30, 2013 at 09:56:51AM -0600, Eric Sandeen wrote: > Ok, TBH I'd not certain why the allocator is doing just what it's doing. > There are quite a lot of larger-than-3-block free spaces. OTOH, it might be > trying for some kind of locality. Yeah, I'll bet that's what's going on. Can you show us the the inode number for each of the test files along with the filefrag -v output? What I suspect is going on is that the kernel is trying too hard to start the block allocation in the same block group which was used for the inode number. What we probably need to do is to have some hueristic where if we know there are plenty of block groups with lots of large contiguous free space, and the block group which we are preferring either because it's the same one as the inode number, or because it's where we had previously done the last block allocation for the file, and we the user requests a large fallocated region, that it's better to switch over to one of the other block groups with lots and lots of free space. - Ted -- 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
