Bug #49893 innodb tablespace corruption and assertions

• Submitted: 23 Dec 2009 14:11
• Modified: 6 May 2010 7:37
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Can't repeat
• Category: MySQL Server: InnoDB Plugin storage engine
• Severity: S1 (Critical)
• Version: 5.5.0-m2, plugin 1.0.5
• OS: Windows (xp64)
• CPU Architecture: Any

[23 Dec 2009 14:11] Shane Bester

Description:
a few errors are being hit during testing with :
mysql-noinstall-5.5.0-m2-winx64.zip (innodb version 1.0.5)

1)
InnoDB: Error: trying to access page number 553974655 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.
091223 15:26:27  InnoDB: Assertion failure in thread 1252 in file .\fil\fil0fil.c line 4297
<cut>

2)
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 0000000000000095ffffffff000000000000011600000002aaaaaaaafeffffffffffbfaafafffffb; asc
InnoDB: Serious error! InnoDB is trying to free page 4177
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
...
091223 15:15:27  InnoDB: Assertion failure in thread 10296 in file .\fsp\fsp0fsp.c line 3285

How to repeat:
no stable testcase yet, stay tuned. they happened with a cleanly created database with no prior crashes, repeated twice from clean start.

[23 Dec 2009 17:19] MySQL Verification Team

some stack traces from crashes...

Attachment: bug49893_stacktraces.txt (text/plain), 21.17 KiB.

[28 Dec 2009 13:04] MySQL Verification Team

maybe related, bug #49938

[6 May 2010 7:37] MySQL Verification Team

haven't seen this in recent versions.

[26 Jul 2010 3:15] Roel Van de Paar

1) see bug #55543