Hi Ted, With fallocate FALLOC_FL_KEEP_SIZE option, when we write to prealloc space and if we hit ENOSPC when trying to insert the extent, we actually zero out the extent. That means we can have blocks outside i_size for an inode. I guess e2fsck currently doesn't handle this. Or should we fix kernel to update i_size to the right value if we do a zero out of the extent ? With fallocate if the prealloc area is small we also aggressively zeroout. This was needed so that a random write pattern on falloc area doesn't results in too many extents. That also can result in the above error on fsck. -aneesh -- 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
