[MDEV-14359] tokudb.dir_per_db_rename_to_nonexisting_schema failed in buildbot on DROP DATABASE Created: 2017-11-10  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - TokuDB, Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/bld-starfs-release/builds/333/steps/test/logs/stdio

tokudb.dir_per_db_rename_to_nonexisting_schema w2 [ fail ]
        Test ended at 2017-10-19 05:35:44
 
CURRENT_TEST: tokudb.dir_per_db_rename_to_nonexisting_schema
mysqltest: At line 20: query 'DROP DATABASE new_db' failed: 1010: Error dropping database (can't rmdir './new_db', errno: 39 "Directory not empty")
 
The result from queries just before the failure was:
SET GLOBAL tokudb_dir_per_db=true;
######
# Tokudb and mysql data dirs are the same, rename to existent db
###
CREATE DATABASE new_db;
CREATE TABLE t1 (id INT AUTO_INCREMENT PRIMARY KEY NOT NULL) ENGINE=tokudb;
ALTER TABLE test.t1 RENAME new_db.t1;
The content of "test" directory:
The content of "new_db" directory:
db.opt
t1.frm
t1_main_id.tokudb
t1_status_id.tokudb
DROP DATABASE new_db;


Generated at Thu Feb 08 08:12:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.