Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.5
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
- relates to
-
MDEV-13481 Merge new release of InnoDB MySQL 5.7.19 to 10.2
- Closed