Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-19813 Aria crash recovery failures
  3. MDEV-19718

Assertion `rownr == 0 && new_page' failed upon Aria crash recovery

    XMLWordPrintable

Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
    • N/A
    • Storage Engine - Aria
    • None

    Description

      10.3 7060b032

      2019-06-08 15:12:22 0 [Note] mysqld: Aria engine: starting recovery
      recovered pages: 0% 10% 20% 30% 40% 50% 60% 70% 80% 90%mysqld: /data/src/10.3/storage/maria/ma_blockrec.c:6358: _ma_apply_redo_insert_row_head_or_tail: Assertion `rownr == 0 && new_page' failed.
      190608 15:12:28 [ERROR] mysqld got signal 6 ;
       
      6  0x00007f0862a50e67 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x563229ac76f4 "rownr == 0 && new_page", file=file@entry=0x563229ac5ea0 "/data/src/10.3/storage/maria/ma_blockrec.c", line=line@entry=6358, function=function@entry=0x563229ac7ee0 <__PRETTY_FUNCTION__.16960> "_ma_apply_redo_insert_row_head_or_tail") at assert.c:92
      #7  0x00007f0862a50f12 in __GI___assert_fail (assertion=0x563229ac76f4 "rownr == 0 && new_page", file=0x563229ac5ea0 "/data/src/10.3/storage/maria/ma_blockrec.c", line=6358, function=0x563229ac7ee0 <__PRETTY_FUNCTION__.16960> "_ma_apply_redo_insert_row_head_or_tail") at assert.c:101
      #8  0x0000563229589835 in _ma_apply_redo_insert_row_head_or_tail (info=0x56322b818a10, lsn=4396194268, page_type=1, new_page=0 '\000', header=0x56322b8d8472 "\001", data=0x56322b8d8478 "", data_length=35) at /data/src/10.3/storage/maria/ma_blockrec.c:6358
      #9  0x0000563229550544 in exec_REDO_LOGREC_REDO_INSERT_ROW_HEAD (rec=0x7ffcc5f93d80) at /data/src/10.3/storage/maria/ma_recovery.c:1558
      #10 0x000056322954e180 in display_and_apply_record (log_desc=0x56322ac11108 <log_record_type_descriptor+72>, rec=0x7ffcc5f93d80) at /data/src/10.3/storage/maria/ma_recovery.c:595
      #11 0x000056322955336e in run_redo_phase (lsn=4367068051, lsn_end=0, apply=MARIA_LOG_APPLY) at /data/src/10.3/storage/maria/ma_recovery.c:2715
      #12 0x000056322954d990 in maria_apply_log (from_lsn=4367068051, end_lsn=0, apply=MARIA_LOG_APPLY, trace_file=0x0, should_run_undo_phase=1 '\001', skip_DDLs_arg=1 '\001', take_checkpoints=1 '\001', warnings_count=0x7ffcc5f98300) at /data/src/10.3/storage/maria/ma_recovery.c:350
      #13 0x000056322954d5ff in maria_recovery_from_log () at /data/src/10.3/storage/maria/ma_recovery.c:240
      #14 0x000056322951fe73 in ha_maria_init (p=0x56322b740e60) at /data/src/10.3/storage/maria/ha_maria.cc:3517
      #15 0x0000563228f3d19a in ha_initialize_handlerton (plugin=0x56322b7372d0) at /data/src/10.3/sql/handler.cc:523
      #16 0x0000563228c59e83 in plugin_initialize (tmp_root=0x7ffcc5f98720, plugin=0x56322b7372d0, argc=0x56322a37d7b0 <remaining_argc>, argv=0x56322b6cad68, options_only=false) at /data/src/10.3/sql/sql_plugin.cc:1432
      #17 0x0000563228c5ab2c in plugin_init (argc=0x56322a37d7b0 <remaining_argc>, argv=0x56322b6cad68, flags=2) at /data/src/10.3/sql/sql_plugin.cc:1714
      #18 0x0000563228b22ea6 in init_server_components () at /data/src/10.3/sql/mysqld.cc:5423
      #19 0x0000563228b24016 in mysqld_main (argc=11, argv=0x56322b6cad68) at /data/src/10.3/sql/mysqld.cc:6030
      #20 0x0000563228b18a00 in main (argc=11, argv=0x7ffcc5f98f58) at /data/src/10.3/sql/main.cc:25
      

      To reproduce:

      10.1, 10.2 and 10.4 also crash on the same datadir.

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              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.