InnoDB: Failing assertion: bpage->oldest_modification != 0 in file buf0flu.c and buf0lru.c

Bug #1111211 reported by Roel Van de Paar
6
This bug affects 1 person
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
Laurynas Biveinis
5.5
Fix Released
High
Laurynas Biveinis

Bug Description

InnoDB: DEBUG: update_statistics for query13003/#sql-694_406.
130130 20:26:03 InnoDB: Assertion failure in thread 465360640 in file buf0flu.c line 1123
InnoDB: Failing assertion: bpage->oldest_modification != 0

Thread 5 (LWP 23771):
+bt
#0 0x0000000004e3969c in pthread_kill () from /lib64/libpthread.so.0
#1 0x00000000007e2779 in my_write_core (sig=6) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/mysys/stacktrace.c:433
#2 0x00000000006ab0ea in handle_fatal_signal (sig=6) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/signal_handler.cc:249
#3 <signal handler called>
#4 0x0000000005b448a5 in raise () from /lib64/libc.so.6
#5 0x0000000005b46085 in abort () from /lib64/libc.so.6
#6 0x00000000008d4346 in buf_flush_or_remove_page (bpage=0x7cf6420, buf_pool=0x76b8eb8) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/buf/buf0lru.c:507
#7 buf_flush_or_remove_pages (id=10468, buf_pool=0x76b8eb8) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/buf/buf0lru.c:564
#8 buf_flush_dirty_pages (id=<optimized out>, buf_pool=<optimized out>) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/buf/buf0lru.c:606
#9 buf_LRU_flush_or_remove_pages (id=10468, buf_remove=BUF_REMOVE_FLUSH_NO_WRITE) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/buf/buf0lru.c:804
#10 0x000000000090687a in fil_delete_tablespace (id=10468, evict_all=0) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/fil/fil0fil.c:2398
#11 0x0000000000841d1b in row_drop_table_for_mysql (name=0x16db44d8 "query011069/#sql2-27a8-7a4", trx=<optimized out>, drop_db=<optimized out>) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/row/row0mysql.c:3577
#12 0x000000000081d3f3 in ha_innobase::delete_table (this=<optimized out>, name=<optimized out>) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/storage/innobase/handler/ha_innodb.cc:8451
#13 0x00000000006b396c in handler::ha_delete_table (this=0x16f004a0, name=0x2691c060 "./query011069/#sql2-27a8-7a4") at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/handler.cc:3660
#14 0x00000000006b3ba4 in ha_delete_table (thd=0x101a8f20, table_type=<optimized out>, path=0x2691c060 "./query011069/#sql2-27a8-7a4", db=0x16d40300 "query011069", alias=0x2691df40 "#sql2-27a8-7a4", generate_warning=false) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/handler.cc:2211
#15 0x00000000006030a7 in quick_rm_table (base=0x6293750, db=0x16d40300 "query011069", table_name=0x2691df40 "#sql2-27a8-7a4", flags=3) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_table.cc:2416
#16 0x0000000000606b84 in mysql_alter_table (thd=<optimized out>, new_db=0x16d40300 "query011069", new_name=0x16d40318 "t1", create_info=0x2691e570, table_list=<optimized out>, alter_info=0x2691e650, order_num=0, order=0x0, ignore=false) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_table.cc:7004
#17 0x00000000007c1a21 in Alter_table_statement::execute (this=<optimized out>, thd=0x101a8f20) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_alter.cc:106
#18 0x000000000059f198 in mysql_execute_command (thd=0x101a8f20) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_parse.cc:4615
#19 0x000000000059fa80 in mysql_parse (thd=0x101a8f20, rawbuf=0x16d40220 "ALTER TABLE query011069 . `t1` DROP COLUMN `c34`", length=<optimized out>, parser_state=0x2691fb10) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_parse.cc:5844
#20 0x00000000005a0d9f in dispatch_command (command=COM_QUERY, thd=0x101a8f20, packet=<optimized out>, packet_length=48) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_parse.cc:1061
#21 0x00000000005a22d9 in do_command (thd=0x101a8f20) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_parse.cc:788
#22 0x00000000006479b1 in do_handle_one_connection (thd_arg=<optimized out>) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_connect.cc:1497
#23 0x0000000000647aa7 in handle_one_connection (arg=0x101a8f20) at /ssd/QA-16274-5.5/Percona-Server-5.5.28-rel29.3/sql/sql_connect.cc:1404
#24 0x0000000004e34851 in start_thread () from /lib64/libpthread.so.0
#25 0x0000000005bfa11d in clone () from /lib64/libc.so.6

Run command:

[roel@macpro2 210222]$ cat cmd1004
ps -ef | grep 'cmdrun_1004' | grep -v grep | awk '{print $2}' | xargs sudo kill -9
rm -Rf /ssd/210222/cmdrun_1004
mkdir /ssd/210222/cmdrun_1004
cd /ssd/randgen
bash -c "set -o pipefail; perl runall.pl --queries=100000000 --seed=29973 --duration=180 --querytimeout=60 --short_column_names --sqltrace --reporter=Shutdown,Backtrace,QueryTimeout,ErrorLog,ErrorLogAlarm --mysqld=--log-output=none --mysqld=--sql_mode=ONLY_FULL_GROUP_BY --grammar=conf/percona_qa/percona_qa.yy --gendata=conf/percona_qa/percona_qa.zz --basedir=/ssd/Percona-Server-5.5.28-rel29.3-416-debug-valgrind.Linux.x86_64 --valgrind --reporter=ValgrindErrors --validator=MarkErrorLog --threads=25 --notnull --validator=Transformer --mysqld=--innodb_track_changed_pages=1 --mysqld=--innodb_max_bitmap_file_size=4096 --mysqld=--innodb_flush_method=O_DSYNC --mysqld=--innodb_file_per_table=1 --mtr-build-thread=715 --mask=12562 --vardir1=/ssd/210222/cmdrun_1004 > /ssd/210222/cmdrun1004.log 2>&1"

Tags: qa xtradb

Related branches

Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :

Crash in trial 1005

InnoDB: DEBUG: update_statistics for query13003/#sql-694_406.
130130 20:26:03 InnoDB: Assertion failure in thread 465360640 in file buf0flu.c line 1123
InnoDB: Failing assertion: bpage->oldest_modification != 0

Note the different location. If you would like stacks/error log, happy to run/provide.

Revision history for this message
Roel Van de Paar (roel11) wrote :

InnoDB: DEBUG: update_statistics for query111092/#sql-27a8_7a7.
130131 1:05:20 InnoDB: Assertion failure in thread 647104256 in file buf0lru.c line 507
InnoDB: Failing assertion: bpage->oldest_modification != 0

That is from trial 1004. Different location, in correction of the one above which was the same location.

summary: InnoDB: Failing assertion: bpage->oldest_modification != 0 in file
- buf0lru.c line <various locations>
+ buf0lru.c and buf0lru.c
tags: removed: bitmap
Revision history for this message
Roel Van de Paar (roel11) wrote :

Also seen in QA-16724-5.5-2

summary: InnoDB: Failing assertion: bpage->oldest_modification != 0 in file
- buf0lru.c and buf0lru.c
+ buf0flu.c and buf0lru.c
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Roel -

The original stacktrace and the assert do not match, let's sync on IRC.

tags: added: xtradb
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Exactly same cause as for bug 934377, different assert due to different timing.

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Also related: bug 1110102, bug 1116447.

Revision history for this message
Roel Van de Paar (roel11) wrote :

Also seen in QA-16724-5.5-2 tree @ revid 422 (debug-valgrind)

130202 12:51:00 InnoDB: Assertion failure in thread 626628352 in file buf0lru.c line 515
InnoDB: Failing assertion: bpage->oldest_modification != 0

Adding error log and stacks below for review

Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :
Revision history for this message
Roel Van de Paar (roel11) wrote :

Re: #5, Failing assertion: bpage->oldest_modification != 0 == abort in buf_flush_or_remove_page

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Also related: bug 1122462.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.