-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have mysql 4.0.15 on a dual Pentium IV machine. It has been running well, though in my logs I get the following error:
030916 17:30:21 InnoDB: Error: page 120855 log sequence number 11 2122008369 InnoDB: is in the future! Current system log sequence number 0 100503279. InnoDB: Your database may be corrupt. 030916 17:30:21 InnoDB: Error: page 120865 log sequence number 11 2188448346 InnoDB: is in the future! Current system log sequence number 0 100503279. InnoDB: Your database may be corrupt. 030916 17:30:21 InnoDB: Error: page 484453 log sequence number 11 4129083213 InnoDB: is in the future! Current system log sequence number 0 100509548. InnoDB: Your database may be corrupt. 030916 17:30:21 InnoDB: Error: page 312065 log sequence number 11 2188448335 InnoDB: is in the future! Current system log sequence number 0 100510501. InnoDB: Your database may be corrupt. 030916 17:30:21 InnoDB: Error: page 650421 log sequence number 11 2217210341 InnoDB: is in the future! Current system log sequence number 0 100513844. InnoDB: Your database may be corrupt. 030916 17:30:22 InnoDB: Error: page 202 log sequence number 12 490783 InnoDB: is in the future! Current system log sequence number 0 100530472. InnoDB: Your database may be corrupt. 030916 17:30:22 InnoDB: Error: page 423590 log sequence number 12 409288 InnoDB: is in the future! Current system log sequence number 0 100532546. InnoDB: Your database may be corrupt. 030916 17:30:22 InnoDB: Error: page 496361 log sequence number 11 2897456634 InnoDB: is in the future! Current system log sequence number 0 100551320. InnoDB: Your database may be corrupt. 030916 17:30:22 InnoDB: Error: page 278587 log sequence number 12 141045159 InnoDB: is in the future! Current system log sequence number 0 100552304. InnoDB: Your database may be corrupt. ... Over and over again....
This does not affect the working of the DB, but I feel that it might in the future. Is there a recommended course of action to fix it? If worse come to worse, I can just do a mysqldump on the data and start over. I was wondering if there was a better course of action, though...
My ibdata file is 19GB large. Is that a problem?
My cnf is as follows: # The MySQL server [mysqld] port = 3306 socket = /tmp/mysql.sock skip-locking set-variable = key_buffer=32M set-variable = max_allowed_packet=16M set-variable = table_cache=64 set-variable = sort_buffer=1M set-variable = net_buffer_length=8K set-variable = myisam_sort_buffer_size=8M log-bin server-id = 1 set-variable = max_allowed_packet=16M
# Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables #set-variable = bdb_cache_size=4M #set-variable = bdb_max_lock=10000
# Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /usr/local/mysql/data/ innodb_data_file_path = ibdata1:300M:autoextend innodb_log_group_home_dir = /usr/local/mysql/data/ innodb_log_arch_dir = /usr/local/mysql/data/ #innodb_force_recovery = 6
# You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high set-variable = innodb_buffer_pool_size=1000M set-variable = innodb_additional_mem_pool_size=100M # Set .._log_file_size to 25 % of buffer pool size set-variable = innodb_log_file_size=50M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 set-variable = innodb_lock_wait_timeout=50
Thanks for any help you can give me.
Dave - -- David Bernick Senior Engineer - Legal Computer Solutions [EMAIL PROTECTED]
As Will Rogers would have said, "There is no such things as a free variable." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/Z4iXzR9WeS6DURURAilBAJ4xng3+pCLoQynnc+PBS26jy15zkACdGklM 64k39wIUUpJ27X6v7TOGL/I= =2Y9+ -----END PGP SIGNATURE-----
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
