https://bugzilla.kernel.org/show_bug.cgi?id=15742 Summary: Fallocated extents handled incorrectly if beyond i_size Product: File System Version: 2.5 Kernel Version: v2.6.25 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: ext4 AssignedTo: fs_ext4@xxxxxxxxxxxxxxxxxxxx ReportedBy: dmonakhov@xxxxxxxxxx Regression: No bad commit: 3977c965ec35ce1a7eac988ad313f0fc9aee9660 Zerrout trick allow us to optimize cases where it is more reasonable to explicitly zeroout extent and mark it as initialized instead of splitting to several small ones. But this optimization is not acceptable is extent is beyond i_size Because it is not possible to have initialized blocks after i_size. Fsck treat this as incorrect inode size. #TESTCASE mkfs.ext4 /dev/sdb1 mount /dev/sdb1 /mnt ./falloc_test /mnt/F1 umount /mnt fsck.ext4 -f /dev/sdb1 fsck.ext4 -f /dev/sdb1 e2fsck 1.41.9 (22-Aug-2009) Pass 1: Checking inodes, blocks, and sizes Inode 12, i_size is 1, should be 40960. Fix<y>? no --- Comment #1 from Dmitry Monakhov <dmonakhov@xxxxxxxxxx> 2010-04-09 17:20:56 --- Created an attachment (id=25931) --> (https://bugzilla.kernel.org/attachment.cgi?id=25931) testcase -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
