I have the same situation with restarting of 5.1.67-rel14.3-log Percona Server (GPL), 14.3, Revision 506
What I have in my mysqld.log:
130130 9:48:39 InnoDB: Warning: allocated tablespace 21, old maximum was 9
130130 9:48:39 InnoDB: Assertion failure in thread 140639204140800 in file btr/btr0cur.c line 321
InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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: about forcing recovery.
15:48:39 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at
key_buffer_size=209715200
read_buffer_size=8388608
max_used_connections=0
max_threads=400
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 = 16593237 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
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 = 0 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8ac755]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x6a862b]
/lib64/libpthread.so.0(+0xf500)[0x7feac550e500]
/lib64/libc.so.6(gsignal+0x35)[0x7feac46be8a5]
/lib64/libc.so.6(abort+0x175)[0x7feac46c0085]
/usr/sbin/mysqld[0x7ed8bd]
/usr/sbin/mysqld[0x7f2ad0]
/usr/sbin/mysqld[0x7a0c68]
/usr/sbin/mysqld[0x79f502]
/usr/sbin/mysqld[0x79fa16]
/usr/sbin/mysqld[0x7a0558]
/usr/sbin/mysqld[0x787680]
/usr/sbin/mysqld[0x7bf3f6]
/usr/sbin/mysqld[0x7b727b]
/lib64/libpthread.so.0(+0x7851)[0x7feac5506851]
/lib64/libc.so.6(clone+0x6d)[0x7feac477411d]
You may download the Percona Server operations manual by visiting
. You may find information
in the manual which will help you identify the cause of the crash.
130130 09:48:39 mysqld_safe Number of processes running now: 0
130130 09:48:39 mysqld_safe mysqld restarted
I have the same situation with restarting of 5.1.67-rel14.3-log Percona Server (GPL), 14.3, Revision 506
What I have in my mysqld.log:
130130 9:48:39 InnoDB: Warning: allocated tablespace 21, old maximum was 9 get_prev( get_block- >frame, mtr) == page_get_ page_no( page)
130130 9:48:39 InnoDB: Assertion failure in thread 140639204140800 in file btr/btr0cur.c line 321
InnoDB: Failing assertion: btr_page_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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: about forcing recovery.
15:48:39 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at
key_buffer_ size=209715200 size=8388608 connections= 0 size)*max_ threads = 16593237 K bytes of memory
read_buffer_
max_used_
max_threads=400
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 mysqld( my_print_ stacktrace+ 0x35)[0x8ac755] mysqld( handle_ fatal_signal+ 0x40b)[ 0x6a862b] libpthread. so.0(+0xf500) [0x7feac550e500 ] libc.so. 6(gsignal+ 0x35)[0x7feac46 be8a5] libc.so. 6(abort+ 0x175)[ 0x7feac46c0085] mysqld[ 0x7ed8bd] mysqld[ 0x7f2ad0] mysqld[ 0x7a0c68] mysqld[ 0x79f502] mysqld[ 0x79fa16] mysqld[ 0x7a0558] mysqld[ 0x787680] mysqld[ 0x7bf3f6] mysqld[ 0x7b727b] libpthread. so.0(+0x7851) [0x7feac5506851 ] libc.so. 6(clone+ 0x6d)[0x7feac47 7411d]
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 = 0 thread_stack 0x80000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
You may download the Percona Server operations manual by visiting
. You may find information
in the manual which will help you identify the cause of the crash.
130130 09:48:39 mysqld_safe Number of processes running now: 0
130130 09:48:39 mysqld_safe mysqld restarted
I have opened a topic http:// www.perconaforu m.com/index. php?t=msg& goto=10374
with more information about my env and issue