InnoDB: Failing assertion: (buf_pool->flush_list).count > 0 [ in buf_flush_remove - buf0flu.c ] {Was: Crash in insert benchmark}
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Fix Released
|
High
|
Laurynas Biveinis |
Bug Description
In some insert intensive benchmark I've got crash
Version: '5.5.20-
120217 9:52:09 InnoDB: Assertion failure in thread 140660403742464 in file buf0flu.c line 542
InnoDB: Failing assertion: (buf_pool-
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
I do not have reliable procedure to repeat, but I will update ticket when I have more information.
Related branches
- Stewart Smith (community): Approve
-
Diff: 434 lines (+153/-46)7 files modifiedPercona-Server/storage/innobase/buf/buf0buf.c (+1/-1)
Percona-Server/storage/innobase/buf/buf0flu.c (+2/-2)
Percona-Server/storage/innobase/buf/buf0lru.c (+97/-37)
Percona-Server/storage/innobase/fil/fil0fil.c (+1/-1)
Percona-Server/storage/innobase/ibuf/ibuf0ibuf.c (+1/-1)
Percona-Server/storage/innobase/include/buf0buf.h (+22/-2)
Percona-Server/storage/innobase/include/buf0buf.ic (+29/-2)
Changed in percona-server: | |
status: | New → Incomplete |
importance: | Undecided → Medium |
tags: | added: crash |
tags: | added: xtradb |
tags: | added: i29552 |
Hi,
I've been hit by a similiar issue with percona 5.5.21. I get the following backtrace (unfortunately without the debuging symbols installed.)
Thread pointer: 0x0 mysqld( my_print_ stacktrace+ 0x35)[0x7c1805] mysqld( handle_ fatal_signal+ 0x4a4)[ 0x6912a4] .so.0(+ 0xeff0) [0x7fb11d00dff0 ] so.6(gsignal+ 0x35)[0x7fb11c2 091b5] so.6(abort+ 0x180)[ 0x7fb11c20bfc0] mysqld[ 0x8bb7f4] mysqld[ 0x8bb837] mysqld[ 0x8b603b] mysqld[ 0x8e908b] mysqld[ 0x86b5a0] .so.0(+ 0x68ca) [0x7fb11d0058ca ] so.6(clone+ 0x6d)[0x7fb11c2 a692d]
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 0x30000
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
/lib/libc.
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.