2012-05-24 13:35:37.714521+00:00 https://api.launchpad.net/1.0/bugs/989055 https://api.launchpad.net/1.0/~jparrott https://api.launchpad.net/1.0/maria/+milestone/5.1 https://api.launchpad.net/1.0/bugs/989055/linked_branches https://api.launchpad.net/1.0/bugs/989055/activity https://bugs.launchpad.net/bugs/989055 Jason Parrott Michael Widenius Maria 5.1 New High 2012-04-26 17:37:37.573774+00:00 bug Jason Parrott added bug attachment added Jason Parrott bug Peter (Stig) Edwards added subscriber Peter (Stig) Edwards maria: milestone Elena Stepanova maria: importance Elena Stepanova maria: assignee Elena Stepanova Jason Parrott Elena Stepanova unique_file_name,filename) || share->last_version' failed) is still observed, and there is no commit for bug #925377 in the tree history, apparently it was only pushed into 5.3. # MTR test case: --connect(con1,localhost,root,,) --perl open( DATA, ">bug925377.txt" ) || die "Couldn't open file bug925377.txt for writing: $!"; foreach my $i ( 1..100000 ) { print DATA "$i,line number $i\n"; } close( DATA ); EOF --disable_warnings DROP TABLE IF EXISTS bug925377; --enable_warnings CREATE TABLE bug925377 ( id INT PRIMARY KEY, a VARCHAR(100), INDEX(a) ) ENGINE=MyISAM; ALTER TABLE bug925377 DISABLE KEYS; LOAD DATA LOCAL INFILE 'bug925377.txt' INTO TABLE bug925377 FIELDS TERMINATED BY ','; --send ALTER TABLE bug925377 ENABLE KEYS; --connection default --let $wait_timeout=10 --let $show_statement= SHOW PROCESSLIST --let $field= State --let $condition= = 'Repair by sorting' --source include/wait_show_condition.inc SHOW TABLE STATUS LIKE 'bug925377'; --connection con1 --reap DROP TABLE bug925377; # End of MTR test case]]> Peter (Stig) Edwards /dev/null } function dbs_size { for i in {1..200} do run_cmd "SELECT table_schema , data_length , index_length FROM information_schema.TABLES WHERE table_schema='$DATABASE'" done } function table_run { IDX="$1" run_cmd "CREATE TABLE table_$IDX (\`id\` int, PRIMARY KEY (\`id\`)) ENGINE=MyISAM CHARSET=latin1" run_cmd "alter table table_$IDX disable keys" run_cmd "alter table table_$IDX enable keys" run_cmd "drop table table_$IDX" } function many_table_run { for i in {1..20} do table_run $i & done } dbs_size & many_table_run # produces in mysqld error log: # 120515 11:31:23 [ERROR] mysqld: Table './test/table_5' is marked as crashed and should be repaired # 120515 11:31:23 [ERROR] mysqld: Table 'table_5' is marked as crashed and should be repaired]]> Peter (Stig) Edwards Peter (Stig) Edwards Elena Stepanova Peter (Stig) Edwards SELECT table_schema , data_length , index_length FROM information_schema.TABLES WHERE table_schema='test'; This fails because of the the table mark as crashed error in the mysqld err log. The MTR test case in comment #2 works for me, in that it reproduces the problem of table marked as crashed. Even though I suspect the bug may be the same, I wanted to try and produce a MTR test case for the 2nd reproducer as it didn't involve "LOAD DATA ..." (or even writing any data to the tables), in the #2 comment MTR the query running while keys are disabled/enabled is SHOW TABLE STATUS LIKE 'bug925377' while in the 2nd reproducer the query is less specific (I imagine it ends up "opening for status"). I have not run it with a debug binary, if it is the same bug then please disregard it, thanks.]]> LPexportBug989055_myisam_crash.rb