[MDEV-20688] Recovery crashes after unnecessarily reading a corrupted page Created: 2019-09-27 Updated: 2020-08-21 Resolved: 2019-09-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.24, 10.3.15, 10.4.5 |
| Fix Version/s: | 10.2.28, 10.3.19, 10.4.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | corruption, recovery | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
The test encryption.innodb-redo-badkey was accidentally disabled until recently. Once it was enabled, it started failing randomly. According to thiru, the crash occurs when recovery reads a corrupted page (or a page that cannot be decrypted) for which no redo log has been buffered, via the read-ahead mechanism. In this case, recovery should simply ignore the corrupted page. |
| Comments |
| Comment by Marko Mäkelä [ 2020-03-09 ] |
|
As reported in |