What to do if MySQL started with InnoDB _ Force _ recovery?
Anyway, if MySQL started with innodb_force_recovery=6 go ahead and dump the databases with –order-by-primary and possibly with –skip-lock-tables. Then stop MySQL, move datadir to a safe place and re-create the databases from scratch. If mysqldump crashes then corruption is too severe for innodb_force_recovery.
Is the non-zero InnoDB Force recovery dangerous?
Non-zero innodb_force_recovery is a dangerous zone and you should be careful increasing its value. Yes, 6 may corrupt your data permanently, but what other options do you have if MySQL doesn’t start with lower values?
How to fix a corrupted InnoDB file cache?
InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table.
How to report InnoDB corruption in MySQL?
InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace.
What to do if your InnoDB table is corrupt?
If you suspect or find corruption in InnoDB tables, examine the MySQL Server error log to find relevant information about specific InnoDB errors. The error log will help you understand: If the table gets corrupt due to database page corruption. A corrupt page in MySQL database can lead to corruption in a db table.
How to force InnoDB storage engine to start up?
In such cases, you can use the innodb_force_recovery option to force the InnoDB storage engine to start up while preventing background operations from running, so that you can dump your tables. For example, you can add the following line to the [mysqld] section of your option file before restarting the server: