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

[Draft] InnoDB: Assertion failure in thread 139783124801280 in file page0zip.ic line 432

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.1
    • Fix Version/s: N/A
    • Labels:
      None
    • Environment:
      10.1 e333d8296480afc63962892f6c8e101dfcaa2686

      Description

      Crash-upgrade from 10.1.20 to 10.1
      http://buildbot.askmonty.org/buildbot/builders/qa-kvm-linux/builds/1596/steps/upgr_10_1/logs/stdio

      perl /home/buildbot/rqg/runall-new.pl --no-mask --seed=1498129711 --threads=4 --duration=60 --queries=100M --mysqld=--loose-max-statement-time=20 --mysqld=--loose-lock-wait-timeout=20 --mysqld=--innodb-lock-wait-timeout=10 --mysqld=--log-bin --mysqld=--binlog-format=ROW --mysqld=--server-id=111 --grammar=conf/mariadb/oltp.yy --gendata=conf/mariadb/innodb_upgrade.zz --gendata-advanced --upgrade-test=crash --basedir1=/home/buildbot/10.1 --basedir2=/home/buildbot/build --mysqld=--innodb-page-size=4K --mysqld=--innodb-compression-algorithm=none --mysqld=--innodb-file-format=Barracuda --mtr-build-thread=300 --vardir1=/home/buildbot/upgrade-from-10.1/current1_1
      

      # 2017-06-22T07:11:18 [27091] Starting MySQL 10.1.25: "/home/buildbot/build/sql/mysqld" "--no-defaults" "--basedir=/home/buildbot/build" "--lc-messages-dir=/home/buildbot/build/sql/share" "--character-sets-dir=/home/buildbot/build/sql/share/charsets" "--tmpdir=/home/buildbot/upgrade-from-10.1/current1_1/tmp" "--core-file" "--datadir=/home/buildbot/upgrade-from-10.1/current1_1/data" "--max-allowed-packet=128Mb" "--port=13000" "--socket=/home/buildbot/upgrade-from-10.1/current1_1/mysql.sock" "--pid-file=/home/buildbot/upgrade-from-10.1/current1_1/mysql.pid" "--general-log" "--general-log-file=/home/buildbot/upgrade-from-10.1/current1_1/mysql.log" --loose-max-statement-time=20 --loose-lock-wait-timeout=20 --innodb-lock-wait-timeout=10 --log-bin --binlog-format=ROW --server-id=111 --innodb-page-size=4K --innodb-compression-algorithm=none --innodb-file-format=Barracuda --sql-mode=no_engine_substitution
      # 2017-06-22T07:11:25 [27091] --------- Contents of /home/buildbot/upgrade-from-10.1/current1_1/mysql.err -------------
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:19 139783583369088 [Note] /home/buildbot/build/sql/mysqld (mysqld 10.1.25-MariaDB-debug) starting as process 27214 ...
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:19 139783583369088 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=debian-jessie-amd64' or '--log-bin=mysql-bin' to avoid this problem.
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:19 139783583369088 [Note] InnoDB:  innodb-page-size has been changed from the default value 16384 to 4096 .
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: The InnoDB memory heap is disabled
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Compressed tables use zlib 1.2.8
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Using Linux native AIO
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Using generic crc32 instructions
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Completed initialization of buffer pool
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Highest supported file format is Barracuda.
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3619955
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:20 139783583369088 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      # 2017-06-22T07:11:25 [27091] | 2017-06-22  7:11:23 139783583369088 [Note] InnoDB: Starting final batch to recover 1670 pages from redo log
      # 2017-06-22T07:11:25 [27091] | 2017-06-22 07:11:23 7f21cb7fd700  InnoDB: Assertion failure in thread 139783124801280 in file page0zip.ic line 432
      # 2017-06-22T07:11:25 [27091] | InnoDB: We intentionally generate a memory trap.
      # 2017-06-22T07:11:25 [27091] | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      # 2017-06-22T07:11:25 [27091] | InnoDB: If you get repeated assertion failures or crashes, even
      # 2017-06-22T07:11:25 [27091] | InnoDB: immediately after the mysqld startup, there may be
      # 2017-06-22T07:11:25 [27091] | InnoDB: corruption in the InnoDB tablespace. Please refer to
      # 2017-06-22T07:11:25 [27091] | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      # 2017-06-22T07:11:25 [27091] | InnoDB: about forcing recovery.
      # 2017-06-22T07:11:25 [27091] | 170622  7:11:23 [ERROR] mysqld got signal 6 ;
      # 2017-06-22T07:11:25 [27091] | This could be because you hit a bug. It is also possible that this binary
      # 2017-06-22T07:11:25 [27091] | or one of the libraries it was linked against is corrupt, improperly built,
      # 2017-06-22T07:11:25 [27091] | or misconfigured. This error can also be caused by malfunctioning hardware.
      # 2017-06-22T07:11:25 [27091] | 
      # 2017-06-22T07:11:25 [27091] | To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      # 2017-06-22T07:11:25 [27091] | 
      # 2017-06-22T07:11:25 [27091] | We will try our best to scrape up some info that will hopefully help
      # 2017-06-22T07:11:25 [27091] | diagnose the problem, but since we have already crashed, 
      # 2017-06-22T07:11:25 [27091] | something is definitely wrong and this may fail.
      # 2017-06-22T07:11:25 [27091] | 
      # 2017-06-22T07:11:25 [27091] | Server version: 10.1.25-MariaDB-debug
      # 2017-06-22T07:11:25 [27091] | key_buffer_size=134217728
      # 2017-06-22T07:11:25 [27091] | read_buffer_size=131072
      # 2017-06-22T07:11:25 [27091] | max_used_connections=0
      # 2017-06-22T07:11:25 [27091] | max_threads=153
      # 2017-06-22T07:11:25 [27091] | thread_count=0
      # 2017-06-22T07:11:25 [27091] | It is possible that mysqld could use up to 
      # 2017-06-22T07:11:25 [27091] | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467211 K  bytes of memory
      # 2017-06-22T07:11:25 [27091] | Hope that's ok; if not, decrease some variables in the equation.
      # 2017-06-22T07:11:25 [27091] | 
      # 2017-06-22T07:11:25 [27091] | Thread pointer: 0x0
      # 2017-06-22T07:11:25 [27091] | Attempting backtrace. You can use the following information to find out
      # 2017-06-22T07:11:25 [27091] | where mysqld died. If you see no messages after this, something went
      # 2017-06-22T07:11:25 [27091] | terribly wrong...
      # 2017-06-22T07:11:25 [27091] | stack_bottom = 0x0 thread_stack 0x48400
      # 2017-06-22T07:11:25 [27091] | /home/buildbot/build/sql/mysqld(my_print_stacktrace+0x38)[0x7f21e6619c68]
      # 2017-06-22T07:11:25 [27091] | /home/buildbot/build/sql/mysqld(handle_fatal_signal+0x394)[0x7f21e5fbb43d]
      # 2017-06-22T07:11:25 [27091] | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f21e5481890]
      # 2017-06-22T07:11:25 [27091] | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f21e357f067]
      # 2017-06-22T07:11:25 [27091] | /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f21e3580448]
      # 2017-06-22T07:11:25 [27091] | mysys/stacktrace.c:267(my_print_stacktrace)[0x7f21e6201420]
      # 2017-06-22T07:11:25 [27091] | sql/signal_handler.cc:168(handle_fatal_signal)[0x7f21e620379d]
      # 2017-06-22T07:11:25 [27091] | include/page0zip.ic:435(page_zip_parse_compress_no_data)[0x7f21e62041bd]
      # 2017-06-22T07:11:25 [27091] | buf/buf0buf.cc:4888(buf_page_io_complete(buf_page_t*))[0x7f21e637c9a2]
      # 2017-06-22T07:11:25 [27091] | fil/fil0fil.cc:6543(fil_aio_wait(unsigned long))[0x7f21e63f4ca8]
      # 2017-06-22T07:11:25 [27091] | srv/srv0start.cc:584(io_handler_thread)[0x7f21e62e4c62]
      # 2017-06-22T07:11:25 [27091] | /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f21e547a064]
      # 2017-06-22T07:11:25 [27091] | /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f21e363262d]
      # 2017-06-22T07:11:25 [27091] | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      # 2017-06-22T07:11:25 [27091] | information that should help you find out what is causing the crash.
      # 2017-06-22T07:11:25 [27091] | Writing a core file
      # 2017-06-22T07:11:25 [27091] | Aborted (core dumped)
      

      Not easily reproducible.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

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