Bug #98342 Use fallocate to initialize redo logs
Submitted: 24 Jan 2020 5:55 Modified: 20 Jul 2020 8:13
Reporter: Rahul Agarkar Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.0.20 OS:Any
Assigned to: CPU Architecture:Any

[24 Jan 2020 5:55] Rahul Agarkar 
Description:
Use fallocate() to initialize the redo log files during startup to speed up the initialization.

Redo log files don’t suffer the problem on reads that data files do. If the HW crashes after the fallocate but before the write to the new pages. It doesn’t matter if the redo log files contain garbage.

How to repeat:
NA
[13 Feb 2020 14:16] Daniel Price 
Posted by developer:
 
Fixed as of the upcoming 8.0.20 release, and here's the changelog entry:

To improve server initialization speed, fallocate() is now used to
allocate space for redo log files.