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

innodb.alter_kill fails in buildbot with Unknown storage engine 'InnoDB'

    XMLWordPrintable

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-stretch-ppc64le/builds/2273

      innodb.alter_kill 'innodb'               w1 [ fail ]
              Test ended at 2018-05-22 23:06:36
       
      CURRENT_TEST: innodb.alter_kill
      mysqltest: At line 70: query 'SELECT COUNT(*) FROM bug16720368' failed with wrong errno 1286: 'Unknown storage engine 'InnoDB'', instead of 1932...
       
      The result from queries just before the failure was:
      < snip >
      SET GLOBAL innodb_file_per_table=1;
      CREATE TABLE bug16720368_1 (a INT PRIMARY KEY) ENGINE=InnoDB;
      connect  con1,localhost,root;
      CREATE TABLE bug16720368 (a INT PRIMARY KEY, b INT) ENGINE=InnoDB;
      INSERT INTO bug16720368 (a) VALUES (1),(2),(3),(4),(5),(6),(7),(8);
      connection default;
      # Cleanly shutdown mysqld
      disconnect con1;
      # Corrupt FIL_PAGE_OFFSET in bug16720368.ibd,
      # and update the checksum to the "don't care" value.
      # Restart mysqld
      # This will succeed after a clean shutdown, due to
      # fil_open_single_table_tablespace(check_space_id=FALSE).
      SELECT COUNT(*) FROM bug16720368;
      COUNT(*)
      8
      INSERT INTO bug16720368_1 VALUES(1);
      # The table is unaccessible, because after a crash we will
      # validate the tablespace header.
      SELECT COUNT(*) FROM bug16720368;
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: