Description:
111130 00:44:01 mysqld_safe Starting mysqld daemon with databases from /data/mysql_shard/db/data
111130 0:44:02 [Note] Plugin 'FEDERATED' is disabled.
111130 0:44:02 InnoDB: The InnoDB memory heap is disabled
111130 0:44:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111130 0:44:02 InnoDB: Compressed tables use zlib 1.2.3
111130 0:44:02 InnoDB: Using Linux native AIO
111130 0:44:02 InnoDB: Initializing buffer pool, size = 40.0G
111130 0:44:04 InnoDB: Completed initialization of buffer pool
111130 0:44:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1961190998489
111130 0:44:04 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1961193713871
111130 0:44:04 InnoDB: Assertion failure in thread 47285717624672 in file fsp0fsp.c line 2101
InnoDB: Failing assertion: inode
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
111130 0:44:04 - mysqld got signal 6 ;
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=8388608
read_buffer_size=262144
max_used_connections=0
max_threads=1200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 246089051 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
How to repeat:
conti..
Thread pointer: 0x0
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...
stack_bottom = (nil) thread_stack 0x40000
/data/mysql_shard/mysql5_1/bin/mysqld(my_print_stacktrace+0x39)[0x796d89]
/data/mysql_shard/mysql5_1/bin/mysqld(handle_segfault+0x380)[0x4fd110]
/lib64/libpthread.so.0[0x3e8d80eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3e8d030265]
/lib64/libc.so.6(abort+0x110)[0x3e8d031d10]
/data/mysql_shard/mysql5_1/bin/mysqld[0x8530a0]
/data/mysql_shard/mysql5_1/bin/mysqld[0x860af5]
/data/mysql_shard/mysql5_1/bin/mysqld[0x8304bb]
/data/mysql_shard/mysql5_1/bin/mysqld[0x7df032]
/data/mysql_shard/mysql5_1/bin/mysqld[0x7b2ced]
/data/mysql_shard/mysql5_1/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x669ea8]
/data/mysql_shard/mysql5_1/bin/mysqld[0x57e8da]
/data/mysql_shard/mysql5_1/bin/mysqld(_Z11plugin_initPiPPci+0xb5d)[0x581f3d]
/data/mysql_shard/mysql5_1/bin/mysqld[0x504b8c]
/data/mysql_shard/mysql5_1/bin/mysqld(_Z11mysqld_mainiPPc+0x3ca)[0x50571a]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3e8d01d994]
/data/mysql_shard/mysql5_1/bin/mysqld[0x4fb3da]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
111130 00:44:04 mysqld_safe mysqld from pid file /data/mysql_shard/db/mysql.pid ended
[root@sharddb-mqb007 bin]#
