Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-26766

Unable to restore Maria db database from Backup file




      Unable to restore Maria db database from backup file. Tried all 6 recovery modes but the result is same.

      bash-4.2$ cat heuristic_recover.log
      2021-10-02 1:22:15 0 [Note] InnoDB: Using Linux native AIO
      2021-10-02 1:22:15 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2021-10-02 1:22:15 0 [Note] InnoDB: Uses event mutexes
      2021-10-02 1:22:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2021-10-02 1:22:15 0 [Note] InnoDB: Number of pools: 1
      2021-10-02 1:22:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2021-10-02 1:22:15 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      2021-10-02 1:22:15 0 [Note] InnoDB: Completed initialization of buffer pool
      2021-10-02 1:22:15 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2021-10-02 1:22:15 0 [Note] InnoDB: The log sequence number 98679815448 in the system tablespace does not match the log sequence number 98679815692 in the ib_logfiles!
      2021-10-02 1:22:15 0 [Note] InnoDB: Last binlog file './nbp-cmdb-mariadb-0-bin.000050', position 403509723
      2021-10-02 01:22:15 0x7f94b57b08c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.24/storage/innobase/btr/btr0pcur.cc line 471
      InnoDB: Failing assertion: btr_page_get_prev(next_page) == btr_pcur_get_block(cursor)->page.id.page_no()
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      211002 1:22: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 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.3.24-MariaDB
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4532509 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 0x49000
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /mariadb/data
      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 unlimited unlimited bytes
      Max resident set unlimited unlimited bytes
      Max processes unlimited unlimited processes
      Max open files 1048576 1048576 files
      Max locked memory 65536 65536 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 1545308 1545308 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: core




            marko Marko Mäkelä
            nareshnr7 Naresh reddy R nimmala
            1 Vote for this issue
            7 Start watching this issue



                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.