Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34830

LSN in the future is not being treated as serious corruption

    XMLWordPrintable

Details

    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

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35371 Missing *.cfg files with export option used in mariabackup (10.6.20)

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35618 Bogus assertion failure 'recv_sys.scanned_lsn < max_lsn + 32 * 512U' during recovery

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-37558 Multi-batch recovery discards needed doublewrite pages

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13542 Crashing on a corrupted page is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29911 InnoDB recovery and mariadb-backup --prepare fail to report detailed progress

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34802 Recovery fails to note some log corruption

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-25909 Unnecessary calls to fil_ibd_load() slow down recovery

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34879 InnoDB fails to merge the change buffer to ROW_FORMAT=COMPRESSED tables

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35226 InnoDB occasionally fails to recover a corrupted page from the doublewrite buffer

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35348 Missing FILE_CHECKPOINT(*) at * recovery

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33670 Redo log overwritten/corrupted

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 7d 4.25h
                  7d 4.25h

                  Git Integration

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