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

Error "Log sequence number at the start XXX and the end 0 do not match" for PAGE_COMPRESSED tables

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.22
    • 10.1.23
    • Backup
    • None

    Description

      Tables with page compression may show errors during backup:

      xtrabackup: Generating a list of tablespaces
      170224 09:38:15 [01] Copying ./ibdata1 to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/ibdata1
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Page 65 is a doublewrite buffer page, skipping.
      InnoDB: Log sequence number at the start 1619866 and the end 0 do not match.
      [01] xtrabackup: Page 74 is a doublewrite buffer page, skipping.
      InnoDB: Log sequence number at the start 1621444 and the end 0 do not match.
      [01] xtrabackup: Page 75 is a doublewrite buffer page, skipping.
      170224 09:38:15 [01]        ...done
      170224 09:38:15 [01] Copying ./mysql/innodb_table_stats.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/innodb_table_stats.ibd
      170224 09:38:15 [01]        ...done
      170224 09:38:15 [01] Copying ./mysql/innodb_index_stats.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/innodb_index_stats.ibd
      170224 09:38:15 [01]        ...done
      170224 09:38:15 [01] Copying ./mysql/gtid_slave_pos.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/mysql/gtid_slave_pos.ibd
      170224 09:38:15 [01]        ...done
      170224 09:38:15 [01] Copying ./test/t.ibd to /home/a/farm/m9-bb-10.1-wlad-xtrabackup/bkup/test/t.ibd
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      170224 09:38:16 >> log scanned up to (1621451)
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Database page corruption detected at page 1, retrying...
      InnoDB: Log sequence number at the start 1616868 and the end 0 do not match.
      [01] xtrabackup: Error: failed to read page after 10 retries. File ./test/t.ibd seems to be corrupted.
      [01] xtrabackup: Error: xtrabackup_copy_datafile() failed.
      

      I can easily reproduce the problem by injecting "do sleep(5);" into xb_page_compress.test before --backup command

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            anikitin Andrii Nikitin (Inactive)
            Votes:
            0 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.