MySQL / InnoDB crash – "Número de secuencia de logging es en el futuro!"

Por lo tanto, después de que los files de una database se copyron con éxito, sin embargo, una versión anterior de los loggings de InnoDB se transfirieron, MySQL no se inicia en nada less que innodb_force_recovery=6 . Debido a esto, no podemos convertir las bases de datos en MyIsam y viceversa, ya que InnoDB está en modo de sólo lectura gracias al número de recuperación de fuerza anterior.

Tenemos el error del LSN que está en el futuro debido a los files de logging de InnoDB que no están allí – los únicos que tenemos de un respaldo son todavía manera en el pasado. Tratar de volcar la database durante la recuperación 6 falla no importa lo que intentamos, dándonos el código de error 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)

No estamos muy seguros de qué hacer desde aquí, ya que hemos intentado muchas cosas para resolverlo. Alguien tiene algún consejo?

Si lo necesitas, he aquí un fragment del error:

 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. 

  • Cómo limpiar la installation de mysql en centos
  • MySQL usuario de repente pierde algunos permissions
  • ¿Es la comunidad MySQL segura para uso en producción?
  • ¿Cómo puedo mover una database mysql a otro host, preservando los usuarios / passwords?
  • ¿Es seguro usar clientes MySQL 5.1 con el server Percona 5.5?
  • phpMyAdmin: Las funciones adicionales para trabajar con tablas vinculadas se han desactivado
  • Cómo restringir el uso de mysqlimport?
  • Migración de MySQL Server a MariaDB
  • El linux y los temas del servidor de Windows, como ubuntu, centos, apache, nginx, debian y consejos de red.