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

innodb assertion cb->m_err == DB_SUCCESS during shutdown (Windows)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.5.16
    • N/A
    • None
    • Microsoft Windows [Version 10.0.17763.3046]

    Description

      2022-06-15 20:16:41 0 [Note] InnoDB: Starting shutdown...
      2022-06-15 20:16:41 0 [Note] InnoDB: Dumping buffer pool(s) to C:\Program Files\MariaDB 10.5\data\ib_buffer_pool
      2022-06-15 20:16:41 0 [Note] InnoDB: Restricted to 32260 pages due to innodb_buf_pool_dump_pct=25
      2022-06-15 20:16:41 0 [Note] InnoDB: Buffer pool(s) dump completed at 220615 20:16:41
      2022-06-15 20:16:43 0x1478 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 3586
      InnoDB: Failing assertion: cb->m_err == DB_SUCCESS
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      220615 20:16:43 [ERROR] mysqld got exception 0x80000003 ;
      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.5.16-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=31
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 142742808 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...
      2022-06-15 20:17:03 0 [Note] mysqld.exe: Aria engine: starting recovery
      tables to flush: 1 0
      (0.0 seconds);
      2022-06-15 20:17:03 0 [Note] mysqld.exe: Aria engine: recovery done
      2022-06-15 20:17:03 0 [Note] InnoDB: Uses event mutexes
      2022-06-15 20:17:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-06-15 20:17:03 0 [Note] InnoDB: Number of pools: 1
      2022-06-15 20:17:03 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2022-06-15 20:17:03 0 [Note] InnoDB: Initializing buffer pool, total size = 2147483648, chunk size = 134217728
      2022-06-15 20:17:03 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-06-15 20:17:03 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=4137992083426,4137992952560
      2022-06-15 20:17:05 0 [Note] InnoDB: Starting final batch to recover 5918 pages from redo log.
      2022-06-15 20:17:06 0 [Note] InnoDB: 128 rollback segments are active.
      2022-06-15 20:17:07 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-06-15 20:17:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-06-15 20:17:07 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-06-15 20:17:07 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
      2022-06-15 20:17:07 0 [Note] InnoDB: 10.5.16 started; log sequence number 4138040092957; transaction id 4576316017
      2022-06-15 20:17:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 10.5\data\ib_buffer_pool
      2022-06-15 20:17:07 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-06-15 20:17:07 0 [Note] mysqld.exe: SSPI: using principal name 'KV-AS-02$@corp.ukrtelecom.loc', mech 'Negotiate'
      2022-06-15 20:17:07 0 [Note] CONNECT: Version 1.07.0002 May 18 2022 08:16:19
      2022-06-15 20:17:08 0 [Note] Server socket created on IP: '::'.
      2022-06-15 20:17:10 1 [Note] Event Scheduler: scheduler thread started with id 1
      2022-06-15 20:17:10 0 [Note] InnoDB: Buffer pool(s) load completed at 220615 20:17:10
      2022-06-15 20:17:10 0 [Note] Reading of all Master_info entries succeeded
      2022-06-15 20:17:10 0 [Note] Added new Master_info '' to hash table
      2022-06-15 20:17:10 0 [Note] C:\Program Files\MariaDB 10.5\bin\mysqld.exe: ready for connections.
      Version: '10.5.16-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              Sergey_W Sergii Volikov
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.