[MDEV-9121] innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty Created: 2015-11-12  Updated: 2016-04-27  Resolved: 2016-04-27

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.8
Fix Version/s: 10.1.14

Type: Bug Priority: Major
Reporter: Johan Kooijman Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 3
Labels: upstream

Issue Links:
Relates
relates to MDEV-8963 innodb_force_recovery >= 4 won't work Closed
Sprint: 10.1.11, 10.1.14

 Description   

Innodb force recovery settings prevent its own recovery. In innodb_force_recovery=6 and read only mode, no reason to expect change or doublewrite buffers to be empty. It does however complain about the change buffer not being empty:

[ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!

Same bug in MySQL:
https://bugs.mysql.com/bug.php?id=77476

 Comments   
Comment by Jan Lindström (Inactive) [ 2015-11-16 ]

Could this be because of MDEV-8963, but that should be fixed on innodb_plugin and MySQL 5.6.27 and MariaDB 10.1.9 (to be released) ?

Comment by Jan Lindström (Inactive) [ 2016-04-27 ]

commit 071ae303bd7ad6ce71f05a25695cd0e9fcef112c
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Wed Apr 27 11:07:43 2016 +0300

MDEV-9121: innodb_force_recovery = 6 cannot recover ANY DATA when
change buffer not empty

Fix: Allow not empty change buffer when innodb_force_recovery >= 5
and output only a warning to error log.

Note: Before using force recovery you should always take backup
of your database.

Generated at Thu Feb 08 07:32:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.