MySQL crash ?

I'm new to MySQL and am having problem restarting MySQL server after it crashes. Below are the error logs:

021023 13:56:05 mysqld started
021023 13:56:05 Warning: setrlimit couldn't increase number of open files to mo
re than 1024
021023 13:56:05 Warning: Changed limits: max_connections: 300 table_cache: 357
021023 13:56:05 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 155 153173917
InnoDB: Doing recovery: scanned up to log sequence number 155 158416384
InnoDB: Doing recovery: scanned up to log sequence number 155 163659264
021023 13:56:06 InnoDB: Starting an apply batch of log records to the database.
..
InnoDB: Progress in percents: InnoDB: Error: trying to access page number 32 in
space 0
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10
InnoDB: Assertion failure in thread 1024 in file fil0fil.c line 1168
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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 agaist 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
record_buffer=20967424
sort_buffer=20971512
max_used_connections=0
max_connections=300
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 3906381 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...


Any help is appreciated. Thanks in advance

Sounds like it could be a configuration file problem. I would suggest using the sameple file my-small.cnf and seeing if the database fires up. If you then need mysql to be more robust, try the my-medium.cnf. Let us know if it fires up with either of these config files....