On Thu, 2009-07-23 at 12:00 -0500, Eric Sandeen wrote: > Sorry I skimmed to fast, skipped over the fsck part. But: > > # mkfs.ext4 /dev/sdb3 > mke2fs 1.41.5 (23-Apr-2009) > ... > # mount /dev/sdb3 /mnt/test > # touch /mnt/test/testfile > # /root/fallocate -n -l 16m /mnt/test/testfile > # ls -l /mnt/test/testfile > -rw-r--r-- 1 root root 0 Jul 23 12:13 /mnt/test/testfile > # du -h /mnt/test/testfile > 16M /mnt/test/testfile > # umount /mnt/test > # e2fsck -f /dev/sdb3 > e2fsck 1.41.5 (23-Apr-2009) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > /dev/sdb3: 12/244800 files (0.0% non-contiguous), 37766/977956 blocks > > there doesn't seem to be a problem in fsck w/ block past EOF, or am I > missing something else? I was taking Andreas' word for it but now that you mention it, I see the same thing. Andreas, did you have a specific case in mind? -- Frank Mayhar <fmayhar@xxxxxxxxxx> Google, Inc. -- 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