Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor)) in btr0pcur.cc line 447 | sig 6 in btr_pcur_move_to_next_page

[Ramesh Sivaraman]

2014-10-20 00:21:46 7f3bae129700 InnoDB: Assertion failure in thread 139894300251904 in file btr0pcur.cc line 447
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))

** Asserting query

 checksum table t1, t2, t3, t4

** GDB info

#0 0x00007f3be52a2771 in pthread_kill () from /lib64/libpthread.so.0
#1 0x0000000000ab7586 in my_write_core (sig=6) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/mysys/stacktrace.c:422
#2 0x000000000072f9ff in handle_fatal_signal (sig=6) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/signal_handler.cc:236
#3 <signal handler called>
#4 0x00007f3be3ea65c9 in raise () from /lib64/libc.so.6
#5 0x00007f3be3ea7cd8 in abort () from /lib64/libc.so.6
#6 0x0000000000ca5a9f in btr_pcur_move_to_next_page (cursor=0x7f3b8c105b20, mtr=0x7f3bae126260) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/btr/btr0pcur.cc:446
#7 0x0000000000c01dea in btr_pcur_move_to_next (cursor=0x7f3b8c105b20, mtr=0x7f3bae126260) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/include/btr0pcur.ic:360
#8 0x0000000000c0b8c5 in row_search_for_mysql (buf=0x7f3b8c122540 "\376\001", mode=1, prebuilt=0x7f3b8c105aa8, match_mode=0, direction=1) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/row/row0sel.cc:5013
#9 0x0000000000ad924d in ha_innobase::general_fetch (this=0x7f3b8c048ee0, buf=0x7f3b8c122540 "\376\001", direction=1, match_mode=0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/handler/ha_innodb.cc:8500
#10 0x0000000000ad9887 in ha_innobase::rnd_next (this=0x7f3b8c048ee0, buf=0x7f3b8c122540 "\376\001") at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/innobase/handler/ha_innodb.cc:8726
#11 0x0000000000642820 in handler::ha_rnd_next (this=0x7f3b8c048ee0, buf=0x7f3b8c122540 "\376\001") at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/handler.cc:2872
#12 0x000000000085e79d in mysql_checksum_table (thd=0x38eddc0, tables=0x7f3b8c005190, check_opt=0x38f10e8) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_table.cc:9478
#13 0x00000000007e4bc6 in mysql_execute_command (thd=0x38eddc0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:3685
#14 0x00000000007ed193 in mysql_parse (thd=0x38eddc0, rawbuf=0x7f3b8c0050a0 "checksum table t1, t2, t3, t4", length=29, parser_state=0x7f3bae127e30) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:6773
#15 0x00000000007df5fc in dispatch_command (command=COM_QUERY, thd=0x38eddc0, packet=0x40ea1f1 "", packet_length=30) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:1432
#16 0x00000000007de528 in do_command (thd=0x38eddc0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_parse.cc:1049
#17 0x00000000007a64e5 in do_handle_one_connection (thd_arg=0x38eddc0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_connect.cc:1532
#18 0x00000000007a5fed in handle_one_connection (arg=0x38eddc0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/sql/sql_connect.cc:1443
#19 0x0000000000dc5bac in pfs_spawn_thread (arg=0x40a51f0) at /mnt/workspace/percona-server-5.6-binaries-debug-yassl/label_exp/centos6-64/percona-server-5.6.21-69.0/storage/perfschema/pfs.cc:1860
#20 0x00007f3be529ddf3 in start_thread () from /lib64/libpthread.so.0
#21 0x00007f3be3f6701d in clone () from /lib64/libc.so.6

[Ramesh Sivaraman (rameshvs02)]

Core, GDB, error log etc

There was no master (single threaded, single mysqld run)

[Ramesh Sivaraman (rameshvs02)]

s/There was no master (single threaded, single mysqld run)/Single threaded run, single mysqld involved/

[DilipSimha (nmdilipsimha)]

I came across this same assert. Ran mysqlcheck and confirmed there is no data loss.
Can someone confirm if this assert implies a bug in source code or hardware ?

May 3 16:10:17 scdnwcb01 mysqld: 2016-05-03 16:10:17 7f91cd01a700 InnoDB: Assertion failure in thread 140264186423040 in file btr0pcur.cc line 447
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: We intentionally generate a memory trap.
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
May 3 16:10:17 scdnwcb01 mysqld: InnoDB: about forcing recovery.
May 3 16:10:17 scdnwcb01 mysqld: 16:10:17 UTC - mysqld got signal 6 ;
May 3 16:10:17 scdnwcb01 mysqld: This could be because you hit a bug. It is also possible that this binary
May 3 16:10:17 scdnwcb01 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 3 16:10:17 scdnwcb01 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 3 16:10:17 scdnwcb01 mysqld: We will try our best to scrape up some info that will hopefully help
May 3 16:10:17 scdnwcb01 mysqld: diagnose the problem, but since we have already crashed,
May 3 16:10:17 scdnwcb01 mysqld: something is definitely wrong and this may fail.
May 3 16:10:17 scdnwcb01 mysqld: Please help us make Percona XtraDB Cluster better by reporting any
May 3 16:10:17 scdnwcb01 mysqld: bugs at https://bugs.launchpad.net/percona-xtradb-cluster
May 3 16:10:17 scdnwcb01 mysqld:
May 3 16:10:17 scdnwcb01 mysqld: key_buffer_size=16777216
May 3 16:10:17 scdnwcb01 mysqld: read_buffer_size=131072
May 3 16:10:17 scdnwcb01 mysqld: max_used_connections=57
May 3 16:10:17 scdnwcb01 mysqld: max_threads=352
May 3 16:10:17 scdnwcb01 mysqld: thread_count=47
May 3 16:10:17 scdnwcb01 mysqld: connection_count=47
May 3 16:10:17 scdnwcb01 mysqld: It is possible that mysqld could use up to
May 3 16:10:17 scdnwcb01 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 156880 K bytes of memory
May 3 16:10:17 scdnwcb01 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 3 16:10:17 scdnwcb01 mysqld:
May 3 16:10:17 scdnwcb01 mysqld: Thread pointer: 0x86b8f10
May 3 16:10:17 scdnwcb01 mysqld: Attempting backtrace. You can use the following information to find out
May 3 16:10:17 scdnwcb01 mysqld: where mysqld died. If you see no messages after this, something went
May 3 16:10:17 scdnwcb01 mysqld: terribly wrong...
May 3 16:10:17 scdnwcb01 mysqld: stack_bottom = 7f91cd019e50 thread_stack 0x30000
May 3 16:10:17 scdnwcb01 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8e397e]
May 3 16:10:17 scdnwcb01 mysqld: /...

[DilipSimha (nmdilipsimha)]

This was with version: percona-server-5.6.20-68.0

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3213