Hello, tldr - Is there a way (similarly as with the InnoDB workaround of DROP TABLE `#mysql50##sql-..') to delete an orphaned TokuDB table (and/or clean the information_schema.tokudb_file_map)? Or should I address this to Percona/Toku people? The long version: I have noticed on one db instance (currently running 10.0.26) and orphaned table (no idea how it got there): ls -la /data/mysql/db/ -rw-r----- 1 mysql mysql 1114 Jul 29 01:41 #sql-6f2d_9.frm -rw-r----- 1 mysql mysql 908 Jul 29 01:41 #sql-6f2d_9.par Also: MariaDB [(none)]> SELECT * FROM information_schema.tokudb_file_map limit 10; +--------------------------------+-----------------------------------------------------+--------------+------------+-----------------------+ | dictionary_name | internal_file_name | table_schema | table_name | table_dictionary_name | +--------------------------------+-----------------------------------------------------+--------------+------------+-----------------------+ | ./db/#sql-6f2d_9#P#p1-key-aid | ./_db_sql_6f2d_9_P_p1_key_aid_1734_2_1b_B_0.tokudb | db | #sql | 6f2d_9#P#p1-key-aid | | ./db/#sql-6f2d_9#P#p1-main | ./_db_sql_6f2d_9_P_p1_main_1734_2_1b_B_1.tokudb | db | #sql | 6f2d_9#P#p1-main | | ./db/#sql-6f2d_9#P#p1-status | ./_db_sql_6f2d_9_P_p1_status_1609_1_1b.tokudb | db | #sql | 6f2d_9#P#p1-status | .... While I can DROP the table: MariaDB [db]> drop table `#mysql50##sql-6f2d_9`; Query OK, 0 rows affected, 1 warning (3.99 sec) And even physically delete the ./_db_sql_6f2d_9_P* files from the root datadir it never disappears from the information_schema tables. It doesn't seem to currently affect anything but I wanted to know if maybe there is a workaround or other ways to rebuild to Toku directory (without dumping/reimporting the whole database). rr