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

Innochecksum misinterprets freed undo pages

Details

    Description

      Innochecksum wrongly reports the freed undo log as exisitng undo log pages. This gives wrong sense about undo log pages
      are not being freed. To fix this issue, we introduce a new command line option

      innochecksum --skip-freed-pages
      

      or short option -r which makes innochecksum consult extent descriptor page and skip further analysis of pages that are marked as freed.

      Attachments

        Activity

          Because we can’t trust the contents of FIL_PAGE_TYPE in old InnoDB system tablespaces, I think that this logic needs to be enabled for all pages, enabled by some command line option of innochecksum, which instructs it to not report page statistics for pages that have been marked as freed.

          I would also suggest another option for validating the page number and tablespace ID inside those data pages that are not filled with NUL bytes, unless such logic already exists.

          marko Marko Mäkelä added a comment - Because we can’t trust the contents of FIL_PAGE_TYPE in old InnoDB system tablespaces, I think that this logic needs to be enabled for all pages, enabled by some command line option of innochecksum , which instructs it to not report page statistics for pages that have been marked as freed. I would also suggest another option for validating the page number and tablespace ID inside those data pages that are not filled with NUL bytes, unless such logic already exists.

          People

            thiru Thirunarayanan Balathandayuthapani
            thiru Thirunarayanan Balathandayuthapani
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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