Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.3(EOL)
-
None
Description
10.3 31bd86c8df63a4d |
...
|
2017-11-16 20:25:04 0 [Note] InnoDB: Ignoring data file './test/t6.ibd' with space ID 4959, since the redo log references ./test/t6.ibd with space ID 4953.
|
2017-11-16 20:25:04 0 [Note] InnoDB: Ignoring data file './test/#sql-160f_e.ibd' with space ID 4959. Another data file called ./test/t6.ibd exists with the same space ID.
|
2017-11-16 20:25:05 0 [Note] InnoDB: Starting final batch to recover 3021 pages from redo log.
|
2017-11-16 20:25:05 0x7f68cd4dc700 InnoDB: Assertion failure in file /data/src/10.3-bug/storage/innobase/log/log0recv.cc line 1186
|
InnoDB: We intentionally generate a memory trap.
|
 |
#5 0x00007f1fcd8ad3fa in abort () from /lib/x86_64-linux-gnu/libc.so.6
|
#6 0x000055dfcdab67cb in ut_dbg_assertion_failed (expr=0x0, file=0x55dfcdfdd3b8 "/data/src/10.3-bug/storage/innobase/log/log0recv.cc", line=1186) at /data/src/10.3-bug/storage/innobase/ut/ut0dbg.cc:61
|
#7 0x000055dfcd9240c7 in recv_parse_or_apply_log_rec_body (type=MLOG_1BYTE, ptr=0x7f1fae032860 "", end_ptr=0x7f1fae032864 "", space_id=4608, page_no=0, apply=true, block=0x7f1fabc61a20, mtr=0x7f1fa877e590) at /data/src/10.3-bug/storage/innobase/log/log0recv.cc:1186
|
#8 0x000055dfcd9264cd in recv_recover_page (just_read_in=true, block=0x7f1fabc61a20) at /data/src/10.3-bug/storage/innobase/log/log0recv.cc:1834
|
#9 0x000055dfcdb2b540 in buf_page_io_complete (bpage=0x7f1fabc61a20, evict=false) at /data/src/10.3-bug/storage/innobase/buf/buf0buf.cc:6034
|
#10 0x000055dfcdbc29f1 in fil_aio_wait (segment=2) at /data/src/10.3-bug/storage/innobase/fil/fil0fil.cc:5359
|
#11 0x000055dfcda51006 in io_handler_thread (arg=0x55dfcf213110 <n+16>) at /data/src/10.3-bug/storage/innobase/srv/srv0start.cc:340
|
#12 0x00007f1fcf57b494 in start_thread (arg=0x7f1fa877f700) at pthread_create.c:333
|
#13 0x00007f1fcd96193f in clone () from /lib/x86_64-linux-gnu/libc.so.6
|
perl ./runall-new.pl --grammar=replication-ddl_sql.yy --gendata=conf/replication/replication-ddl_data.zz --duration=600 --threads=6 --queries=100M --redefine=instant_add.yy --mysqld=--max-statement-time=30 --scenario=Restart --scenario-type=crash --engine=InnoDB --seed=time --basedir=/data/src/10.3-bug --vardir=/dev/shm/vardir6
|
It's reproducible reasonably well, but not reducible easily. Probably not the highest priority, because the scenario is crash-restart during DML/DDL, which can't be good anyway, but maybe there is still something to solve here.
I have the datadir, but it's too big to attach.
Attachments
Issue Links
- relates to
-
MDEV-14545 Backup fails due to MLOG_INDEX_LOAD record
- Closed