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

Mariabackup --apply-log-only crashes if incomplete transactions with update_undo logs are present




      When I am trying to apply-log-only my Incremental backup, I started to see this error frequently, like 1 or 2 times a week. Could not reach information on the Internet. So I am reporting it as a bug.

      This error started to appear after I upgraded MariaDB server and backup from 10.1.26 to 10.1.28. Previously, I did not encounter this error.

      CurrentIy I cannot provide a full and an incremental backup because database is nearly 400 GB. However, next time the error happens, I can provide desktop sharing if desired.

      Here is the stack trace from the logs:

      2017-11-08 1:13:10 139887762020384 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      2017-11-08 1:13:10 139887762020384 [Note] InnoDB: Read redo log up to LSN=63569216412160
      InnoDB: 1 transaction(s) which must be rolled back or cleaned up
      InnoDB: in total 9 row operations to undo
      InnoDB: Trx id counter is 45387091968
      2017-11-08 1:13:21 139887762020384 [Note] InnoDB: Starting final batch to recover 5944 pages from redo log
      2017-11-08 1:13:25 139878396319488 [Note] InnoDB: To recover: 5269 pages from log
      2017-11-08 1:13:40 139878406809344 [Note] InnoDB: To recover: 3861 pages from log
      2017-11-08 1:13:55 139887657346816 [Note] InnoDB: To recover: 738 pages from log
      InnoDB: Last MySQL binlog file position 0 23440540, file name ./saturn.000033
      InnoDB: Last MySQL binlog file position 0 23440540, file name ./saturn.000033

      xtrabackup: Recovered WSREP position: 00000000-0000-0000-0000-000000000000:-1
      xtrabackup: starting shutdown with innodb_fast_shutdown = 1
      2017-11-08 1:14:00 139887762020384 [Note] InnoDB: Starting shutdown...
      2017-11-08 01:14:02 7f3a285d1820 InnoDB: Assertion failure in thread 139887762020384 in file trx0undo.cc line 2022
      InnoDB: Failing assertion: srv_read_only_mode || srv_force_recovery >= SRV_FORCE_NO_TRX_UNDO
      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.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      171108 1:14:02 [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.1.28-MariaDB
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5311 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 0x48400
      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.


        Issue Links



              marko Marko Mäkelä
              gokhan Gokhan Demir
              0 Vote for this issue
              2 Start watching this issue



                Git Integration

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