[MDEV-34830] LSN in the future is not being treated as serious corruption - Jira

XML

Word

Printable

Details

Type: Bug
Status: In Review (View Workflow)
Priority: Major
Resolution: Unresolved
Affects Version/s: 10.5, 10.6, 10.11, 11.4
Fix Version/s: 10.6, 10.11, 11.4
Component/s: Storage Engine - InnoDB
Labels:
- recovery

Description

InnoDB crash recovery is suppressing error messages about FIL_PAGE_LSN being in the future (recv_lsn_checks_on) and instead implementing a partly duplicated logic (recv_max_page_lsn). At least ever since the recovery was refactored in ~~MDEV-29911~~, we’d better always enable these checks.

Furthermore, InnoDB fails to treat a page as corrupted when it has a valid checksum but the FIL_PAGE_LSN is too large. This could lead to the database becoming increasingly more corrupted.

Attachments

Issue Links

is blocked by

MDEV-13542 Crashing on a corrupted page is unhelpful

Closed

MDEV-29911 InnoDB recovery and mariadb-backup --prepare fail to report detailed progress

Closed

MDEV-34802 Recovery fails to note some log corruption

Closed

relates to

MDEV-34879 InnoDB fails to merge the change buffer to ROW_FORMAT=COMPRESSED tables

Closed

Activity

People

Assignee:: Debarun Banerjee

Reporter:: Marko Mäkelä

Votes:: 1 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2024-08-28 12:37

Updated:: 2024-09-09 10:33

Git Integration

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