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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 9 Aug 2021 10:43:08 +0300 From: ValdikSS <iam@...dikss.org.ru> To: Theodore Ts'o <tytso@....edu> Cc: linux-ext4@...r.kernel.org Subject: Re: ext4lazyinit reads HDD data on mount since 5.13 On 09.08.2021 04:51, Theodore Ts'o wrote: > It's a new feature which optimizes block allocations for very large > file systems. The work being done by ext4lazyinit is to read the > block allocation bitmaps so we can cache the buddy bitmaps and how > fragmented (or not) various block groups are, which is used to > optimize the block allocator. Thanks for the info. To revert old behavior, the filesystem should be mounted with -o no_prefetch_block_bitmaps Is it safe to use this option with new optimizations? Should I expect only less optimal filesystem speed and no other issues?
Powered by blists - more mailing lists