Percona Server moved to https://jira.percona.com/projects/PS

Bug #1653764
Comment #14

Comment 14 for bug 1653764

Revision history for this message

luojia (luojia) wrote on 2018-07-11:

#14

when truncate table,We have the same problem in 5.7.21-21-log Percona Server (GPL), Release 21, Revision 2a37e4e.
Linux version 2.6.32-431.20.3.el6.mt20161028.x86_64 (<email address hidden>) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Fri Oct 28 17:50:35 CST 2016
log:
2018-07-06T20:01:18.064913+08:00 0 [ERROR] InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page 3910:31517
2018-07-06T20:01:18.064980+08:00 0 [ERROR] InnoDB: Submit a detailed bug report to http://bugs.mysql.com
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
0: len 4; hex 00000e59; asc Y;;
1: len 1; hex 00; asc ;;
2: len 4; hex 0019515f; asc Q_;;
3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc ; (total 34 bytes);
4: len 3; hex 303034; asc 004;;
5: len 2; hex 5052; asc PR;;
6: len 2; hex 3039; asc 09;;
7: len 6; hex 2a2a2a2a2a2a; asc ******;;
8: len 4; hex 8d78f926; asc x &;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
0: len 4; hex 00000e59; asc Y;;
1: len 1; hex 00; asc ;;
2: len 4; hex 0019515f; asc Q_;;
3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc ; (total 34 bytes);
4: len 3; hex 303034; asc 004;;
5: len 2; hex 5052; asc PR;;
6: len 2; hex 3039; asc 09;;
7: len 6; hex 2a2a2a2a2a2a; asc ******;;
8: len 4; hex 8d78f926; asc x &;;
DATA TUPLE: 3 fields;
0: len 4; hex 00000f46; asc F;;
1: len 1; hex 00; asc ;;
2: len 4; hex 00007b1d; asc { ;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 32
0: len 4; hex 00000f46; asc F;;
1: len 1; hex 00; asc ;;
2: len 4; hex 00007b1d; asc { ;;
3: len 30; hex 000400010c0f0020802d0c0f000c802d0c0f0014002d0c0f0014002d8608; asc - - - - ; (total 34 bytes);
4: len 6; hex 523150314752; asc R1P1GR;;
5: len 2; hex 4b4c; asc KL;;
6: len 3; hex 415448; asc ATH;;
7: len 3; hex 545045; asc TPE;;
8: len 8; hex 80000000f29c7f54; asc T;;
2018-07-06T20:01:18.070471+08:00 0 [ERROR] [FATAL] InnoDB: Failed to restore ibuf position.
2018-07-06 20:01:18 0x7f828f8ca700 InnoDB: Assertion failure in thread 140198730835712 in file ut0ut.cc line 943
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.
12:01:18 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=981
max_threads=10010
thread_count=912
connection_count=910
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 83374237 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...lect some information that could help diagnose the problem.
stack_bottom = 0 thread_stack 0x80000efinitely wrong, the information
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec6cdc]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79bab1]g any
/lib64/libpthread.so.0(+0xf7e0)[0x7f9dc54567e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f9dc368f495]
/lib64/libc.so.6(abort+0x175)[0x7f9dc3690c75]
/usr/sbin/mysqld[0x769826]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x111befe]
/usr/sbin/mysqld[0xfb440e]
/usr/sbin/mysqld[0xfb6431]
/usr/sbin/mysqld(_Z29ibuf_merge_or_delete_for_pageP11buf_block_tRK9page_id_tPK11page_size_tm+0xbe8)[0xfbce38]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x5bc)[0x115ef1c]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x13f)[0x11d724f]
/usr/sbin/mysqld(io_handler_thread+0xc0)[0x10bc190]
/lib64/libpthread.so.0(+0x7aa1)[0x7f9dc544eaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f9dc3745bcd]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2018-07-06T20:03:41.840877+08:00 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2018-07-06T20:03:41.841008+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-07-06T20:03:41.841748+08:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2018-07-06T20:03:41.841776+08:00 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2018-07-06T20:03:41.841800+08:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-21-log) starting as process 146817 ...
2018-07-06T20:03:41.861955+08:00 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2018-07-06T20:03:41.862058+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2018-07-06T20:03:41.862074+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-07-06T20:03:41.862079+08:00 0 [Note] InnoDB: Uses event mutexes
2018-07-06T20:03:41.862083+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-07-04T15:27:31.218883+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-07-04T15:27:31.218888+08:00 0 [Note] InnoDB: Using Linux native AIO
2018-07-04T15:27:31.225237+08:00 0 [Note] InnoDB: Number of pools: 1
2018-07-04T15:27:31.229872+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2018-07-04T15:27:31.232669+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 100G, instances = 4, chunk size = 128M
2018-07-04T15:27:33.886134+08:00 0 [Note] InnoDB: Completed initialization of buffer pool

when truncate table,We have the same problem in 	5.7.21-21-log Percona Server (GPL), Release 21, Revision 2a37e4e.
Linux version 2.6.32-431.20.3.el6.mt20161028.x86_64 (sankuai@kerneltest2.office.mos) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Fri Oct 28 17:50:35 CST 2016
log:
2018-07-06T20:01:18.064913+08:00 0 [ERROR] InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page 3910:31517
2018-07-06T20:01:18.064980+08:00 0 [ERROR] InnoDB: Submit a detailed bug report to http://bugs.mysql.com
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
 0: len 4; hex 00000e59; asc    Y;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 0019515f; asc   Q_;;
 3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc                               ; (total 34 bytes);
 4: len 3; hex 303034; asc 004;;
 5: len 2; hex 5052; asc PR;;
 6: len 2; hex 3039; asc 09;;
 7: len 6; hex 2a2a2a2a2a2a; asc ******;;
 8: len 4; hex 8d78f926; asc  x &;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
 0: len 4; hex 00000e59; asc    Y;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 0019515f; asc   Q_;;
 3: len 30; hex 000300010c0f000c00e00c0f001000e00c0f000800e00c0f002000e08603; asc                               ; (total 34 bytes);
 4: len 3; hex 303034; asc 004;;
 5: len 2; hex 5052; asc PR;;
 6: len 2; hex 3039; asc 09;;
 7: len 6; hex 2a2a2a2a2a2a; asc ******;;
 8: len 4; hex 8d78f926; asc  x &;;
DATA TUPLE: 3 fields;
 0: len 4; hex 00000f46; asc    F;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00007b1d; asc   { ;;
PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 32
 0: len 4; hex 00000f46; asc    F;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00007b1d; asc   { ;;
 3: len 30; hex 000400010c0f0020802d0c0f000c802d0c0f0014002d0c0f0014002d8608; asc          -     -     -     -  ; (total 34 bytes);
 4: len 6; hex 523150314752; asc R1P1GR;;
 5: len 2; hex 4b4c; asc KL;;
 6: len 3; hex 415448; asc ATH;;
 7: len 3; hex 545045; asc TPE;;
 8: len 8; hex 80000000f29c7f54; asc        T;;
2018-07-06T20:01:18.070471+08:00 0 [ERROR] [FATAL] InnoDB: Failed to restore ibuf position.
2018-07-06 20:01:18 0x7f828f8ca700  InnoDB: Assertion failure in thread 140198730835712 in file ut0ut.cc line 943
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.
12:01:18 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=981
max_threads=10010
thread_count=912
connection_count=910
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 83374237 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.