Harald, if your server does not crash, then the database probably is not corrupt. But having wrong log sequence numbers can make it corrupt. What is the error message in your case?
4.0.15 contains the check, I think 4.0.14 did not. I am wondering if there could be some bug in InnoDB which lowers the log sequence number under some condition? Or is it that people often switch old log files to their database? I may need to add another check to InnoDB which looks that the lsn stamped in the ibdata files is not ahead of the lsn in ib_logfiles. That will in most cases warn you if you put wrong log files to your database. It is very important to understand that the ib_logfiles are an integral part of the database, just like the ibdata files. One should not change log files, except through the procedure explained at http://www.innodb.com/ibman.html#Adding_and_removing. Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL support from http://www.mysql.com/support/index.html ......................... List: MySQL General Discussion « Previous MessageNext Message » From: Harald FuchsDate: September 23 2003 11:45am Subject: Re: innodb In article <[EMAIL PROTECTED]>, "Heikki Tuuri" <[EMAIL PROTECTED]> writes: > Gustavo, > ----- Original Message ----- > From: ""Gustavo A. Baratto"" <[EMAIL PROTECTED]> > Newsgroups: mailing.database.myodbc > Sent: Monday, September 22, 2003 7:33 PM > Subject: innodb >> Does anybody know what this error is all about? and how do to get rid of >> it... It started when I upgraded 4.0.13 to 4.0.15 >> >> ------- >> 030922 5:17:30 InnoDB: Error: page 12222 log sequence number 0 768348475 >> InnoDB: is in the future! Current system log sequence number 0 330400180. >> InnoDB: Your database may be corrupt. >> ------ > you have probably put old ib_logfiles to your database, and the log sequence > number in the log files is lagging behind what is in the ibdata files. I'm having the same problem as Gustavo, but the only thing I changed was replacing /usr/sbin/mysqld (SuSE Linux 8.1, kernel 2.4.18). Going back to MySQL 4.0.14 (once again, just replacing /usr/sbin/mysqld) made the messages disappear. Does that mean that my databse is maybe corrupt, but InnoDB didn't notice it until 4.0.15? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
