Description:
I install MySQL from windows installer as i did many times before. But now MySQL service would not start. OS: win2008 R2 SP1 64bit on HP Proliant 12Gb memory, RAID 5.
To make my.ini i use configuration wizard. After several tests i notices that MySQL service runing well with MyISAM only. When i use INNODB + MyISAM i received next error. I spent many hours changing ini settings, nothing helps.
Here the content of .err file
110305 13:28:29 [Note] Plugin 'FEDERATED' is disabled.
110305 13:28:29 InnoDB: The InnoDB memory heap is disabled
110305 13:28:29 InnoDB: Mutexes and rw_locks use Windows interlocked functions
110305 13:28:29 InnoDB: Compressed tables use zlib 1.2.3
110305 13:28:29 InnoDB: Initializing buffer pool, size = 686.0M
110305 13:28:29 InnoDB: Completed initialization of buffer pool
110305 13:28:29 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!
110305 13:28:29 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...
110305 13:28:29 InnoDB: Assertion failure in thread 6420 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.
110305 13:28:29 - 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=371195904
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 = 395520 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...
000000013FCB626C mysqld.exe!fseg_inode_get()[fsp0fsp.c:2101]
000000013FCB6557 mysqld.exe!fseg_n_reserved_pages()[fsp0fsp.c:2436]
000000013FC794AE mysqld.exe!ibuf_init_at_db_start()[ibuf0ibuf.c:550]
000000013FCD4B4C mysqld.exe!dict_boot()[dict0boot.c:450]
000000013FC52FEA mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1699]
000000013FC49890 mysqld.exe!innobase_init()[ha_innodb.cc:2477]
000000013FA22666 mysqld.exe!ha_initialize_handlerton()[handler.cc:462]
000000013FA1C002 mysqld.exe!plugin_initialize()[sql_plugin.cc:1063]
000000013FA21279 mysqld.exe!plugin_init()[sql_plugin.cc:1349]
000000013FA0BC47 mysqld.exe!init_server_components()[mysqld.cc:3869]
000000013FA0C7D8 mysqld.exe!win_main()[mysqld.cc:4433]
000000013FA0CC1F mysqld.exe!mysql_service()[mysqld.cc:4626]
000000013FDA8D77 mysqld.exe!_callthreadstart()[thread.c:295]
000000013FDA8E21 mysqld.exe!_threadstart()[thread.c:275]
000000007721652D kernel32.dll!BaseThreadInitThunk()
000000007744C521 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:
Just install MySQL 5.5.9 64bit on 2008 R2 SP1 64bit. OS is almost clean, no other apps which can to block MySQL
Suggested fix:
I have no clue
