[MDEV-20688] Recovery crashes after unnecessarily reading a corrupted page - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2.24, 10.3.15, 10.4.5
Fix Version/s: 10.2.28, 10.3.19, 10.4.9
Component/s: Storage Engine - InnoDB
Labels:
- corruption
- recovery

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

Transition	Time In Source Status	Execution Times

Marko Mäkelä made transition - 2019-09-27 12:19

Open

Closed

37m 28s

People

Assignee:: Thirunarayanan Balathandayuthapani

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2019-09-27 11:42

Updated:: 2020-08-21 12:58

Resolved:: 2019-09-27 12:19

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server