Uploaded image for project: 'Percona XtraBackup'
  1. Percona XtraBackup
  2. PXB-1661

Assertion failure in fsp_reserve_free_extents when preparing incremental backup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Pending Release
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 8.0-2-alpha2
    • Fix Version/s: 8.0-2-alpha2
    • Component/s: None
    • Labels:
      None

      Description

      Command:

      xtrabackup --no-version-check --prepare --apply-log-only --incremental-dir=inc2 --target-dir=backup --transition-key=top-secret
      

      Error log:

      InnoDB: Allocated tablespace ID 4 for test/t3, old maximum was 0
      InnoDB: Starting in background the rollback of uncommitted transactions
      InnoDB: Rolling back trx with id 1595, 1536 rows to undo
      
      InnoDB: Progress in percents: 1InnoDB: 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.
      11:40:05 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=0
      read_buffer_size=131072
      max_used_connections=0
      max_threads=0
      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 = 0 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      
      Thread pointer: 0x7f7ee881ec00
      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 = 70000e9b0b70 thread_stack 0x46000
      InnoDB: xtrabackup: Last MySQL binlog file position 16691, file name mysql-bin.000002
      
      0   xtrabackup                          0x000000010c322df8 my_print_stacktrace(unsigned char*, unsigned long) + 88
      1   xtrabackup                          0x000000010a3fefbb handle_fatal_signal + 923
      2   libsystem_platform.dylib            0x00007fff67aeef5a _sigtramp + 26
      3   ???                                 0x000000011dea66f8 0x0 + 4796868344
      4   libsystem_c.dylib                   0x00007fff6788c1ae abort + 127
      5   xtrabackup                          0x000000010aad6923 ut_dbg_assertion_failed(char const*, char const*, unsigned long) + 371
      6   xtrabackup                          0x000000010a662b55 fsp_reserve_free_extents(unsigned long*, unsigned int, unsigned long, fsp_reserve_t, mtr_t*, unsigned int) + 261
      7   xtrabackup                          0x000000010a45d2e7 btr_cur_pessimistic_delete(dberr_t*, unsigned long, btr_cur_t*, unsigned long, bool, unsigned long long, unsigned long long, unsigned long, mtr_t*) + 2231
      8   xtrabackup                          0x000000010a9d7baa row_undo_ins_remove_clust_rec(undo_node_t*) + 1786
      9   xtrabackup                          0x000000010a9d6eb4 row_undo_ins(undo_node_t*, que_thr_t*) + 580
      10  xtrabackup                          0x000000010a9e28a8 row_undo(undo_node_t*, que_thr_t*) + 440
      11  xtrabackup                          0x000000010a9e24f8 row_undo_step(que_thr_t*) + 184
      12  xtrabackup                          0x000000010a913580 que_thr_step(que_thr_t*) + 928
      13  xtrabackup                          0x000000010a9127d0 que_run_threads_low(que_thr_t*) + 240
      14  xtrabackup                          0x000000010a912593 que_run_threads(que_thr_t*) + 163
      15  xtrabackup                          0x000000010aa98e76 trx_rollback_active(trx_t*) + 822
      16  xtrabackup                          0x000000010aa9784f trx_rollback_resurrected(trx_t*, unsigned long) + 527
      17  xtrabackup                          0x000000010aa9743e trx_rollback_or_clean_recovered(unsigned long) + 830
      18  xtrabackup                          0x000000010aa97945 trx_recovery_rollback_thread() + 117
      19  xtrabackup                          0x0000000109849401 void Runnable::operator()<void (*)()>(void (*&&)()) + 257
      20  xtrabackup                          0x00000001098490a9 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, Runnable, void (*)()> >(void*) + 569
      21  libsystem_pthread.dylib             0x00007fff67af8661 _pthread_body + 340
      22  libsystem_pthread.dylib             0x00007fff67af850d _pthread_body + 0
      23  libsystem_pthread.dylib             0x00007fff67af7bf9 thread_start + 13
      
      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
      
      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.
      

        Attachments

          Activity

            People

            • Assignee:
              sergei.glushchenko Sergei Glushchenko
              Reporter:
              sergei.glushchenko Sergei Glushchenko
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 6 hours
                6h