Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.1.17
-
None
-
CentOS 7.2 docker container
Description
On optimizing a large table, while writing a temporary file, the disk runs out of space and
mysqld crashes with signal 6:
2016-09-28 1:24:58 140093479201536 [Note] InnoDB: Online DDL : Start building index `GEN_CLUST_INDEX` (1 / 1), estimated cost : 30.0000
|
2016-09-28 01:25:32 7f6a0e102b00 InnoDB: Error: Write to file ./kt/#sql-ib8466-2005151349.ibd failed at offset 146800640.
|
InnoDB: 1048576 bytes should have been written, only 0 were written.
|
InnoDB: Operating system error number 28.
|
InnoDB: Check that your OS and file system support files of this size.
|
InnoDB: Check also that the disk is not full or a disk quota exceeded.
|
InnoDB: Error number 28 means 'No space left on device'.
|
InnoDB: Some operating system error numbers are described at
|
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
|
FAILFAIL2016-09-28 1:25:33 140093479201536 [Note] InnoDB: Online DDL : End of building index `GEN_CLUST_INDEX` (1 / 1)
|
2016-09-28 1:25:33 140093479201536 [Note] InnoDB: Online DDL : Completed
|
2016-09-28 01:25:33 7f6a0e102b00 InnoDB: Assertion failure in thread 140093479201536 in file handler0alter.cc line 137
|
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.6/en/forcing-innodb-recovery.html
|
InnoDB: about forcing recovery.
|
160928 1:25:33 [ERROR] 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.
|
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.1.17-MariaDB
|
key_buffer_size=524288
|
read_buffer_size=131072
|
max_used_connections=1
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 336561 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
Thread pointer: 0x0x7f69ed82b008
|
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 = 0x7f6a0e1018d0 thread_stack 0x48400
|
mysqld(my_print_stacktrace+0x2e)[0x7f6a0ecaeebe]
|
mysqld(handle_fatal_signal+0x2d5)[0x7f6a0e7d5915]
|
/lib64/libpthread.so.0(+0xf100)[0x7f6a0ddf3100]
|
/lib64/libc.so.6(gsignal+0x37)[0x7f6a0c14c5f7]
|
/lib64/libc.so.6(abort+0x148)[0x7f6a0c14dce8]
|
mysqld(+0x738a11)[0x7f6a0e95ca11]
|
mysqld(+0x73db1a)[0x7f6a0e961b1a]
|
addr2line: 'mysqld': No such file
|
mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x252e)[0x7f6a0e6e0e3e]
|
mysqld(_Z20mysql_recreate_tableP3THDP10TABLE_LISTb+0x15d)[0x7f6a0e6e26dd]
|
mysqld(+0x50c8a9)[0x7f6a0e7308a9]
|
mysqld(_ZN22Sql_cmd_optimize_table7executeEP3THD+0xf4)[0x7f6a0e7316a4]
|
mysqld(_Z21mysql_execute_commandP3THD+0x1206)[0x7f6a0e651356]
|
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28e)[0x7f6a0e6599be]
|
mysqld(_ZN15Query_log_event14do_apply_eventEP14rpl_group_infoPKcj+0x11e8)[0x7f6a0e8ac5a8]
|
mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14rpl_group_infoP19rpl_parallel_thread+0x1e1)[0x7f6a0e5dbdd1]
|
mysqld(handle_slave_sql+0x259b)[0x7f6a0e5df76b]
|
/lib64/libpthread.so.0(+0x7dc5)[0x7f6a0ddebdc5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f6a0c20dced]
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f69ed8572f1): is an invalid pointer
|
Connection ID (thread ID): 5
|
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=off
|
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.
|
We think the query pointer is invalid, but we will try to print it anyway.
|
Query: optimize table il_InputLogs
|