Bug #74187 InnoDB: Assertion failure in thread 140575349729088 in file fsp0fsp.c line 2102
Submitted: 2 Oct 2014 7:55 Modified: 22 Aug 2015 11:50
Reporter: Lutz Boldt Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.5.38-0 OS:Linux (Ubuntu)
Assigned to: CPU Architecture:Any

[2 Oct 2014 7:55] Lutz Boldt
Our Server crashs with this error-message:
141002  9:04:33 [Note] Plugin 'FEDERATED' is disabled.
141002  9:04:33 InnoDB: The InnoDB memory heap is disabled
141002  9:04:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141002  9:04:33 InnoDB: Compressed tables use zlib
141002  9:04:33 InnoDB: Initializing buffer pool, size = 256.0M
141002  9:04:33 InnoDB: Completed initialization of buffer pool
141002  9:04:33 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141002  9:04:33  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141002  9:04:33  InnoDB: Assertion failure in thread 140575349729088 in file fsp0fsp.c line 2102
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:04:33 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 = 346700 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000

How to repeat:
First, our Server crashs with this error:

[Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Initializing buffer pool, size = 16.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
[ERROR] Plugin 'InnoDB' init function returned error.
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting

After a search, we found this: http://superuser.com/questions/653953/cant-start-mysql-xampp-after-installing-on-external-... (Answer 1).
[22 Aug 2015 11:50] MySQL Verification Team
this crash is due to improperly creating innodb tablespace/subsystem from the start.  you need to recreate it from scratch (innodb log files and ibdata).