[MDEV-8963] innodb_force_recovery >= 4 won't work Created: 2015-10-18  Updated: 2015-12-15  Resolved: 2015-12-15

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - XtraDB
Affects Version/s: 10.0.21
Fix Version/s: 10.0.23

Type: Bug Priority: Minor
Reporter: 20430 Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: innodb, recovery, upstream
Environment:

Arch Linux
Linux 4.2.3-1

Issue Links:
Relates
relates to MDEV-9121 innodb_force_recovery = 6 cannot reco... Closed
relates to MDEV-8877 Inrecoverable InnoDB/XtraDB database ... Closed
Sprint: 10.1.9-1, 10.1.9-2

 Description   

This bug has been reported here https://bugs.mysql.com/bug.php?id=77654.

My InnoDB got corrupted and mariadb crashes every time i start it, so i tried using innodb_force_recovery option, values 1-3 still crash and >=4 InnoDB refuses to work:

2015-10-18 20:27:43 3068483456 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2015-10-18 20:27:43 3068483456 [Note] InnoDB: The log sequence numbers 420559692 and 420559692 in ibdata files do not match the log sequence number 21215150453 in the ib_logfiles!
2015-10-18 20:27:43 3068483456 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2015-10-18 20:27:43 3068483456 [ERROR] Plugin 'InnoDB' init function returned error.
2015-10-18 20:27:43 3068483456 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-10-18 20:27:43 3068483456 [Note] Plugin 'FEEDBACK' is disabled.
2015-10-18 20:27:43 3068483456 [ERROR] Unknown/unsupported storage engine: InnoDB
2015-10-18 20:27:43 3068483456 [ERROR] Aborting

 Comments   
Comment by Elena Stepanova [ 2015-10-20 ]

I've set affected version to 10.0 because if the upstream bug is confirmed for 5.6 InnoDB, it most likely exists in 10.0 as well.

Assigning to Jan to decide whether we want to wait for the upstream bugfix, or fix it on MariaDB side.

Comment by Jan Lindström (Inactive) [ 2015-10-28 ]

Tested that this does work with mysql-5.6.27 and we have this fix on innodb_plugin 10.0.22, but fix is not in xtradb.

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