mysql - InnoDB：文件 rem0rec.cc 第 586 行中线程 139982489777920 中的断言失败

Question

有人可以帮我理解这个错误吗？或者指出我正确的恢复方向？

这发生在服务器用完磁盘空间并崩溃之后。我在释放磁盘空间时不小心删除了我的备份，所以现在我一直在尝试恢复这个数据库。

我已经尝试按照强制 InnoDB 恢复中提到的指示，innodb_force_recovery = 1一直到 6，但是在启动 mysql 时我得到了同样的错误。

2021-03-10T05:23:07.396530Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2021-03-10T05:23:07.396621Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2021-03-10T05:23:07.565046Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-10T05:23:07.566757Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.32-0ubuntu0.16.04.1) starting as process 13521 ...
2021-03-10T05:23:07.570900Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-03-10T05:23:07.570921Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-10T05:23:07.570928Z 0 [Note] InnoDB: Uses event mutexes
2021-03-10T05:23:07.570931Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-10T05:23:07.570934Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-03-10T05:23:07.570938Z 0 [Note] InnoDB: Using Linux native AIO
2021-03-10T05:23:07.571162Z 0 [Note] InnoDB: Number of pools: 1
2021-03-10T05:23:07.571286Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-03-10T05:23:07.572769Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-10T05:23:07.580436Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-10T05:23:07.582615Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-10T05:23:07.594886Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-10T05:23:07.596654Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89324856058
2021-03-10T05:23:07.739129Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89330098688
2021-03-10T05:23:07.749947Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89330662414
2021-03-10T05:23:07.750223Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-10T05:23:07.750229Z 0 [Note] InnoDB: Starting crash recovery.
2021-03-10T05:23:07.775248Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 2021-03-10 05:23:07 0x7f503693f700  InnoDB: Assertion failure in thread 139982489777920 in file rem0rec.cc line 586
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.
05:23:07 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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 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...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8bf8b]
/usr/sbin/mysqld(handle_fatal_signal+0x36f)[0x772ccf]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f504b56d390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f504a926438]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f504a92803a]
/usr/sbin/mysqld[0x7483ac]
/usr/sbin/mysqld(_Z20rec_get_offsets_funcPKhPK12dict_index_tPmmPP16mem_block_info_t+0x51)[0x1037691]
/usr/sbin/mysqld(_Z36btr_cur_parse_del_mark_set_clust_recPhS_S_P14page_zip_des_tP12dict_index_t+0x185)[0x113c715]
66 67 68 69 70 71 /usr/sbin/mysqld[0xfe8618]
/usr/sbin/mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0x9ad)[0xfe991d]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x3e4)[0x115e884]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x11f)[0x11d532f]
/usr/sbin/mysqld(io_handler_thread+0xd0)[0x10c0270]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f504b5636ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f504a9f84dd]
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.

标签： mysqllinux