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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 09 Apr 2008 11:09:18 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	supersud501 <supersud501@...oo.de>
CC:	Calvin Walton <calvin.walton@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file

supersud501 wrote:
> Calvin Walton wrote:
>> On Tue, 2008-04-08 at 13:36 -0500, Eric Sandeen wrote:

...

>>> Do you in fact have any very large files on the disk?
>> I'm just curious - if I know for sure that I don't have any huge files
>> on my disk, would I be able to do something like use debugfs to simply
>> clear the flag?
>>
> 
> interests mee, too. and how are "huge files" defined? thought they are 
>  >4gb files?

"large" files are for ei->i_disksize > 0x7fffffffULL, or 2147483647
bytes / 2G.  This is just max offset, not block counts; i.e. completely
sparse 2g file will set this flag.

the "huge" sb flag is set if any file has i_blocks > ~0UL, or 2^32
512-byte blocks, or around 2T, but in this case I think sparseness
doesn't count; you have to actually have the blocks allocated.

-Eric

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