Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
This is related to bug lp:925377, but confirmed on the 5.3.6 release.
Jervin R (viiin) wrote a reproducer which I have attached (myisam_crash.rb) and confirm causes the corrupt table message. We're seeing corrupt tables on our live databases as well.
This bug appears to be present still on 5.3.6 - possibly not during ENABLE|DISABLE keys but immediately before drop. see my.cnf below and Ruby script for test case.
[mysqld]
|
basedir=/home/revin/Downloads/mariadb-5.3.6-Linux-x86_64/
|
datadir=/var/lib/mysql
|
socket=/var/lib/mysql/mysql.sock
|
user=revin
|
# Disabling symbolic-links is recommended to prevent assorted security risks
|
symbolic-links=0
|
|
collation_server = utf8_unicode_ci
|
character_set_server = utf8
|
skip-external-locking
|
#fast_index_creation = false
|
|
# 10MB ramdisk - can be ignored
|
tmpdir = /tmpfs
|
|
key_buffer = 276M
|
innodb_buffer_pool_size = 276M
|
max_allowed_packet = 16M
|
thread_stack = 256K
|
thread_cache_size = 128
|
thread_concurrency = 8
|
max_connections = 512
|
table_cache = 2048
|
myisam-recover = BACKUP
|
query_cache_limit = 1M
|
query_cache_size = 128M
|
expire_logs_days = 10
|
max_binlog_size = 100M
|
|
[mysqld_safe]
|
log-error=/var/log/mysqld.log
|
pid-file=/var/run/mysqld/mysqld.pid
|
Produces the output:
120426 11:32:39 [ERROR] mysqld: Table './test/customerXX' is marked as crashed and should be repaired