mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the

Posted 2020-10-14 技术为王

mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.

 

mysql版本：5.7.19

系统版本：centos7.3

 

由于公司断电，跑在vmware虚拟机上的mysql挂掉，无法重启

innodb_force_recovery=6
2017-11-15T12:07:25.235397+08:00 0 [Warning] ‘db‘ entry ‘sys [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T12:07:25.235408+08:00 0 [Warning] ‘proxies_priv‘ entry ‘@ [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T12:07:25.235540+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_leap_second` in the cache. Attempting to load the tablespace with space id 46
2017-11-15T12:07:25.256456+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_name` in the cache. Attempting to load the tablespace with space id 47
2017-11-15T12:07:25.258414+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone` in the cache. Attempting to load the tablespace with space id 45
2017-11-15T12:07:25.263576+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_transition_type` in the cache. Attempting to load the tablespace with space id 49
2017-11-15T12:07:25.267569+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`time_zone_transition` in the cache. Attempting to load the tablespace with space id 48
2017-11-15T12:07:25.272648+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`servers` in the cache. Attempting to load the tablespace with space id 41
2017-11-15T12:07:25.276466+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_master_info` in the cache. Attempting to load the tablespace with space id 42
2017-11-15T12:07:25.280225+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_relay_log_info` in the cache. Attempting to load the tablespace with space id 43
2017-11-15T12:07:25.286619+08:00 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`slave_worker_info` in the cache. Attempting to load the tablespace with space id 44
2017-11-15T12:07:25.292450+08:00 0 [ERROR] Error writing master configuration.
2017-11-15T12:07:25.292468+08:00 0 [ERROR] Error reading master configuration.
2017-11-15T12:07:25.294535+08:00 0 [Warning] Recovery from master pos 1065 and file mysql-bin.000003 for channel ‘‘. Previous relay log pos and relay log file had been set to 4, /data/mysql/mysql3306/logs/mysql-relay.000003 respectively.
2017-11-15T12:07:25.294643+08:00 0 [ERROR] Error writing relay log configuration.
2017-11-15T12:07:25.294656+08:00 0 [ERROR] Error reading relay log configuration.
2017-11-15T12:07:25.294983+08:00 0 [ERROR] Slave: Failed to initialize the master info structure for channel ‘‘; its record may still be present in ‘mysql.slave_master_info‘ table, consider deleting it.
2017-11-15T12:07:25.294996+08:00 0 [ERROR] Failed to create or recover replication info repositories.
2017-11-15T12:07:25.295000+08:00 0 [Note] Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.

---

http://blog.csdn.net/weiwangsisoftstone/article/details/52954228

 

-15T11:44:46.406153+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2017-11-15T11:44:46.453775+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 5M, instances = 1, chunk size = 5M
2017-11-15T11:44:46.454888+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2017-11-15T11:44:46.456582+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-11-15T11:44:46.546548+08:00 0 [Note] InnoDB: Opened 8 undo tablespaces
2017-11-15T11:44:46.546575+08:00 0 [Note] InnoDB: 8 undo tablespaces made active
2017-11-15T11:44:46.546960+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-15T11:44:46.562061+08:00 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.
2017-11-15T11:44:46.562090+08:00 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-11-15T11:44:47.062885+08:00 0 [ERROR] Plugin ‘InnoDB‘ init function returned error.
2017-11-15T11:44:47.062936+08:00 0 [ERROR] Plugin ‘InnoDB‘ registration as a STORAGE ENGINE failed.
2017-11-15T11:44:47.062945+08:00 0 [ERROR] Failed to initialize plugins.
2017-11-15T11:44:47.062951+08:00 0 [ERROR] Aborting

2017-11-15T11:44:47.062962+08:00 0 [Note] Binlog end
2017-11-15T11:44:47.063067+08:00 0 [Note] Shutting down plugin ‘MyISAM‘
2017-11-15T11:44:47.063097+08:00 0 [Note] Shutting down plugin ‘CSV‘
2017-11-15T11:44:47.063622+08:00 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete


丢失数据
2017-11-15T11:54:17.694175+08:00 0 [Note] Server socket created on IP: ‘::‘.
2017-11-15T11:54:17.696000+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=3] log sequence number 3725922 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696018+08:00 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-11-15T11:54:17.696287+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=1] log sequence number 3720522 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696300+08:00 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-11-15T11:54:17.696535+08:00 0 [ERROR] InnoDB: Page [page id: space=40, page number=2] log sequence number 3724576 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.696551+08:00 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-11-15T11:54:17.697469+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=3] log sequence number 2483079 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.697485+08:00 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-11-15T11:54:17.697809+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=1] log sequence number 2479069 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.697821+08:00 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-11-15T11:54:17.698049+08:00 0 [ERROR] InnoDB: Page [page id: space=32, page number=2] log sequence number 2482784 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.698061+08:00 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-11-15T11:54:17.700092+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.700140+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.700153+08:00 0 [Warning] ‘user‘ entry ‘[email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701714+08:00 0 [Warning] ‘db‘ entry ‘performance_schema [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701727+08:00 0 [Warning] ‘db‘ entry ‘sys [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.701881+08:00 0 [Warning] ‘proxies_priv‘ entry ‘@ [email protected]‘ ignored in --skip-name-resolve mode.
2017-11-15T11:54:17.702485+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=3] log sequence number 3754946 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702502+08:00 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-11-15T11:54:17.702718+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=1] log sequence number 3751039 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702741+08:00 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-11-15T11:54:17.702962+08:00 0 [ERROR] InnoDB: Page [page id: space=46, page number=2] log sequence number 3754946 is in the future! Current system log sequence number 2440232.
2017-11-15T11:54:17.702974+08:00 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.