MySQL Bugs: #60264: Crash because of AssertionError in fsp0fsp.c

Bug #60264	Crash because of AssertionError in fsp0fsp.c
Submitted:	26 Feb 2011 13:12	Modified:	15 May 2011 17:48
Reporter:	Martin Kirchner	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.5.9	OS:	Windows (Win 7 64 bit)
Assigned to:		CPU Architecture:	Any

Description:
mysqld crashes.
The log contains the following output:

110226 13:25:44 [Note] Plugin 'FEDERATED' is disabled.
110226 13:25:44 InnoDB: The InnoDB memory heap is disabled
110226 13:25:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
110226 13:25:44 InnoDB: Compressed tables use zlib 1.2.3
110226 13:25:45 InnoDB: Initializing buffer pool, size = 87.0M
110226 13:25:45 InnoDB: Completed initialization of buffer pool
110226 13:25:45 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!
110226 13:25:45  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...
110226 13:25:45  InnoDB: Assertion failure in thread 5144 in file ..\..\..\mysql-5.5.9\storage\innobase\fsp\fsp0fsp.c line 2101
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.
110226 13:25:45 - 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 = 36416 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...
000000013F61626C    mysqld.exe!fseg_inode_get()[fsp0fsp.c:2101]
000000013F616557    mysqld.exe!fseg_n_reserved_pages()[fsp0fsp.c:2436]
000000013F5D94AE    mysqld.exe!ibuf_init_at_db_start()[ibuf0ibuf.c:550]
000000013F634B4C    mysqld.exe!dict_boot()[dict0boot.c:450]
000000013F5B2FEA    mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1699]
000000013F5A9890    mysqld.exe!innobase_init()[ha_innodb.cc:2477]
000000013F382666    mysqld.exe!ha_initialize_handlerton()[handler.cc:462]
000000013F37C002    mysqld.exe!plugin_initialize()[sql_plugin.cc:1063]
000000013F381279    mysqld.exe!plugin_init()[sql_plugin.cc:1349]
000000013F36BC47    mysqld.exe!init_server_components()[mysqld.cc:3869]
000000013F36C7D8    mysqld.exe!win_main()[mysqld.cc:4433]
000000013F36CC38    mysqld.exe!mysql_service()[mysqld.cc:4626]
000000013F36CF23    mysqld.exe!mysqld_main()[mysqld.cc:4812]
000000013F7094A7    mysqld.exe!__tmainCRTStartup()[crt0.c:266]
000000007789F56D    kernel32.dll!BaseThreadInitThunk()
0000000077AD2CC1    ntdll.dll!RtlUserThreadStart()
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:
I started the daemon from the commandline (with admin privileges):
"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini"

I imported some schema dumps.

I connected with the JDBC driver. Then the server crashed.

What location had you set for datadir in my.ini? Check http://bugs.mysql.com/bug.php?id=55529 for similar symptoms.

I used the default as set by the installation procedure: 

[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306

#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.5/"

#Path to the database root
datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"

You'll find the complete my.ini attached.

my.ini

Attachment: my.ini (application/octet-stream, text), 9.03 KiB.

Please, upload the entire error log.

Complete log file

Attachment: CPR-51-502.err (application/octet-stream, text), 3.68 KiB.

Looks duplicate of http://bugs.mysql.com/bug.php?id=55529. Please check.

Well, it might be the same as http://bugs.mysql.com/bug.php?id=55529.
However, that one is not solved either and the error occurred again in 5.5.9.

I tried the default data dir as set by the installer: 
datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"

as well as a folder where I don't need administrator privilege to write to:
C:\MySQL_Data\

bug http://bugs.mysql.com/bug.php?id=60353 marked as duplicate of this one.

Please, check if the same problem still happens with a newer version, 5.5.11.

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".