Bug #84485 Drop table crashes if innodb_force_recovery > 4
Submitted: 12 Jan 2017 12:24 Modified: 3 Feb 2017 19:15
Reporter: Thirunarayanan Balathandayuthapani Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:mysql-5.7.15 OS:Any
Assigned to: CPU Architecture:Any

[12 Jan 2017 12:24] Thirunarayanan Balathandayuthapani
Description:

If innodb_force_recovery is set to 6 then InnoDb does not do the redo log
roll-forward in connection with recovery. In this case, log_sys will be initalized only
and it will not have latest checkpoint information.

Checkpoint is done during shutdown even innodb_force_recovery is set to 6. So it leads
to incorrect information update in checkpoint header.

How to repeat:
-

Suggested fix:
Remove/ignore the checkpoint during shutdown when innodb_force_recovery is set to 6.
[3 Feb 2017 19:15] Daniel Price
Posted by developer:
 
Fixed as of the upcoming 5.7.18, 8.0.1 release, and here's the changelog entry:

A DROP TABLE operation raised an assertion on a server with an
innodb_force_recovery setting of 5 or 6. DROP TABLE is no longer permitted
with these innodb_force_recovery settings.
[6 Feb 2017 12:53] Erlend Dahl
Bug#84753 [ERROR] InnoDB: Failed to find tablespace | trx_sys->rseg_array[0] != __null 

Bug#82024 --innodb-force-recovery=2047 leads to trx_sys->rseg_array[0] != __null Assert

were marked as duplicates.