Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.2.30
Description
Hi!
When applying an incremental backup during a restore, I get the following:
2020-01-10 15:59:32 140260523783488 [Note] InnoDB: Read redo log up to LSN=49923047000576 |
2020-01-10 15:59:47 140260523783488 [Note] InnoDB: Read redo log up to LSN=49923891235328 |
2020-01-10 16:00:02 140260523783488 [Note] InnoDB: Read redo log up to LSN=49924736256512 |
2020-01-10 16:00:07 140260523783488 [Note] InnoDB: Starting a batch to recover 999452 pages from redo log. |
2020-01-10 16:00:07 0x7f8b9a071700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.30/storage/innobase/log/log0recv.cc line 1666 |
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
|
InnoDB: We intentionally generate a memory trap.
|
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ |
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mysqld startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ |
InnoDB: about forcing recovery.
|
2020-01-10 16:00:07 0x7f8b9a872700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.30/storage/innobase/log/log0recv.cc line 1652 |
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
|
InnoDB: We intentionally generate a memory trap.
|
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ |
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mysqld startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ |
InnoDB: about forcing recovery.
|