Log tracking is incompatible with innodb_force_recovery=6

Bug #1083596 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.

Related branches

lp:~laurynas-biveinis/percona-server/BT-16274-bug1083596-5.1
Merged into lp:percona-server/5.1 at revision 521
Stewart Smith (community): Approve on 2013-01-11
lp:~laurynas-biveinis/percona-server/BT-16274-bug1083596-5.5
Merged into lp:percona-server/5.5 at revision 414
Stewart Smith (community): Approve on 2013-01-11
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers