| Message ID | 4ECF433C.4030604@sx.jp.nec.com |
|---|---|
| State | Accepted, archived |
| Headers | show |
On Fri, Nov 25, 2011 at 04:26:52PM +0900, Kazuya Mio wrote: > When I create a non-extent file with the maximum size in ext4, > e2fsck detects the following error: > > Pass 1: Checking inodes, blocks, and sizes > Inode 12, i_size is 4402345721856, should be 4402345721856. Fix? > > As we know, e2fsck checks the size field of the inode in pass 1. > However, in case of the ext4 with the feature of ^extent and huge_file, > the maximum file size calculated in e2fsck is less than the real one. > The patch fixes this problem. > > Signed-off-by: Kazuya Mio <k-mio@sx.jp.nec.com> Thanks, applied. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c index dbf3c94..61e3e7f 100644 --- a/e2fsck/pass1.c +++ b/e2fsck/pass1.c @@ -583,7 +583,7 @@ void e2fsck_pass1(e2fsck_t ctx) max_sizes = EXT2_NDIR_BLOCKS + EXT2_BPP(i); max_sizes = max_sizes + EXT2_BPP(i) * EXT2_BPP(i); max_sizes = max_sizes + EXT2_BPP(i) * EXT2_BPP(i) * EXT2_BPP(i); - max_sizes = (max_sizes * (1UL << i)) - 1; + max_sizes = (max_sizes * (1UL << i)); ext2_max_sizes[i - EXT2_MIN_BLOCK_LOG_SIZE] = max_sizes; } #undef EXT2_BPP
When I create a non-extent file with the maximum size in ext4, e2fsck detects the following error: Pass 1: Checking inodes, blocks, and sizes Inode 12, i_size is 4402345721856, should be 4402345721856. Fix? As we know, e2fsck checks the size field of the inode in pass 1. However, in case of the ext4 with the feature of ^extent and huge_file, the maximum file size calculated in e2fsck is less than the real one. The patch fixes this problem. Signed-off-by: Kazuya Mio <k-mio@sx.jp.nec.com> --- e2fsck/pass1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html