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]

Message-ID: <20080409161117.GB26924@mit.edu>
Date:	Wed, 9 Apr 2008 12:11:17 -0400
From:	Theodore Tso <tytso@....EDU>
To:	supersud501 <supersud501@...oo.de>
Cc:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file

On Wed, Apr 09, 2008 at 11:15:24AM +0200, supersud501 wrote:
>
> ah ok, so i know what's up - seems i've to wait until fixing it. just 
> wanted to do it, because syslog said "maximum mount time reached, running 
> is recommended". so no need to hurry ;)

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.

In answer to question of how to determine if you actually *have* any
large files, the simplest thing to do is to use debugfs to temporarily
remove huge_file feature:

debugfs -w /dev/sdXXX               <------- disable the huge_file feature
debugfs: features ^huge_file
debugfs: quit

e2fsck -nf /dev/sdXXX

debugfs -w /dev/sdXXX               <------- re-enable the huge_file feature
debugfs: features huge_file
debugfs: quit

If you see error messages about i_blocks values being wrong (with the
huge_file feature disabled), then the inodes that are referenced are
the ones that have the huge_file flag set.

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