Details
Major
Description
Test: innodb_simulate_comp_failures-xtradb
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/2429
InnoDB: Assertion failure in thread 2810182464 in file buf0flu.cc line 549 InnoDB: Failing assertion: buf_page_in_file(bpage) buf/buf0flu.cc:549(buf_flush_ready_for_flush(buf_page_t*, buf_flush_t))[0x8856dd2] buf/buf0flu.cc:1368(buf_flush_page_and_try_neighbors)[0x8858e00] buf/buf0flu.cc:1721(buf_do_flush_list_batch)[0x885a55f] buf/buf0flu.cc:2053(buf_flush_list(unsigned long, unsigned long long, unsigned long*))[0x885bb14] buf/buf0flu.cc:2354(page_cleaner_do_flush_batch)[0x885d765] /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb76d9d4c] /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb74e8ace]
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Looks like https://bugs.launchpad.net/percona-server/+bug/1305364, which applies to 5.5 as well, and is fixed in XtraDB 5.5.37-35.1/5.6.17-66.0.
Are you seeing it with a newer XtraDB version than those above?
Hi, this was repeatable with Percona XtraDB (http://www.percona.com) 5.6.17-65.0 and with modified version of Facebook's patch to simulate compression failures https://github.com/facebook/mysql-5.6/commit/bce56ed93e4bfa06f845b7b98e78b9ab6281bdfc
But not very easily repeatable, I can't repeat on my machine.
R: Jan
OK, it's indeed LP 1305364 then, and you'll have a complete fix once you merge the corresponding 5.5/5.6.
True, your fix seems better and will be part of 5.5.39 release.
revno: 4313
committer: Jan Lindström <jplindst@mariadb.org>
branch nick: 10.0-innodb
timestamp: Thu 2014-07-31 10:32:52 +0300
message:
MDEV-6506: InnoDB: Assertion failure in thread 2810182464 in filebuf0flu.cc line 549.
Analysis: If buf_page_get_state(bpage) == BUF_BLOCK_REMOVE_HASH then
buf_page_in_file(bpage) might not be true.
Fix: ut_a(buf_page_in_file(bpage) || buf_page_get_state(bpage) == BUF_BLOCK_RE
MOVE_HASH);