Description:
I used mysqldump to upgrade the database, but I encountered this error:
2019-06-14T10:05:53.173158+08:002 [System] [MY-011003] [Server] Finished populating Data Dictionary tables with data.
2019-06-14T10:06:00.130977+08:002 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2019-06-14T10:06:00.131003+08:002 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2019-06-14T10:06:00.131025+08:002 [ERROR] [MY-012646] [InnoDB] File. / mysql/innodb_index_stats_backup57.ibd:'open'returned OS 71. Cannot continue operation
2019-06-14T10:06:00.131049+08:002 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.
2019-06-14T10:06:00.190534+08:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0buf.cc:700:srv_shutdown_state <= SRV_SHUTDOWN_FLUSH_PHASE thread 140428286297856
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.
02:06:00 UTC-mysqld got signal 6;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fb8ac6d3bc0
Attempting backtrace. You can use the following information to find out
Where mysqld died. If you see no messages after this, something goes
Terribly wrong...
Stack_bottom = 7fb8021 efc98 thread_stack 0x46000
/ data/arkdb/3310/private/bin/mysqld (my_print_stacktrace (unsigned char*, unsigned long) +0x2e) [0x1d563fe]
/ Data/arkdb/3310/private/bin/mysqld (handle_fatal_signal+0x323) [0xee86f3]
/ lib64/libpthread.so.0 (+0xf5d0) [0x7fb8da2f25d0]
/ lib64/libc.so.6 (gsignal+0x37) [0x7fb8d8632207]
/ lib64/libc.so.6 (abort+0x148) [0x7fb8d86338f8]
/ Data/arkdb/3310/private/bin/mysqld (ut_dbg_assertion_failed (char const*, char const*, unsigned long) +0x2b6) [0x1fdf586]
/ Data/arkdb/3310/private/bin/mysqld (log_buffer_reserve (log_t &, unsigned long) +0x218) [0x1ea4c28]
/ Data/arkdb/3310/private/bin/mysqld (mtr_t::Command::execute()+0x47) [0x1ed4357]
/ data / ARKdb / 3310 / private / bin / mysqld (mtr_t:: commit ()+0x69) [0x1ed4549]
/ data/arkdb/3310/private/bin/mysqld() [0x1fade03]
/ data / ARKdb / 3310 / private / bin / mysqld () [0x1faea17]
/ data / ARKdb / 3310 / private / bin / mysqld (trx_purge (unsigned long, unsigned long, bool) +0x4ec) [0x1fb496c]
/ data/arkdb/3310/private/bin/mysqld (srv_purge_coordinator_thread()+0x88f) [0x1f8835f]
/ Data/arkdb/3310/private/bin/mysqld (std::thread:_State_impl<std:::_Invoker<std::tuple<Runnable,void(*)()> >: _M_run()+0x63) [0x1e0fcf3]
/ data / ARKdb / 3310 / private / bin / mysqld () [0x23c4caf]
/ lib64/libpthread.so.0 (+0x7dd5) [0x7fb8da2eadd5]
/ lib64/libc.so.6 (clone+0x6d) [0x7fb8d86f9ead]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
How to repeat:
I used mysqldump to upgrade the database, but I encountered this error:
2019-06-14T10:05:53.173158+08:002 [System] [MY-011003] [Server] Finished populating Data Dictionary tables with data.
2019-06-14T10:06:00.130977+08:002 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2019-06-14T10:06:00.131003+08:002 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2019-06-14T10:06:00.131025+08:002 [ERROR] [MY-012646] [InnoDB] File. / mysql/innodb_index_stats_backup57.ibd:'open'returned OS 71. Cannot continue operation
2019-06-14T10:06:00.131049+08:002 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.
2019-06-14T10:06:00.190534+08:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0buf.cc:700:srv_shutdown_state <= SRV_SHUTDOWN_FLUSH_PHASE thread 140428286297856
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.
02:06:00 UTC-mysqld got signal 6;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fb8ac6d3bc0
Attempting backtrace. You can use the following information to find out
Where mysqld died. If you see no messages after this, something goes
Terribly wrong...
Stack_bottom = 7fb8021 efc98 thread_stack 0x46000
/ data/arkdb/3310/private/bin/mysqld (my_print_stacktrace (unsigned char*, unsigned long) +0x2e) [0x1d563fe]
/ Data/arkdb/3310/private/bin/mysqld (handle_fatal_signal+0x323) [0xee86f3]
/ lib64/libpthread.so.0 (+0xf5d0) [0x7fb8da2f25d0]
/ lib64/libc.so.6 (gsignal+0x37) [0x7fb8d8632207]
/ lib64/libc.so.6 (abort+0x148) [0x7fb8d86338f8]
/ Data/arkdb/3310/private/bin/mysqld (ut_dbg_assertion_failed (char const*, char const*, unsigned long) +0x2b6) [0x1fdf586]
/ Data/arkdb/3310/private/bin/mysqld (log_buffer_reserve (log_t &, unsigned long) +0x218) [0x1ea4c28]
/ Data/arkdb/3310/private/bin/mysqld (mtr_t::Command::execute()+0x47) [0x1ed4357]
/ data / ARKdb / 3310 / private / bin / mysqld (mtr_t:: commit ()+0x69) [0x1ed4549]
/ data/arkdb/3310/private/bin/mysqld() [0x1fade03]
/ data / ARKdb / 3310 / private / bin / mysqld () [0x1faea17]
/ data / ARKdb / 3310 / private / bin / mysqld (trx_purge (unsigned long, unsigned long, bool) +0x4ec) [0x1fb496c]
/ data/arkdb/3310/private/bin/mysqld (srv_purge_coordinator_thread()+0x88f) [0x1f8835f]
/ Data/arkdb/3310/private/bin/mysqld (std::thread:_State_impl<std:::_Invoker<std::tuple<Runnable,void(*)()> >: _M_run()+0x63) [0x1e0fcf3]
/ data / ARKdb / 3310 / private / bin / mysqld () [0x23c4caf]
/ lib64/libpthread.so.0 (+0x7dd5) [0x7fb8da2eadd5]
/ lib64/libc.so.6 (clone+0x6d) [0x7fb8d86f9ead]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
