MySQL Bugs: #58824: Crash MySQL in Windows Server 2008 R2 x64

Bug #58824	Crash MySQL in Windows Server 2008 R2 x64
Submitted:	8 Dec 2010 16:50	Modified:	25 Apr 2012 13:14
Reporter:	Davi Alencar	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S2 (Serious)
Version:	5.1.50	OS:	Windows (Server 2008 R2 x64)
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
101208 11:21:58 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Error: log file .\ib_logfile0 is of different size 0 56623104 bytes
InnoDB: than specified in the .cnf file 0 55574528 bytes!
101208 11:21:59 [ERROR] Plugin 'InnoDB' init function returned error.
101208 11:21:59 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
101208 11:21:59 [ERROR] Unknown/unsupported table type: INNODB
101208 11:21:59 [ERROR] Aborting

101208 11:21:59 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete

101208 11:38:50 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 2 3780802760
101208 11:38:51  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...
InnoDB: Doing recovery: scanned up to log sequence number 2 3780805825
InnoDB: Error: trying to access page number 2444762418 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
101208 11:38:51  InnoDB: Assertion failure in thread 1084 in file .\fil\fil0fil.c line 4078
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.

How to repeat:
?

Suggested fix:
?

Thank you for the bug report.

InnoDB: Error: log file .\ib_logfile0 is of different size 0 56623104 bytes
InnoDB: than specified in the .cnf file 0 55574528 bytes!

Please see if you have several my.ini files on your environment or you have older data directory in the current server datadir. Thanks in advance.

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

I hjave the same problem with no multiple My.ini files.  I completely uninstall MySQL and remove the directory to have a clean build.

120217 13:09:57 [Note] Plugin 'FEDERATED' is disabled.
120217 13:09:57 InnoDB: The InnoDB memory heap is disabled
120217 13:09:57 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120217 13:09:57 InnoDB: Compressed tables use zlib 1.2.3
120217 13:09:57 InnoDB: Initializing buffer pool, size = 95.0M
120217 13:09:57 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file C:\MySQL InnoDB Datafiles\ibdata1 did not exist:
InnoDB: a new database to be created!
120217 13:09:57  InnoDB: Setting file C:\MySQL InnoDB Datafiles\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Error: log file .\ib_logfile0 is of different size 0 55574528 bytes
InnoDB: than specified in the .cnf file 0 19922944 bytes!
120217 13:09:58 [ERROR] Plugin 'InnoDB' init function returned error.
120217 13:09:58 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120217 13:09:58 [ERROR] Unknown/unsupported storage engine: INNODB
120217 13:09:58 [ERROR] Aborting

120217 13:09:58 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

Erv,

Please, check the datadir value in your my.ini and then check/send the output of dir for that directory. I think that files mentioned in the error message are left in place from previous installation.

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

There seem to be two issues here.

One is that InnoDB refuses to start if the redo log file size disagrees with the configuration. This is a duplicate of MySQL Bug#13494, which will be fixed in MySQL 5.6.8.

Then, in the original bug report, it seems that something was fiddled with incorrectly, and InnoDB treated the log file as corrupted. Or, the log files did not really belong to the database instance that was recovered. This caused the assertion failure. Unfortunately, there are not many integrity checks in the InnoDB redo log code.