Hello,
again, I'm having problems with InnoDB tables. A certain table cannot be
dropped. If I'm issueing the drop table statement, the connection is
lost and I get the following in the logfile:
060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks,
InnoDB: space id 12 did not exist in memory. Retrying an open.
InnoDB: Error: trying to add tablespace 12 of name
'./db15670/mw_pagelinks.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 12 of name './db15720/admin.ibd' already exists in the tablespace
InnoDB: memory cache!
060327 14:38:11 InnoDB: Error: page 3 log sequence number 0 153218641
InnoDB: is in the future! Current system log sequence number 0 14322402.
InnoDB: Your database may be corrupt.
060327 14:38:11InnoDB: Assertion failure in thread 196621 in file
fsp0fsp.c line 3202
InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT,
buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE
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/mysql/en/Forcing_recovery.html
InnoDB: 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=402653184
read_buffer_size=2093056
max_used_connections=12
max_connections=1000
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 290904 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8a000c18
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...
Cannot determine thread, fp=0xbe1fbe08, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a43b4
0x82bf71c
0x820a5fd
0x81b64f5
0x8169f26
0x81a4bc7
0x81a4224
0x81a36c2
0x817f332
0x817e57d
0x819376b
0x8125411
0x811ba68
0x812abe0
0x812a500
0x80b76b2
0x80bbb72
0x80b54bd
0x80b5102
0x80b48f9
0x82bb001
0x82ed89a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and
follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8bb38e0 = drop table mw_pagelinks
thd->thread_id=220
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.
Number of processes running now: 0
060327 14:38:12 mysqld restarted
060327 14:38:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
The whole mysql-server crashed just because something is wrong in one
innodb table. The force-recovery-hint didn't help at all, because it
just made it possible do drop the table, but nothing was fixed and I
couldn't create the table back then.
Why does this happen?
Regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
