This is because you didn't copy innodb ibdata and ib_log files togeter. Or you forgot to stop mysqld when you remove its ib_log files.
On Sat, Feb 7, 2009 at 7:21 AM, my sql <mysql.g...@gmail.com> wrote: > WHY do I see this error when restoring my backup db : > " InnoDB: Your database may be corrupt or you may have copied the InnoDB > tablespace but not the InnoDB log files. " > > GOAL: Trying to restore mysql backup on different host > using InnoDB backup that copes the backed up files to a files sever where I > pulle them down to the new host > I place all the MySQL datafiles and InnoDB log files in the same directory > and all paths in the my.cnf files are pointing here > > upon the startup of the mysqld and the following crach recover that the > Innodb do I get tons of this errors [see below] why? > I do have the two InnoDB log files - so why does it complain that my DB > 'may' be corrupt - I don't like this message. > > Event tried with seting innodb_force_recovery = 4 but I still get the > error upon startup - why? > It doesn't look like a clean startup to me .... > > > 090206 14:56:34 InnoDB: Error: page 27060 log sequence number 4 1755884236 > InnoDB: is in the future! Current system log sequence number 4 1682795020. > InnoDB: Your database may be corrupt or you may have copied the InnoDB > InnoDB: tablespace but not the InnoDB log files. > -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
