Bug #76603 InnoDB asserts for DROP TABLESPACE ib_logfile0
Submitted: 7 Apr 2015 3:57 Modified: 13 Apr 2015 19:16
Reporter: Marko Mäkelä Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7.6 OS:Any
Assigned to: CPU Architecture:Any

[7 Apr 2015 3:57] Marko Mäkelä
The CREATE TABLESPACE functionality failed to move InnoDB redo log files to the reserved name space that starts with the innodb_ prefix. Thus, the tablespace name ib_logfile0 is incorrectly reserved for internal use.

How to repeat:
create tablespace ib_logfile0 ADD DATAFILE 'foo.ibd';
drop tablespace ib_logfile0;

Suggested fix:
In fil_system_t::name_hash and fil_space_t::name, use a different name for the redo log entry, such as innodb_redo_log.
[13 Apr 2015 19:16] Daniel Price
Posted by developer:
Fixed as of the upcoming 5.7.8, 5.8.0 releases, and here's the changelog entry:

"CREATE TABLESPACE" failed to move internal tablespace files to a
reserved name space that starts with an "innodb_" prefix, permitting
internal tablespace files to be dropped.