| Bug #93651 | Assertion failure in space_id == page_get_space_id(buf_block_get_frame(block)) | ||
|---|---|---|---|
| Submitted: | 18 Dec 2018 11:49 | Modified: | 18 Dec 2018 21:48 |
| Reporter: | Ramesh Sivaraman | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S6 (Debug Builds) |
| Version: | 8.0.13 | OS: | Ubuntu |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | debug | ||
[18 Dec 2018 11:49]
Ramesh Sivaraman
[18 Dec 2018 21:40]
MySQL Verification Team
Repeatable with version 8.0.13: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7 Server version: 8.0.13-debug Source distribution Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> SET @@GLOBAL.innodb_undo_tablespaces=128; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> 2018-12-18T21:35:43.940627Z 0 [System] [MY-010931] [Server] /home/miguel/bug/8.0//bin/mysqld: ready for connections. Version: '8.0.13-debug' socket: '/tmp/mysql.sock' port: 32649 Source distribution. 2018-12-18T21:35:44.030092Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/tmp/mysqlx.sock' bind-address: '::' port: 33060 2018-12-18T21:36:21.475377Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fsp0fsp.cc:897:space_id == page_get_space_id(buf_block_get_frame(block)) thread 139849000531712 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 21:36:21 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=2 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67877 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f3110000bb0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 7f3121ffab70 thread_stack 0x46000 /home/miguel/bug/8.0//bin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x55) [0x55d3f9f2c270] /home/miguel/bug/8.0//bin/mysqld(handle_fatal_signal+0x3f2) [0x55d3f8c022ed] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12dd0) [0x7f3194f63dd0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7f3194508077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7f31944e9535] /home/miguel/bug/8.0//bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x1a5) [0x55d3fa3197ab] /home/miguel/bug/8.0//bin/mysqld(fsp_header_write_encryption(unsigned int, unsigned long, unsigned char*, bool, bool, mtr_t*)+0xfa) [0x55d3fa4a20c0] /home/miguel/bug/8.0//bin/mysqld(+0x43d830e) [0x55d3fa29830e] /home/miguel/bug/8.0//bin/mysqld(srv_master_thread()+0x1d4) [0x55d3fa298a6a] /home/miguel/bug/8.0//bin/mysqld(void std::__invoke_impl<void, void (*&)()>(std::__invoke_other, void (*&)())+0x1d) [0x55d3fa09f92c] /home/miguel/bug/8.0//bin/mysqld(std::__invoke_result<void (*&)()>::type std::__invoke<void (*&)()>(void (*&)())+0x2f) [0x55d3fa09e56e] /home/miguel/bug/8.0//bin/mysqld(void std::_Bind<void (*())()>::__call<void>(std::tuple<>&&, std::_Index_tuple<>)+0x1c) [0x55d3fa09c654] /home/miguel/bug/8.0//bin/mysqld(void std::_Bind<void (*())()>::operator()<, void>()+0x33) [0x55d3fa09a661] /home/miguel/bug/8.0//bin/mysqld(void Runnable::operator()<void (*)()>(void (*&&)())+0x55) [0x55d3fa098215] /home/miguel/bug/8.0//bin/mysqld(void std::__invoke_impl<void, Runnable, void (*)()>(std::__invoke_other, Runnable&&, void (*&&)())+0x37) [0x55d3fa093a10] /home/miguel/bug/8.0//bin/mysqld(std::__invoke_result<Runnable, void (*)()>::type std::__invoke<Runnable, void (*)()>(Runnable&&, void (*&&)())+0x46) [0x55d3fa08da36] /home/miguel/bug/8.0//bin/mysqld(decltype (__invoke((_S_declval<0ul>)(), (_S_declval<1ul>)())) std::thread::_Invoker<std::tuple<Runnable, void (*)()> >::_M_invoke<0ul, 1ul>(std::_Index_tuple<0ul, 1ul>)+0x43) [0x55d3fa0a0f1f] /home/miguel/bug/8.0//bin/mysqld(std::thread::_Invoker<std::tuple<Runnable, void (*)()> >::operator()()+0x27) [0x55d3fa0a0d01] /home/miguel/bug/8.0//bin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0x1c) [0x55d3fa0a06fa] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbd63f) [0x7f319491563f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8164) [0x7f3194f59164] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f31945e1def] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): Connection ID (thread ID): 0 Status: NOT_KILLED
[18 Dec 2018 21:48]
MySQL Verification Team
Thank you for the bug report. Repeatable with version reported 8.0.13 but not anymore with most source server: iguel@tikal:~/bug $ 8.0/bin/mysql -uroot -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 7 Server version: 8.0.15-debug Source distribution Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> SET @@GLOBAL.innodb_undo_tablespaces=128; Query OK, 0 rows affected, 1 warning (0,00 sec) mysql> SHOW WARNINGS; +---------+------+----------------------------------------------------------+ | Level | Code | Message | +---------+------+----------------------------------------------------------+ | Warning | 1292 | Truncated incorrect innodb_undo_tablespaces value: '128' | +---------+------+----------------------------------------------------------+ 1 row in set (0,00 sec) mysql>
[21 Dec 2018 12:15]
Roel Van de Paar
Also see bug 93717
