linux-ext4 - Re: e2fsck (git) on ext4: unsupported feature(s): huge

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 09 Apr 2008 20:12:52 +0200
From:	supersud501 <supersud501@...oo.de>
To:	Theodore Tso <tytso@....EDU>
CC:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file

Theodore Tso wrote:
> That patch which I just sent out passes the regression test suite, but
> it hasn't been extensively tested for actual *huge* files.
> (Specifically, files with the EXT4_HUGE_FILE_FL because they are
> larger than 2TB and so i_blocks had to be specified in units of
> filesystem blocksize, instead of units of 512 bytes.)
> 
> If you could apply the patch I just sent out and then run "e2fsck -nf
> /dev/sdXXX" and let me know you get, that would be much appreciated.
> 


with this patch (and huge_files enabled) i get much more errors 
(>1000++) of the following type:

inode x, i_blocks is y, should be y/8
inoda x+1, iblocks is z, should be z/8
.....

for example:

Inode 32538663, i_blocks is 8, should be 1.  Fix? no
Inode 32538664, i_blocks is 8, should be 1.  Fix? no
Inode 32538665, i_blocks is 8, should be 1.  Fix? no
Inode 32538666, i_blocks is 40, should be 5.  Fix? no
Inode 32538667, i_blocks is 32, should be 4.  Fix? no
Inode 32538668, i_blocks is 8, should be 1.  Fix? no
Inode 32538669, i_blocks is 8, should be 1.  Fix? no
Inode 32538670, i_blocks is 8, should be 1.  Fix? no
....
Inode 32587785, i_blocks is 17320, should be 2165.  Fix? no
Inode 32587786, i_blocks is 16936, should be 2117.  Fix? no
Inode 32587787, i_blocks is 120, should be 15.  Fix? no 
<------------ there are also gaps, not always x+1
Inode 32604181, i_blocks is 8, should be 1.  Fix? no
Inode 32604161, i_blocks is 18624, should be 2328.  Fix? no
Inode 32604162, i_blocks is 19400, should be 2425.  Fix? no
Inode 32604163, i_blocks is 18800, should be 2350.  Fix? no
Inode 32604164, i_blocks is 16488, should be 2061.  Fix? no
Inode 32604165, i_blocks is 17832, should be 2229.  Fix? no
Inode 32604166, i_blocks is 17880, should be 2235.  Fix? no
Inode 32604167, i_blocks is 20560, should be 2570.  Fix? no
Inode 32604168, i_blocks is 20480, should be 2560.  Fix? no
Inode 32604169, i_blocks is 18224, should be 2278.  Fix? no

not good?

--
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