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

LP:553982 - InnoDB crash: Assertion failure... in file ../../storage/xtradb/include/buf0buf.ic line 544

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Resolution: Incomplete
    • None
    • None
    • None

    Description

      Sorry that this isn't much of a report. Let me know if I can provide more info.

      MariaDB 5.1.39 crashed - the error log reports:

      100402 4:26:23 InnoDB: Assertion failure in thread 139685025216272 in file ../../storage/xtradb/include/buf0buf.ic line 544
      InnoDB: Failing assertion: buf_page_in_file(bpage)
      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.1/en/forcing-recovery.html
      InnoDB: about forcing recovery.
      100402 4:26:23 - 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.
      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.

      key_buffer_size=1073741824
      read_buffer_size=131072
      max_used_connections=154
      max_threads=202
      threads_connected=74
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1903909 K
      bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      thd: 0x7f0adc40de30
      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 = 0x7f0af44eed40 thread_stack 0x48000
      [0x82cf44]
      [0x4ad227]
      [0x60b860]
      [0x8bfc35]
      [0x888691]
      [0x7c9f6f]
      [0x7b88e1]
      [0x7b8e8a]
      [0x77ce65]
      [0x77f4c6]
      [0x726319]
      [0x57ba69]
      [0x50bb81]
      [0x50bf5f]
      [0x51b4be]
      [0x51ccf0]
      [0x51d70c]
      [0x4b814f]
      [0x4ba821]
      [0x4be39b]
      [0x4c0303]
      [0x4c0c86]
      [0x4b3dbb]
      [0x6077f0]
      [0x8abe19]
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort...
      thd->query at 0x7f0ad43b3938 is an invalid pointer
      thd->thread_id=1004063
      thd->killed=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.
      100402 04:26:27 mysqld_safe Number of processes running now: 0
      100402 04:26:27 mysqld_safe mysqld restarted

      Attachments

        Activity

          People

            Unassigned Unassigned
            caseyforbes Casey Forbes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 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.