Percona Server with XtraDB

Log tracking is incompatible with innodb_force_recovery=6

Reported by Laurynas Biveinis on 2012-11-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Medium
Laurynas Biveinis
5.1
Medium
Laurynas Biveinis
5.5
Medium
Laurynas Biveinis

Bug Description

--innodb_track_changed_pages=TRUE --innodb_force_recovery=6:

InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: last tracked LSN is in future. This can be caused by mismatched bitmap files.

And the server quits. The fix is to skip log tracking initialization on forced recovery.

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers