InnoDB: Failing assertion: log_bmp_sys->parse_buf_end == log_bmp_sys->parse_buf in file log0online.cc line 1092 | abort (sig=6) in log_online_follow_log_group

Bug #1233506 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
Invalid
Undecided
Unassigned
5.1
Won't Fix
Undecided
Unassigned
5.5
New
Undecided
Unassigned
5.6
Invalid
Undecided
Unassigned

Bug Description

2013-09-30 21:47:48 8845 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2829109
2013-09-30 21:47:48 8845 [Warning] InnoDB: last tracked LSN in './ib_modified_log_2_65548.xdb' is 65548, but the last checkpoint LSN is 2027532. This might be due to a server crash or a very fast shutdown.
2013-09-30 21:47:48 8845 [Note] InnoDB: reading the log to advance the last tracked LSN.
2013-09-30 21:47:48 7fd077c3f7e0 InnoDB: Assertion failure in thread 140533339256800 in file log0online.cc line 1092
InnoDB: Failing assertion: log_bmp_sys->parse_buf_end == log_bmp_sys->parse_buf

Testcase:

/sde/Percona-Server-5.6.13-rc60.5-450.Linux.x86_64/bin/mysqld \
--innodb_buffer_pool_size=2147483648 \
--basedir=/sde/Percona-Server-5.6.13-rc60.5-450.Linux.x86_64 \
--datadir=/sde/Percona-Server-5.6.13-rc60.5-450.Linux.x86_64/data \
--core --socket=/sde/Percona-Server-5.6.13-rc60.5-450.Linux.x86_64/socket.sock \
--port=19659 \
--log-error=/sde/Percona-Server-5.6.13-rc60.5-450.Linux.x86_64/log/master.err \
--innodb_log_files_in_group=2 \
--innodb_log_group_home_dir=/sde//942626/_epoch/1380225251588335918 \
--innodb_max_changed_pages=2 \
--innodb_log_block_size=4096 \
--innodb_track_changed_pages=1 \
--innodb_use_global_flush_log_at_trx_commit=0 \
--innodb-buffer-pool-populate \
--loose-readonly-key-cache-division-limit=0 \
--minimum-join-buffer-size=128 \
--skip-innodb_doublewrite \
--thread_handling=pool-of-threads \
--userstat \
--hidden-key-buffer-size=0 \
--innodb_purge_threads=1 \
--innodb_adaptive_hash_index_partitions=1 \
--innodb_buffer_pool_instances=5 \
--core 2>&1 &

Tags: bitmap qa xtradb
Revision history for this message
Roel Van de Paar (roel11) wrote :

If 5.1/5.5 also like previous bug 1108613, please remove 56qual

Revision history for this message
Roel Van de Paar (roel11) wrote :
summary: InnoDB: Failing assertion: log_bmp_sys->parse_buf_end ==
- log_bmp_sys->parse_buf in file log0online.cc line 1092
+ log_bmp_sys->parse_buf in file log0online.cc line 1092 | abort (sig=6)
+ in log_online_follow_log_group
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 :

Not all mysqld options may be needed, simplified somewhat already from original set.

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

Without --innodb_log_block_size=4096, it gives:

2013-09-30 22:11:48 9478 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
2013-09-30 22:11:48 9478 [ERROR] Plugin 'InnoDB' init function returned error.
2013-09-30 22:11:48 9478 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2013-09-30 22:11:48 9478 [ERROR] Unknown/unsupported storage engine: InnoDB
2013-09-30 22:11:48 9478 [ERROR] Aborting

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

Removing 56qual, because this bug 1) only happens when server tries to track missing log data on startup, a corner case; 2) high chance the issue is present in 5.1 and 5.5 too.

tags: added: bitmap xtradb
removed: 56qual
Revision history for this message
Roel Van de Paar (roel11) wrote :

Invalid. Issues with test setup:
1. (Most importantly) - when using mysql_install_db, you have to use a matching innodb_log_block_size=4096
2. Do not point to other/old innodb_log_group_home_dir's nor modify innodb_log_files_in_group etc.

Revision history for this message
Roel Van de Paar (roel11) wrote :
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-3034

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.