mariadb/mysql-test/suite/mariabackup/innodb_redo_overwrite.opt at af52a0e516aa044b7fcdf91b3d2a7036c6c7ae9f - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-17 20:42:30 +01:00

Vlad Lesin 0a224edc3e MDEV-23711 make mariabackup innodb redo log read error message more clear

log_group_read_log_seg() returns error when:

1) Calculated log block number does not correspond to read log block
number. This can be caused by:
  a) Garbage or an incompletely written log block. We can exclude this
  case by checking log block checksum if it's enabled(see innodb-log-checksums,
  encrypted log block contains checksum always).
  b) The log block is overwritten. In this case checksum will be correct and
  read log block number will be greater then requested one.

2) When log block length is wrong. In this case recv_sys->found_corrupt_log
is set.

3) When redo log block checksum is wrong. In this case innodb code
writes messages to error log with the following prefix: "Invalid log
block checksum."

The fix processes all the cases above.

2020-09-21 12:29:52 +03:00

1 line

73 B

Text

Raw Blame History

--loose-innodb-log-file-size=1048576 --loose-innodb-log-files-in-group=2