linux-ext4 - >2TB file issue with e2fsck

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 18 Mar 2010 14:25:23 -0700
From:	Justin Maggard <jmaggard10@...il.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: >2TB file issue with e2fsck

Ran into an interesting issue, and thought I'd report it.  I created a
4TB file using posix_fallocate() on a freshly-created ext4 filesystem,
unmounted, and then ran e2fsck -f on it.  Using e2fsprogs 1.41.9,
e2fsck ran through with no issues.  Versions 1.41.10 and 1.41.11,
however, reported finding an error.  Output was the same for both
1.41.10 and 1.41.11:

e2fsck 1.41.10 (10-Feb-2009)
Pass 1: Checking inodes, blocks, and sizes
Inode 12, i_blocks is 8589935432, should be 840.  Fix? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

c: ***** FILE SYSTEM WAS MODIFIED *****
c: 12/90523648 files (0.0% non-contiguous), 1079543383/1448361984 blocks

I'm in the process of trying it again using dd to create the large
file instead of posix_fallocate(), but I suspect the results will be
the same.  Writing out such a huge file using dd takes a lot longer,
since as was discussed on this list a couple weeks ago, large
sequential writes on ext4 max out around 350MB/s. :)

-Justin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html