Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.21
-
Arch Linux
Linux 4.2.3-1
-
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