http://bugzilla.novell.com/show_bug.cgi?id=516339
User mhrusecky@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=516339#c14
--- Comment #14 from Michal Hrusecky 2009-08-03 06:33:41 MDT ---
My finding so far:
According to the backtraces, MySQL crashes somewhere around bmove512 function
while working with key cache in MyISAM storage engine. Most likely it seems
like there is some kind of bad pointer (I read code around this function and
although it looks quite ugly, it looks correct).
So what is needed to fix this is to find out where the bad pointer comes from
and how something like this could happened.
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.
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.
As problem seems to be MyISAM related, possible workaround may be to migrate
affected table to different storage engine. For example InnoDB.
Still trying to figure out what went wrong, but wanted to provide some feedback
in the meantime.
--
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.