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

Log sequence numbers do not match during backup

    XMLWordPrintable

    Details

      Description

      Backup fails for different tables (usually small, not always the same, and sometimes it completes successfully), with messages like these:

      ...
      2019-12-20  2:50:05 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      [01] mariabackup: Database page corruption detected at page 5, retrying...
      2019-12-20  2:50:05 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:05 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      2019-12-20  2:50:06 140619606296320 [Note] InnoDB: Log sequence number at the start 1919250543 and the end 1933193007 do not match
      [01] mariabackup: Error: failed to read page after 10 retries. File ./db/table.ibd seems to be corrupted.
      [01] mariabackup: Error: xtrabackup_copy_datafile() failed.
      [01] mariabackup: Error: failed to copy datafile.
      

      The table can be read and rebuilt, and next time backup does not fail on this same table.

      innochecksum gives something like these for affected tables:

      openxs@ao756:/tmp$ ~/dbs/maria10.2/bin/innochecksum -v -i -S /tmp/tt.ibd
       
      Variables (--variable-name=value)
      and boolean options {FALSE|TRUE} Value (after reading options)
      --------------------------------- ----------------------------------------
      verbose TRUE
      count FALSE
      start-page 0
      end-page 0
      page 0
      strict-check crc32
      no-check FALSE
      allow-mismatches 0
      write crc32
      page-type-summary TRUE
      page-type-dump (No default value)
      per-page-details TRUE
      log (No default value)
      leaf FALSE
      merge 0
      page 0 page 1 page 2 page 3 index id=15027 page 3 leaf 0 n_recs 3 data_bytes 66
      page 4 index id=15028 page 4 leaf 1 n_recs 13 data_bytes 307
      page 5 index id=15027 page 5 leaf 1 n_recs 2 data_bytes 52
      97
      page 6 index id=15027 page 6 leaf 1 n_recs 6 data_bytes 13714
      page 7 index id=15027 page 7 leaf 1 n_recs 5 data_bytes 9779
      Fail: page::8 invalid
      Exceeded the maximum allowed checksum mismatch count::1 current::0

      So it's not only mariabackup code that considers the table problematic.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              valerii Valerii Kravchuk
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: