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

Failing assertion: node->modification_counter == node->flush_counter with innodb_flush_method=O_DSYNC

    XMLWordPrintable

    Details

      Description

      got this when shutting down server during heavy write benchmark
      (innodb_flush_method was set to O_DSYNC)
      ...
      I believe I have seen this assertion also with other innodb_flush_methods in the past (e.g nosync)

      -05-11 21:51:59 0x1678  InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\fil\fil0fil.cc line 759
      InnoDB: Failing assertion: node->modification_counter == node->flush_counter || node->space->purpose == FIL_TYPE_TEMPORARY || srv_fast_shutdown == 2 || !srv_was_started
      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/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180511 21:52:00 [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.3.6-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=64
      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 = 212147 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...
      mysqld.exe!my_sigabrt_handler()[my_thr_init.c:485]
      mysqld.exe!raise()[signal.cpp:516]
      mysqld.exe!abort()[abort.cpp:71]
      mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:61]
      mysqld.exe!fil_node_close_file()[fil0fil.cc:756]
      mysqld.exe!fil_close_all_files()[fil0fil.cc:1945]
      mysqld.exe!logs_empty_and_mark_files_at_shutdown()[log0log.cc:2142]
      mysqld.exe!innodb_shutdown()[srv0start.cc:2811]
      mysqld.exe!innobase_end()[ha_innodb.cc:4269]
      mysqld.exe!ha_finalize_handlerton()[handler.cc:463]
      mysqld.exe!plugin_deinitialize()[sql_plugin.cc:1258]
      mysqld.exe!reap_plugins()[sql_plugin.cc:1334]
      mysqld.exe!plugin_shutdown()[sql_plugin.cc:2001]
      mysqld.exe!clean_up()[mysqld.cc:2244]
      mysqld.exe!unireg_end()[mysqld.cc:2116]
      mysqld.exe!kill_server()[mysqld.cc:2042]
      mysqld.exe!handle_shutdown()[mysqld.cc:3712]
      mysqld.exe!pthread_start()[my_winthread.c:62]
      mysqld.exe!thread_start<unsigned int (__cdecl*)(void * __ptr64)>()[thread.cpp:115]
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              wlad Vladislav Vaintroub
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: