Bug #80695 | handle_fatal_signal (sig=6) in ib::fatal::~fatal | innobase/ut/ut0ut.cc:920 | ||
---|---|---|---|
Submitted: | 10 Mar 2016 17:12 | Modified: | 11 Mar 2016 2:35 |
Reporter: | Ramesh Sivaraman | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.7.11 | OS: | CentOS |
Assigned to: | CPU Architecture: | Any | |
Tags: | debug |
[10 Mar 2016 17:12]
Ramesh Sivaraman
[11 Mar 2016 2:32]
MySQL Verification Team
C:\dbs>c:\dbs\5.7\bin\mysql -uroot -p --port=3570 --prompt="mysql 5.7 > " Enter password: ****** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.7.13-debug Source distribution PULL: 2016-MAR-05 Copyright (c) 2000, 2016, 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 5.7 > DROP DATABASE test; ERROR 1008 (HY000): Can't drop database 'test'; database doesn't exist mysql 5.7 > set global innodb_saved_page_number_debug=100; Query OK, 0 rows affected (0.00 sec) mysql 5.7 > set global innodb_fil_make_page_dirty_debug=0; ERROR 2013 (HY000): Lost connection to MySQL server during query
[11 Mar 2016 2:35]
MySQL Verification Team
Thank you for the bug report. 2016-03-11T02:29:01.440710Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160310 23:29:01 <CUT> 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] InnoDB: Trying to read doublewrite buffer page [page id: space=0, page number=100] 2016-03-11T02:29:51.801776Z 2 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=0, page number=100] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/refman/5.7/en/ for more details. Aborting... 2016-03-10 23:29:51 0x3160 InnoDB: Assertion failure in thread 12640 in file ut0ut.cc line 920 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/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 02:29:51 UTC - mysqld got exception 0x80000003 ; 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=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68071 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x200cac6d610 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... 7ff61f9756e5 mysqld.exe!my_sigabrt_handler()[my_thr_init.c:449] 7ff62016f63f mysqld.exe!raise()[winsig.c:594] 7ff62016c550 mysqld.exe!abort()[abort.c:82] 7ff61fc1cc5f mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:68] 7ff61fc1e743 mysqld.exe!ib::fatal::~fatal()[ut0ut.cc:920] 7ff61fa504f8 mysqld.exe!buf_page_get_gen()[buf0buf.cc:4209] 7ff61fa1b7f0 mysqld.exe!innodb_make_page_dirty()[ha_innodb.cc:17536] 7ff61ee71b23 mysqld.exe!sys_var_pluginvar::global_update()[sql_plugin.cc:3503] 7ff61ed2513b mysqld.exe!sys_var::update()[set_var.cc:184] 7ff61ed25e77 mysqld.exe!set_var::update()[set_var.cc:802] 7ff61ed26f35 mysqld.exe!sql_set_variables()[set_var.cc:662] 7ff61ecb9797 mysqld.exe!mysql_execute_command()[sql_parse.cc:3631] 7ff61ecb4f1f mysqld.exe!mysql_parse()[sql_parse.cc:5519] 7ff61ecbf654 mysqld.exe!dispatch_command()[sql_parse.cc:1432] 7ff61ecbe533 mysqld.exe!do_command()[sql_parse.cc:997] 7ff61ec71ad2 mysqld.exe!handle_connection()[connection_handler_per_thread.cc:301] 7ff61ffe27f2 mysqld.exe!pfs_spawn_thread()[pfs.cc:2190] 7ff61f973f86 mysqld.exe!win_thread_start()[my_thread.c:37] 7ff62016ee55 mysqld.exe!_callthreadstartex()[threadex.c:376] 7ff62016f0a7 mysqld.exe!_threadstartex()[threadex.c:359] 7ff9b8ac8102 KERNEL32.DLL!BaseThreadInitThunk() 7ff9b8dbc2e4 ntdll.dll!RtlUserThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (200cad64960): set global innodb_fil_make_page_dirty_debug=0 Connection ID (thread ID): 2 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.