linux-ext4 - Re: Suggestion: don't default to ext4 lazy init (or warn about it)

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

Date:   Mon, 13 Nov 2017 12:08:55 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     Eduard Rozenberg <edrozenberg@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: Suggestion: don't default to ext4 lazy init (or warn about it)

On Mon, Nov 13, 2017 at 07:00:38AM -0800, Eduard Rozenberg wrote:
> As I understand:
> * There is no way to force it to speed up

It is possible to speed it up.  Unmount the flie system, and then
mount it with the additional mount option "init_itable=0".  From
Documentation/filesystems/ext4.txt:

init_itable=n		The lazy itable init code will wait n times the
			number of milliseconds it took to zero out the
			previous block group's inode table.  This
			minimizes the impact on the system performance
			while file system's inode table is being initialized.


Hope this helps,

						- Ted