Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2.2, 10.3.0
Description
MDEV-9977 is back?
The last comment there says
Hi,
It looks like this is back again. I'm working with some tables in the 15-20GB range and the test instructions in this bug report reproduce the issue. 32-bit 10.2.x is affected? x64 is fine.
Error log:
2017-12-30 21:47:01 2376 [ERROR] [FATAL] InnoDB: Trying to read page number 1196032 in space 102, space name test/tinno, which is outside the tablespace bounds. Byte offset 0, len 16384
171230 21:47:01 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.2.11-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=65537
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 24849 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1f940138
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...
mysqld.exe!my_parameter_handler()[my_init.c:255]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:64]
mysqld.exe!ib::fatal::~fatal()[ut0ut.cc:791]
mysqld.exe!fil_report_invalid_page_access()[fil0fil.cc:5005]
mysqld.exe!fil_io()[fil0fil.cc:5146]
mysqld.exe!buf_read_page_low()[buf0rea.cc:192]
mysqld.exe!buf_read_page()[buf0rea.cc:462]
mysqld.exe!buf_page_get_gen()[buf0buf.cc:4320]
mysqld.exe!flst_add_last()[fut0lst.cc:131]
mysqld.exe!fsp_free_extent()[fsp0fsp.cc:1629]
mysqld.exe!fseg_free_extent()[fsp0fsp.cc:3296]
mysqld.exe!fseg_free_step_func()[fsp0fsp.cc:3369]
mysqld.exe!btr_free_but_not_root()[btr0btr.cc:1387]
mysqld.exe!btr_free_if_exists()[btr0btr.cc:1438]
mysqld.exe!dict_drop_index_tree()[dict0crea.cc:1048]
mysqld.exe!row_upd_clust_step()[row0upd.cc:3103]
mysqld.exe!row_upd()[row0upd.cc:3261]
mysqld.exe!row_upd_step()[row0upd.cc:3407]
mysqld.exe!que_thr_step()[que0que.cc:1035]
mysqld.exe!que_run_threads_low()[que0que.cc:1115]
mysqld.exe!que_run_threads()[que0que.cc:1157]
mysqld.exe!que_eval_sql()[que0que.cc:1232]
mysqld.exe!row_drop_table_for_mysql()[row0mysql.cc:3998]
mysqld.exe!ha_innobase::delete_table()[ha_innodb.cc:13670]
mysqld.exe!handler::ha_delete_table()[handler.cc:4335]
mysqld.exe!ha_delete_table()[handler.cc:2350]
mysqld.exe!mysql_rm_table_no_locks()[sql_table.cc:2466]
mysqld.exe!mysql_rm_table()[sql_table.cc:2086]
mysqld.exe!mysql_execute_command()[sql_parse.cc:4739]
mysqld.exe!mysql_parse()[sql_parse.cc:7887]
mysqld.exe!dispatch_command()[sql_parse.cc:1804]
mysqld.exe!do_command()[sql_parse.cc:1359]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:366]
mysqld.exe!tp_callback()[threadpool_common.cc:192]
mysqld.exe!work_callback()[threadpool_win.cc:451]
ntdll.dll!LdrRegisterDllNotification()
ntdll.dll!TpCallbackIndependent()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x1fa1d548): drop table tinno
Connection ID (thread ID): 8
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
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.
Attachments
Issue Links
- relates to
-
MDEV-9977 Crash when accessing large (>4G) InnoDB table on MariaDB 10.1.x 32-bit binaries
- Closed
-
MDEV-11849 Fix storage/innobase/* compile warnings
- Closed
-
MDEV-13013 InnoDB unnecessarily extends data files
- Closed
-
MDEV-29165 Merge new release of InnoDB 5.7.39 to 10.3
- Closed