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

MySQL bug #84038 also affects MariaDB 10.2

    XMLWordPrintable

    Details

      Description

      MySQL bug #84038 is not reproducible on XtraDB based MariaDB 10.1 (at least not on 10.1.21 or later), but is hit in InnoDB based MariaDB 10.2.5

      How to reproduce:

      Execute the following

      mysql <<< "
      DROP DATABASE IF EXISTS test_jfg;
      DROP DATABASE IF EXISTS test_jfg2;
      CREATE DATABASE test_jfg;
      CREATE DATABASE test_jfg2;
      CREATE TABLE test_jfg.test (a int unsigned NOT NULL PRIMARY KEY);
      FLUSH TABLES test_jfg.test FOR EXPORT;"
       
      mysql <<< "
      RENAME TABLE test_jfg.test TO test_jfg2.test;
      DROP DATABASE test_jfg;"
      

      then restart mysqld

      Works fine on MariaDB 10.1, but on 10.2 it causes

      2017-05-22 15:29:31 140342278871232 [ERROR] InnoDB: Operating system error number 2 in a file operation.
      2017-05-22 15:29:31 140342278871232 [ERROR] InnoDB: The error means the system cannot find the path specified.
      2017-05-22 15:29:31 140342278871232 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
      2017-05-22 15:29:31 140342278871232 [ERROR] InnoDB: Cannot open datafile for read-only: './test_jfg/test.ibd' OS error: 71
      2017-05-22 15:29:31 140342278871232 [Note] InnoDB: The InnoDB data dictionary table SYS_DATAFILES for tablespace ID 4 was updated to use file ./test_jfg2/test.ibd.
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              hholzgra Hartmut Holzgraefe
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: