MySQL Forums
Forum List  »  InnoDB

MySQL-server-community-5.0.41 crashed. Error number 5 means 'Input/output error'.
Posted by: fish zheng
Date: June 05, 2007 02:54AM

OS : Red Hat Enterprise Linux AS release 3
MySQL : MySQL-server-community-5.0.41-0.rhel3

After I installed the mysql-server on 05/21/2007, It works about 13 days and then crashed.
I get the same errors many times with different mysql-server version 5.1.X.
It can works but only some days about from 1 week to 3 weeks.


====================================================================
# cat /var/lib/mysql/server.err

070602 0:05:35 InnoDB: ERROR: the age of the last checkpoint is 9433654,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
070602 0:05:53 InnoDB: ERROR: the age of the last checkpoint is 9433836,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
070603 0:05:34 InnoDB: ERROR: the age of the last checkpoint is 9433564,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
InnoDB: Error: tried to read 16384 bytes at offset 0 770048.
InnoDB: Was only able to read -1.
070603 2:00:45 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
070603 02:00:45 mysqld restarted
070603 2:00:46 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...
070603 2:00:46 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 4227939145.
InnoDB: Doing recovery: scanned up to log sequence number 0 4227939145
InnoDB: Error: tried to read 327680 bytes at offset 0 196608.
InnoDB: Was only able to read 208896.
070603 2:02:35 InnoDB: Operating system error number 0 in a file operation.
InnoDB: Error number 0 means 'Success'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
070603 02:02:35 mysqld ended

====================================================================
# cat /etc/my.cnf

[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock

# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 16K
max_allowed_packet = 1M
table_cache = 4
sort_buffer_size = 64K
read_buffer_size = 256K
read_rnd_buffer_size = 256K
net_buffer_length = 2K
thread_stack = 64K

server-id = 1
default-character-set = gbk
skip-external-locking
#skip-name-resolve
skip-bdb

innodb_data_home_dir = /var/lib/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[isamchk]
key_buffer = 8M
sort_buffer_size = 8M

[myisamchk]
key_buffer = 8M
sort_buffer_size = 8M

[mysqlhotcopy]
interactive-timeout

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL-server-community-5.0.41 crashed. Error number 5 means 'Input/output error'.
10923
June 05, 2007 02:54AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.