MySQL Bugs: #66879: InnoDB: Assertion failure in thread 940 in file fsp0fsp.c line 2040

Bug #66879	InnoDB: Assertion failure in thread 940 in file fsp0fsp.c line 2040
Submitted:	19 Sep 2012 19:51	Modified:	20 Oct 2012 16:01
Reporter:	Richard Bollinger	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	5.5.21 & 5.5.25a & 5.5.27	OS:	Windows (XP Proj 32 bit)
Assigned to:		CPU Architecture:	Any

Description:
C:\Documents and Settings\Computer>mysqld --console
120919 15:39:46 [Note] Plugin 'FEDERATED' is disabled.
120919 15:39:46 InnoDB: The InnoDB memory heap is disabled
120919 15:39:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120919 15:39:46 InnoDB: Compressed tables use zlib 1.2.3
120919 15:39:46 InnoDB: Initializing buffer pool, size = 35.0M
120919 15:39:46 InnoDB: Completed initialization of buffer pool
120919 15:39:46 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
120919 15:39:46 InnoDB: Assertion failure in thread 940 in file fsp0fsp.c line 2040
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.
19:39:46 UTC - mysqld got exception 0xc0000005 ;
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.

key_buffer_size=8388608
read_buffer_size=65536
max_used_connections=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 40919 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...
641558 mysqld.exe!my_osmaperr()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
run mysqld after installation and configuration fail to start MySQL service.

It would be nice to see your my.ini file content. Please, upload the entire error log also.

Ouch! I solved my problem by deleting all the MySQL directories and files. I was surprised after I removed and reinstalled MySQL that my old data tables were still in InnoDB. I could not query them or anything because of corrupted files. But, there they were. It told me that when I Removed MySQL, that all the files were actually NOT removed. So, I did it manually. The next install worked.

You have started the server with: mysqld --console without the --defaults-file=the_path_of_my_ini_file. So I guess were conflicts among the size of files. If that the case?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".