130522 12:30:15 InnoDB: error: space object of table atlassar_peresta/ps_product,
InnoDB: space id 3545 did not exist in memory. Retrying an open.
InnoDB: Error: trying to add tablespace 3545 of name './atlassar_peresta/ps_product.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 3545 of name './iraniant_2012/wp_likes.ibd' already exists in the tablespace
InnoDB: memory cache!
130522 12:30:15 InnoDB: Assertion failure in thread 140418577573632 in file btr/btr0btr.c line 136
InnoDB: Failing assertion: (ibool)!!page_is_comp(root) == dict_table_is_comp(index->table)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: MySQL :: MySQL 5.1 Reference Manual :: 184.108.40.206 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
08:00:15 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2898179 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.