http://bugzilla.novell.com/show_bug.cgi?id=516339
User per.jessen@enidan.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516339#c15
--- Comment #15 from Per Jessen
My finding so far:
Possibilities that came across my mind so far:
Somehow corrupted key file. If this is the case, dumping table, deleting it and recreating it should help. But as MySQL is trying fix key file after the crash (mentioned in logs) it looks like this is not very probable.
I did in fact dump the table, truncated it and have tried to reload it since. Just reloading it causes the problem, so it is in fact now very reproducable.
Some kind of race condition somewhere. This would explain why it is happening only under heavy load, but it will be hard to find and fix. Newer version differs in some mutexes so this is quite possible.
It is no longer only under heavy load, see above.
As problem seems to be MyISAM related, possible workaround may be to migrate affected table to different storage engine. For example InnoDB.
Out of the question.
Still trying to figure out what went wrong, but wanted to provide some feedback in the meantime.
Thanks, feedback much appreciated. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.