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

InnoDB: Assertion failure in file buf0buf.cc line 5963 (Failing assertion: key_version == 0 || key_version >= bpage->key_version)

Details

    • 10.1.8-4

    Description

      Stack:

      2015-07-21 11:01:11 3fff69bff140  InnoDB: Assertion failure in thread 70366223397184 in file buf0buf.cc line 5963
      InnoDB: Failing assertion: key_version == 0 || key_version >= bpage->key_version
      InnoDB: We intentionally generate a memory trap.
      mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x48000
      mysys/stacktrace.c:246(my_print_stacktrace)[0x5b5397dc]
      sql/signal_handler.cc:153(handle_fatal_signal)[0x5aca1b58]
      linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fff7af60478]
      /opt/at8.0/lib64/power8/libc.so.6(gsignal-0x187978)[0x3fff7a5f0b60]
      /opt/at8.0/lib64/power8/libc.so.6(abort-0x18549c)[0x3fff7a5f34a4]
      buf/buf0buf.cc:5963(buf_page_encrypt_before_write(buf_page_t*, unsigned char*, unsigned long))[0x5b3bb0e0]
      buf/buf0flu.cc:954(buf_flush_write_block_low)[0x5b3ca72c]
      buf/buf0flu.cc:1116(buf_flush_page(buf_pool_t*, buf_page_t*, buf_flush_t, bool))[0x5b3cae74]
      buf/buf0flu.cc:1328(buf_flush_try_neighbors)[0x5b3cb660]
      buf/buf0flu.cc:1416(buf_flush_page_and_try_neighbors)[0x5b3cba38]
      buf/buf0flu.cc:1745(buf_do_flush_list_batch)[0x5b3cc6ec]
      buf/buf0flu.cc:1821(buf_flush_batch(buf_pool_t*, buf_flush_t, unsigned long, unsigned long, bool, flush_counters_t*))[0x5b3ccb48]
      buf/buf0flu.cc:2103(buf_flush_list(unsigned long, unsigned long, unsigned long*))[0x5b3cd54c]
      buf/buf0flu.cc:2416(page_cleaner_do_flush_batch)[0x5b3ce2bc]
      buf/buf0flu.cc:2786(buf_flush_page_cleaner_thread)[0x5b3cf52c]
      /opt/at8.0/lib64/power8/libpthread.so.0(+0xb8a0)[0x3fff7af2b8a0]
      /opt/at8.0/lib64/power8/libc.so.6(clone-0xa7018)[0x3fff7a6da1c0]

      Attachments

        Issue Links

          Activity

            Still happens:
            http://buildbot.askmonty.org/buildbot/builders/p8-rhel7-bintar-debug/builds/834/steps/test/logs/stdio

            Version: '10.1.8-MariaDB-debug-log'  socket: '/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/tmp/4/mysqld.1.sock'  port: 16060  Source distribution
            2015-09-28 06:55:47 3fff7efff140  InnoDB: Assertion failure in thread 70366579913024 in file buf0buf.cc line 6019
            InnoDB: Failing assertion: key_version == 0 || key_version >= bpage->key_version
            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.
            150928  6:55:47 [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 http://kb.askmonty.org/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.8-MariaDB-debug-log
            key_buffer_size=1048576
            read_buffer_size=131072
            max_used_connections=1
            max_threads=153
            thread_count=0
            It is possible that mysqld could use up to 
            key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62963 K  bytes of memory
            Hope that's ok; if not, decrease some variables in the equation.
             
            Thread pointer: 0x0x0
            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 0x48000
            mysys/stacktrace.c:246(my_print_stacktrace)[0x396e806c]
            sql/signal_handler.cc:160(handle_fatal_signal)[0x38df1d00]
            linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fff942b0478]
            /opt/at8.0/lib64/power8/libc.so.6(gsignal-0x19261c)[0x3fff93900e6c]
            /opt/at8.0/lib64/power8/libc.so.6(abort-0x18ff64)[0x3fff9390398c]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x16c0cc)[0x3fff8bf3c0cc]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b014)[0x3fff8bf4b014]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b708)[0x3fff8bf4b708]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17bfe4)[0x3fff8bf4bfe4]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17c36c)[0x3fff8bf4c36c]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17ce4c)[0x3fff8bf4ce4c]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(_Z15buf_flush_batchP10buf_pool_t11buf_flush_tmmP16flush_counters_t-0x409b64)[0x3fff8bf4d274]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17db04)[0x3fff8bf4db04]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x21191c)[0x3fff8bfe191c]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x211e34)[0x3fff8bfe1e34]
            /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x212144)[0x3fff8bfe2144]
            /opt/at8.0/lib64/power8/libpthread.so.0(+0xbcec)[0x3fff9426bcec]
            /opt/at8.0/lib64/power8/libc.so.6(clone-0xa814c)[0x3fff939f403c]
            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

            elenst Elena Stepanova added a comment - Still happens: http://buildbot.askmonty.org/buildbot/builders/p8-rhel7-bintar-debug/builds/834/steps/test/logs/stdio Version: '10.1.8-MariaDB-debug-log' socket: '/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/tmp/4/mysqld.1.sock' port: 16060 Source distribution 2015-09-28 06:55:47 3fff7efff140 InnoDB: Assertion failure in thread 70366579913024 in file buf0buf.cc line 6019 InnoDB: Failing assertion: key_version == 0 || key_version >= bpage->key_version 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. 150928 6:55:47 [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 http://kb.askmonty.org/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.8-MariaDB-debug-log key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62963 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 0x0x0 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 0x48000 mysys/stacktrace.c:246(my_print_stacktrace)[0x396e806c] sql/signal_handler.cc:160(handle_fatal_signal)[0x38df1d00] linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fff942b0478] /opt/at8.0/lib64/power8/libc.so.6(gsignal-0x19261c)[0x3fff93900e6c] /opt/at8.0/lib64/power8/libc.so.6(abort-0x18ff64)[0x3fff9390398c] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x16c0cc)[0x3fff8bf3c0cc] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b014)[0x3fff8bf4b014] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b708)[0x3fff8bf4b708] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17bfe4)[0x3fff8bf4bfe4] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17c36c)[0x3fff8bf4c36c] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17ce4c)[0x3fff8bf4ce4c] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(_Z15buf_flush_batchP10buf_pool_t11buf_flush_tmmP16flush_counters_t-0x409b64)[0x3fff8bf4d274] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17db04)[0x3fff8bf4db04] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x21191c)[0x3fff8bfe191c] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x211e34)[0x3fff8bfe1e34] /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x212144)[0x3fff8bfe2144] /opt/at8.0/lib64/power8/libpthread.so.0(+0xbcec)[0x3fff9426bcec] /opt/at8.0/lib64/power8/libc.so.6(clone-0xa814c)[0x3fff939f403c] 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

            commit 5e7f100bf55e65f4a4f38dbe6d79a0db70b4acf8
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Thu Oct 1 13:50:11 2015 +0300

            MDEV-8523: InnoDB: Assertion failure in file buf0buf.cc line 5963 (Failing assertion: key_version == 0 || key_version >= bpage->key_version)

            jplindst Jan Lindström (Inactive) added a comment - commit 5e7f100bf55e65f4a4f38dbe6d79a0db70b4acf8 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Thu Oct 1 13:50:11 2015 +0300 MDEV-8523 : InnoDB: Assertion failure in file buf0buf.cc line 5963 (Failing assertion: key_version == 0 || key_version >= bpage->key_version)

            People

              jplindst Jan Lindström (Inactive)
              jplindst Jan Lindström (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.