ib_logfile0 and ib_logfile1 got deleted
2
votes
2
answers
7898
views
After restoring from a percona-xtrabackup without a preparation step,
ib_logfile0
and ib_logfile1
were not present in the restore data. Therefor during startup the following message is observed:
140223 04:10:24 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140223 04:46:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140223 4:46:51 InnoDB: Initializing buffer pool, size = 18.0G
140223 4:46:54 InnoDB: Completed initialization of buffer pool
140223 4:46:54 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140223 4:46:54 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140223 4:46:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140223 4:46:55 InnoDB: Error: page 7 log sequence number 45 3368182252
InnoDB: is in the future! Current system log sequence number 42 975484940.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
How can I fix this?
Asked by slava
(21 rep)
Mar 6, 2014, 05:24 PM
Last activity: Sep 11, 2019, 09:24 PM
Last activity: Sep 11, 2019, 09:24 PM