Even with brand new log files, I got the messages again:


030923 13:37:10  InnoDB: Error: page 2621 log sequence number 0 758479545
InnoDB: is in the future! Current system log sequence number 0 330424282.
InnoDB: Your database may be corrupt.
030923 13:37:10  InnoDB: Error: page 2622 log sequence number 0 758440573
InnoDB: is in the future! Current system log sequence number 0 330424282.
InnoDB: Your database may be corrupt.
030923 13:37:10  InnoDB: Error: page 2623 log sequence number 0 758358467
InnoDB: is in the future! Current system log sequence number 0 330424282.
InnoDB: Your database may be corrupt.

Heikki Tuuri wrote:
Harald,


  030923 15:10:14  InnoDB: Error: page 53 log sequence number 6 190415140
  InnoDB: is in the future! Current system log sequence number 1

3864837242.


InnoDB: Your database may be corrupt.


what do you think is the correct log sequence number? How much do you have
data?

The pages have lsn about 16 GB or 24 GB, while the log files only have lsn
about 8 GB.

Please send me your whole .err log. That may contain clues of what has
happened.

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


.............. Heikki, many thanks for your reply.

I do well understand that I must *never* touch logfiles or datafiles,
and I did not do that.  The only thing I did was the following:

$ mysqladmin shutdown
  This was 4.0.14.  The error log said:
    InnoDB: Starting shutdown...
    InnoDB: Shutdown completed
    /usr/sbin/mysqld: Shutdown Complete
$ cp /usr/sbin/mysqld-4.0.15 /usr/sbin/mysqld
  This is bin/mysqld from "mysql-standard-4.0.15-pc-linux-i686.tar.gz"
$ rcmysql start
  Now the error log said:
    030923 15:10:12  mysqld started
    030923 15:10:14  InnoDB: Error: page 45 log sequence number 6 193108436
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 52 log sequence number 6 190390477
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 53 log sequence number 6 190415140
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 54 log sequence number 4 1256304988
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 55 log sequence number 6 190440189
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 56 log sequence number 6 190464315
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 59 log sequence number 4 1253798302
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 60 log sequence number 4 1216946799
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Error: page 61 log sequence number 4 1253798302
    InnoDB: is in the future! Current system log sequence number 1
3864837242.
    InnoDB: Your database may be corrupt.
    030923 15:10:14  InnoDB: Started
    /usr/sbin/mysqld: ready for connections.
    Version: '4.0.15-standard-log'  socket: '/var/lib/mysql/mysql.sock'
port: 3306

Now I switched back to 4.0.14:
$ mysqladmin shutdown
$ cp /usr/sbin/mysqld-max /usr/sbin/mysqld
  This is the old 4.0.14 binary, compiled by MySQL AB.
$ rcmysql start
  The error log said:
    030923 15:10:46  InnoDB: Started
    /usr/sbin/mysqld: ready for connections.
    Version: '4.0.14-Max-log'  socket: '/var/lib/mysql/mysql.sock'  port:
3306

I had 4.0.14 running for quite some time now and neither experienced
any problem nor saw anything in the error log.

The InnoDB part of my.cnf looks like this:

  innodb_data_home_dir      =
  innodb_data_file_path     =
/dev/raw/raw1:6149Mraw;/var/mysql/innodb/ibdata:100M:autoextend
  innodb_log_group_home_dir = /var/mysql/innodb.log
  innodb_log_arch_dir       = /var/mysql/innodb.log

  innodb_mirrored_log_groups      = 1
  innodb_log_files_in_group       = 3
  innodb_log_file_size            = 100M
  innodb_log_buffer_size          = 64M
  innodb_flush_log_at_trx_commit  = 2
  innodb_flush_method             = O_DSYNC
  innodb_log_archive              = 0
  innodb_buffer_pool_size         = 128M
  innodb_additional_mem_pool_size = 16M
  innodb_file_io_threads          = 4
  innodb_lock_wait_timeout        = 50

Just ask if you need more information.



-- -------------------------------------------------------------------------- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408

 Technical support web-site: http://support.superb.net
 Superb Internet Corp. "Ahead of the Rest"
 -------------------------------------------------------------------------


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to