On Fri, Aug 07, 2009 at 02:08:40PM -0500, Eric Sandeen wrote: > > Ah that crossed my mind, but since so many other e2fsprogs tools > coalesce adjacent extents and report "1" I figured e2fsck was too > (though I didn't look...) No, actually e2fsck counts non-contiguous only when the extent is non-adjacent to the previous extent. What we may want to do though is to create some other statistic which is something like "file has more than one contiguous run of blocks and one or more contiguous runs of blocks is smaller than 512 blocks". This will take into account that for very large files small amounts of non-contiguousness is acceptable, although certainly not ideal. But if we report both number of non-contiguous files, and number of fragmented files, it might be a good way of reflecting this. We really do need to improve the ext4's block allocator, though. What we have here is definitely that needs improving. Personally, I think free space fragmentation problem caused by small files should be higher priority, since although it isn't as blindly obvious by people running e2fsprogs, in the long run the free space fragmentation will cause files to get fragmented very badly when the filesystem ages and as it gets full. - 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
