[MDEV-27139] 32-bit systems fail to use big innodb-log-file-size Created: 2021-11-29 Updated: 2022-02-16 Resolved: 2021-12-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.5.1, 10.6.0, 10.7.0 |
| Fix Version/s: | 10.5.14, 10.6.6, 10.7.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Eugene Kosov (Inactive) | Assignee: | Eugene Kosov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
This line disallows using files bigger than 4G. The correct type should be os_offset_t. |
| Comments |
| Comment by Marko Mäkelä [ 2022-02-16 ] |
|
This regression had been introduced in 10.5.1 by this change. As far as I can tell, an attempt to use innodb_log_file_size larger than 4GiB on a 32-bit system would have resulted in a corrupted (unrecoverable) redo log. The impact probably is minor, because the log file is rarely configured to be larger than innodb_buffer_pool_size, which is limited to some 2GiB or maybe at most 3GiB on 32-bit systems. |