Mariadb + tokudb startup error

An error occurred in the system while using tokudb, and after rebooting the computer, the database does not run with the message below.

Thu Apr 14 13:40:14 2022 PerconaFT recovery starting in env /var/lib/mysql/
Thu Apr 14 13:40:14 2022 PerconaFT recovery scanning backward from 12564896439
Thu Apr 14 13:40:15 2022 PerconaFT recovery bw_end_checkpoint at 12564891742 timestamp 1649903938270494 xid 12564891448 (bw_newer)
Thu Apr 14 13:40:15 2022 PerconaFT recovery bw_begin_checkpoint at 12564891448 timestamp 1649903934833060 (bw_between)
Thu Apr 14 13:40:15 2022 PerconaFT recovery turning around at begin checkpoint 12564891448 time 3437434
Thu Apr 14 13:40:15 2022 PerconaFT recovery starts scanning forward to 12564896439 from 12564891448 left 4991 (fw_between)
/home/buildbot/buildbot/build/mariadb-10.4.12/storage/tokudb/PerconaFT/ft/serialize/ft_node-serialize.cc:1175:verify_ftnode_sub_block - file[unknown], blocknum[733], stored_xsum[1179653659] != actual_xsum[148357199]
0x7f2c8f19e7c0: BB250000000100000000007D1E2C060204000000D00C3DA90000000001000000050000000024650400B10700000AE0FCCA020079000000265A08000000000002
0x7f2c8f19e800: 0000000001B93C000000000000000000000000000000000000000000000000000062455226625621FC0001000000010000004D0059008600E600E6005B3131EB
0x7f2c8f19e840: A788ECA1B45D20EC838CEB9494EC8AA4ED81AC20ED9CB4EB8C80EC9AA9207373642032ED858CEB9DBC20283234382C373430EC9B902FEC9AB0ECA3BCED8CA8EC
0x7f2c8f19e880: 8AA4EBACB4EBA38C29EC868CED8388ED9598EAB28C68747470733A2F2F7777772E313173742E636F2E6B722F70726F64756374732F70612F3336333039363132
0x7f2c8f19e8c0: 303168747470733A2F2F63646E2E30313173742E636F6D2F313164696D732F726573697A652F363030783630302F7175616C6974792F37352F31317372632F61
0x7f2c8f19e900: 73696E2F423038484E33375843312F422E6A70673F31363438313932393738303530630200003C696D67207372633D27687474703A2F2F63646E2E6465616C62
0x7f2c8f19e940: 6164612E636F6D2F726573746170692F696D6167652F726573697A6557696474682F313038302F646174612F656469746F722F323230332F6236383431623231



many code



0x7f2c8f1b09c0: 746170692F696D6167652F726573697A6557696474682F313038302F646174612F656469746F722F323230332F62363834316232316361653230646664356135
0x7f2c8f1b0a00: 623834326637366564386566315F313634383731303132395F3134362E4A5047225D000000002500000000000000D9070000B20F00008B170000641F00003D27
0x7f2c8f1b0a40: 0000162F0000EF360000C83E0000A14600007A4E0000535600002C5E000005660000DE6D0000B7750000907D000069850000428D00001B950000F49C0000CDA4
0x7f2c8f1b0a80: 0000A6AC00007FB4000058BC000031C400000ACC0000E3D30000BCDB000095E300006EEB000047F3000020FB0000F9020100D20A0100AB120100841A01000000
0x7f2c8f1b0ac0: 00001B165046
/home/buildbot/buildbot/build/mariadb-10.4.12/storage/tokudb/PerconaFT/ft/serialize/ft_node-serialize.cc:1394:deserialize_ftnode_partition - file[unknown], blocknum[733], verify_ftnode_sub_block failed with -100015
Checksum failure while reading node partition in file ./_mqoo_sql_5d2_700890_main_22064335d_1_1d_B_0.tokudb.
220414 13:40:15 [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 MariaDB Community Bug Reporting - MariaDB Knowledge Base

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.4.12-MariaDB-1:10.4.12+maria~disco-log
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=129
thread_count=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 684859 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 = 0x0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55cc8d57c6de]
/usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55cc8d07222d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13f40)[0x7f2cc8666f40]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f2cc7d77ed7]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f2cc7d59535]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z23toku_ftnode_pf_callbackPvS_S_iP11pair_attr_s+0xad2)[0x7f2cc5544712]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z28toku_deserialize_ftnode_fromi10blocknum_sjPP6ftnodePP16ftnode_disk_dataP18ftnode_fetch_extra+0x8cc)[0x7f2cc552fc5c]
/usr/lib/mysql/plugin/ha_tokudb.so(Z26toku_ftnode_fetch_callbackP9cachefileP6ctpairi10blocknum_sjPPvS5_P11pair_attr_sPiS4+0x4c)[0x7f2cc554481c]
/usr/lib/mysql/plugin/ha_tokudb.so(+0x101fe2)[0x7f2cc5554fe2]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z42toku_cachetable_get_and_pin_with_dep_pairsP9cachefile10blocknum_sjPPv25CACHETABLE_WRITE_CALLBACKPFiS0_P6ctpairiS1_jS3_S3_P11pair_attr_sPiS2_EPFbS2_S2_EPFiS2_S2_S2_iS8_E14pair_lock_typeS2_jPS6_P16cachetable_dirty+0x43a)[0x7f2cc555d9aa]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z30toku_pin_ftnode_with_dep_nodesP2ft10blocknum_sjP18ftnode_fetch_extra14pair_lock_typejPP6ftnodeS7_b+0x128)[0x7f2cc54dc318]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z15toku_pin_ftnodeP2ft10blocknum_sjP18ftnode_fetch_extra14pair_lock_typePP6ftnodeb+0x19)[0x7f2cc54dc3b9]
/usr/lib/mysql/plugin/ha_tokudb.so(+0xf3cbc)[0x7f2cc5546cbc]
/usr/lib/mysql/plugin/ha_tokudb.so(+0xf42ac)[0x7f2cc55472ac]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z20toku_ft_root_put_msgP2ftRK6ft_msgP11txn_gc_info+0x423)[0x7f2cc5547e23]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z19toku_ft_send_insertP9ft_handleP10__toku_dbtS2_P6XIDS_S11ft_msg_typeP11txn_gc_info+0x3d)[0x7f2cc554856d]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z20toku_ft_maybe_insertP9ft_handleP10__toku_dbtS2_P7tokutxnb10__toku_lsnb11ft_msg_type+0x21c)[0x7f2cc554879c]
/usr/lib/mysql/plugin/ha_tokudb.so(+0xb04b2)[0x7f2cc55034b2]
/usr/lib/mysql/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAYSQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x21e)[0x7f2cc55048ce]
/usr/lib/mysql/plugin/ha_tokudb.so(+0x130c51)[0x7f2cc5583c51]
/usr/lib/mysql/plugin/ha_tokudb.so(+0x59e32)[0x7f2cc54ace32]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x68)[0x55cc8d0755f8]
/usr/sbin/mysqld(+0x6b3b69)[0x55cc8ce79b69]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xaaa)[0x55cc8ce7af9a]
/usr/sbin/mysqld(+0x5e396b)[0x55cc8cda996b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x426)[0x55cc8cdaebd6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f2cc7d5ab6b]
/usr/sbin/mysqld(_start+0x2a)[0x55cc8cda277a]
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.
Writing a core file…
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 257219 257219 processes
Max open files 16364 16364 files
Max locked memory 67108864 67108864 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 257219 257219 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/share/apport/apport %p %s %c %d %P

I don’t want integrity, all I need to do is keep the data from the past alive.

log000000052602.tokulog29

If the file is moved to another location

TokuDB: Recovery log is missing (persistent environment information is present) while looking for recovery log files in

It doesn’t work because a message like this is displayed.

I want to quickly find past data.

What should I do best?

Thanks in advance for your reply.