TokuDB file map table doesn't reflect the real situation of the files on the disk

Sometimes TokuDB tables get corrupted, the server crash and will not start anymore. The only way I found to have the server running, is to delete all the .tokudb, .frm and .par files related to the table that caused the crash. The problem is that the information_schema.TokuDB_file_map table still shows the records related to the table, and any subsequent attempt to recreate the table produces the error: 17 "File exists". As reported in MDEV-7841, I "created a table with the same structure (and partitions), renamed the files to reflect the files in the dictionary, then dropped the old table again". Files are deleted from disk, but the information_schema.TokuDB_file_map table still shows the records. So I can't recreate the table with the same name. Please, can you suggest me a workaround to the problem? Is there a way to synchronize the file map with the real situation of existing files?