Assim, depois que os arquivos de um banco de dados foram copiados com sucesso, no entanto, uma versão mais antiga dos logs do InnoDB foi transferida, o MySQL não inicializa em nada menos que innodb_force_recovery=6 . Devido a isso, não podemos converter os bancos de dados em MyIsam e voltar, já que o InnoDB está em modo somente leitura graças ao número de recuperação de força acima.
Nós temos o erro do LSN estar no futuro porque os arquivos de log do InnoDB não estão lá - os únicos que temos a partir de um backup ainda estão no passado. Tentar despejar o banco de dados durante a recuperação 6 falha, não importa o que tentemos, fornecendo o código de erro mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM {random selection of one of our tables}: Lost connection to MySQL server during query (2013)
Não temos certeza do que fazer a partir daqui, já que tentamos muitas coisas para resolvê-lo. Alguém tem alguma dica?
Se você precisar, aqui está um trecho do erro:
2017-02-08T16:22:50.463643Z 0 [ERROR] InnoDB: Page [page id: space=14, page number=5] log sequence number 65609017550 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.463646Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464047Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=4] log sequence number 66046898577 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464051Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464067Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=1] log sequence number 65610191668 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464069Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464274Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=5] log sequence number 66046898611 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464276Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464928Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=6] log sequence number 66051918727 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464934Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464944Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=7] log sequence number 66046898674 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464946Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464956Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=3] log sequence number 66027773690 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464958Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.464967Z 0 [ERROR] InnoDB: Page [page id: space=563, page number=12] log sequence number 65988073134 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.464969Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.465150Z 0 [ERROR] InnoDB: Page [page id: space=14, page number=14] log sequence number 65719956190 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.465153Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.465326Z 0 [ERROR] InnoDB: Page [page id: space=562, page number=8] log sequence number 57866129147 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.465329Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2017-02-08T16:22:50.465494Z 0 [ERROR] InnoDB: Page [page id: space=562, page number=63] log sequence number 66042781044 is in the future! Current system log sequence number 8744.
2017-02-08T16:22:50.465497Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.