Description:
We had a server running RedHat 7.3 and RedHat's 3.23.58 Mysql Server. We wanted to upgrade the server to Centos 3.1 running Mysql.coms's 4.0.20 Server.
We copied the /var/lib/mysql folder to another machine, running 4.0.20. When we tried to run /etc/init.d/mysql start, we found the following in the mysql log file;
InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Error: trying to access a stray pointer 0x37bf3ff8
InnoDB: buf pool start is at 0xb7400000, number of pages 512
040623 22:07:24InnoDB: Assertion failure in thread 1024 in file ../../innobase/include/buf0buf.ic line 282
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. See section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about forcing recovery.
mysqld got signal 11;
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=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x83bc2a0
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...
Bogus stack limit or frame pointer, fp=0xbfffc0f8, stack_bottom=0x7c99c290, thread_stack=196608, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7bcebb90 is invalid pointer
thd->thread_id=0
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
040623 22:07:24 mysqld ended
We copied the data files to another RedHat7.3 box, recently upgraded to mysql4, with the same results. We ran myismchk on the files, in case they were damaged, but they checked out fine, and when mysql was started, it failed again in the same way.
john
How to repeat:
I can give someone a copy of all these datafiles (though they are around 250MB) for debugging purposes, or can carry out instructions from a developer.
john
