linux-ext4 - Re: [PATCH e2fsprogs] resize2fs: avoid constantly flushing while moving blocks

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]

Message-ID: <171332777784.2749069.4830925403023907737.b4-ty@mit.edu>
Date: Wed, 17 Apr 2024 00:33:40 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4@...r.kernel.org, Anssi Hannula <anssi.hannula@....fi>
Cc: "Theodore Ts'o" <tytso@....edu>
Subject: Re: [PATCH e2fsprogs] resize2fs: avoid constantly flushing while moving blocks


On Tue, 07 Nov 2023 11:46:53 +0200, Anssi Hannula wrote:
> resize2fs block_mover() flushes data after each extent and, curiously,
> only if progress indicator is enabled, every inode_blocks_per_group
> blocks.
> 
> This significantly affects performance, e.g. on a tested large
> filesystem on top of MD-RAID6+LVM+dm-crypt these flush calls reduce the
> operation rate from approx. 500MB/s to 5MB/s, causing extremely long
> shrinking times for large size deltas (70TB in my case).
> 
> [...]

Applied, thanks!

[1/1] resize2fs: avoid constantly flushing while moving blocks
      commit: e0e6b13d0ea7330234a6fe51ec3ba13ef884735e

Best regards,
-- 
Theodore Ts'o <tytso@....edu>