[MDEV-27268] Failed InnoDB initialization leaves garbage files behind Created: 2021-12-15 Updated: 2021-12-15 Resolved: 2021-12-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8 |
| Fix Version/s: | 10.2.42, 10.3.33, 10.4.23, 10.5.14, 10.6.6, 10.7.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression-10.5 | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
The following invocation will fail, leaving behind NUL-filled ibdata1 and ib_logfile0 in InnoDB initialization.
Note: The actual minimum log file size limit is as follows:
The log must be reasonably large to prevent overrun. Only once The immediate problem here is that if an attempt to initialize InnoDB with a too small log file is made, InnoDB will leave behind NUL-filled system tablespace and log files. That needs to be fixed, to avoid confusing messages like this:
|
| Comments |
| Comment by Marko Mäkelä [ 2021-12-15 ] | |||||||||
|
After a fix, the invocation of the test will fail like this:
|