Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.24, 10.3.15, 10.4.5
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.
Attachments
Issue Links
- is caused by
-
MDEV-12699 Improve crash recovery of corrupted data pages
-
- Closed
-
- relates to
-
MDEV-20755 InnoDB: Database page corruption on disk or a failed file read of tablespace upon prepare of mariabackup incremental backup
-
- Closed
-
-
MDEV-21572 buf_page_get_gen() should apply buffered page initialized redo log during recovery
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is caused by |
issue.field.resolutiondate | 2019-09-27 12:19:43.0 | 2019-09-27 12:19:43.275 |
Fix Version/s | 10.2.28 [ 23910 ] | |
Fix Version/s | 10.3.19 [ 23908 ] | |
Fix Version/s | 10.4.9 [ 23906 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Assignee | Marko Mäkelä [ marko ] | Thirunarayanan Balathandayuthapani [ thiru ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue relates to |
Link |
This issue causes |
Link |
This issue causes |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 100021 ] | MariaDB v4 [ 156796 ] |
As reported in
MDEV-21572, recovery still is unnecessarily reading some pages.