Forum Debian Users Gang

/usr/sbin/mysqld: ready for connections.
Version: '4.1.21-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
 MySQL Community Edition - Standard (GPL)
InnoDB: Error: trying to access page number 387440817 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10
070807 17:00:05InnoDB: Assertion failure in thread 9235360 in file fil0fil.c lin
e 3922
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=8388600
read_buffer_size=2093056
max_used_connections=31
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 417391
 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xac657ed0
Attempting backtrace. You can use the following information to find out