panic: MySQL tables currupt and can't reload

[Evan Leibovitch]

Hello all.

If there are any expects here on mySQL I could use some help.

I have a database that reports two tables corrupt when running mysqlcheck.

mysql dies if one of a command attempts to write to those tables, though
reads are fine (and I have done appropriate dumps of the data).

However, if I try to do a reload (or even try to drop the database
before recreating) I get mysql crashing.
Below is a past of the messages I get when it crashes.

I am not a C++ programmer so the stack trace will likely not be of much
help to me.

Any suggestions are welcomed -- including the best way to nuke the whole
database and start over. There is only one database in use and it's
backed up OK.

- Evan



-------------------------------------------------------

InnoDB: Error: trying to access page number 1946337664 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.
081001 13:19:49InnoDB: Assertion failure in thread 1149196624 in file
fil0fil.c line 3959
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.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
081001 13:19:49 - 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=16777216
read_buffer_size=131072
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x2424b40
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=0x447f4fd0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x2424b40 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

--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists