MySQL error 7 (EE_LINK) signals the server could not rename a table or file because the underlying operating system returned a link or rename failure.
MySQL Error 7: EE_LINK occurs when the server cannot rename a table file and returns “Error on rename of 'old' to 'new' (OS errno …)”. Correct the underlying file-system issue—permissions, locks, path validity—then rerun the DDL statement to resolve the error.
Error on rename of '%s' to '%s' (OS errno %d - %s)
The message “Error on rename of '%s' to '%s' (OS errno %d - %s)” appears when MySQL requests the operating system to rename or link a table file and the call fails. The server maps that operating-system failure to internal error code 7, condition name EE_LINK.
The failure usually happens during ALTER TABLE RENAME, CREATE TABLE LIKE, DROP TABLE, or OPTIMIZE TABLE because these commands move .frm, .ibd, or .par files on disk.
Fixing the root cause at the file-system layer clears the error.
The error is raised immediately after MySQL issues a rename() or link() system call that returns a non-zero errno. MySQL stops the DDL statement, rolls back metadata changes, and returns error 7 to the client.
Subsequent statements that reference the same table may also fail until the underlying problem is solved.
Unresolved EE_LINK errors leave tables in an inconsistent state, block schema migrations, and stall deployments.
Ignoring the problem can cause dangling table files, orphaned metadata, and possible data loss if the mismatch is not corrected before the next backup or replication event.
Operating-system permissions, file locks, path length limits, and cross-device moves are the most common root causes. Hardware, antivirus software, and container volume mounts can also interfere with rename calls.
First capture the exact OS errno with SHOW WARNINGS or review the MySQL error log.
The errno maps directly to a descriptive string such as “Permission denied” or “Device or resource busy.” Address that issue, verify file ownership, and retry the DDL.
If multiple .ibd or .frm files exist for the same table, clean them up with the correct ALTER TABLE … DISCARD/IMPORT TABLESPACE workflow before renaming again.
Restarting MySQL or the host can release lingering locks.
Scenario 1 - errno 13 (Permission denied): Fix by chowning data files to the mysqld user and ensuring the directory is writable.
Scenario 2 - errno 18 (Cross-device link): Move the table to a directory on the same partition, or adjust datadir so all files live on a single volume.
Scenario 3 - errno 16 (Device or resource busy): Verify no other process, backup agent, or antivirus is holding an open handle.
Stop the process, or disable real-time scanning on the datadir.
Run MySQL with dedicated ownership of the datadir, keep data files on a single partition, and automate schema changes during low-traffic windows.
Continuous monitoring of the MySQL error log and OS audit logs can catch permission drifts early.
Galaxy’s AI copilot reviews DDL scripts in real time and alerts you to risky cross-device renames or missing privileges before execution, preventing most EE_LINK incidents in collaborative environments.
Error 1025 (Error on rename) is a higher-level MySQL error that often wraps EE_LINK. Error 6 (EE_WRITE) signals write failures, and Error 17 (ER_FILE_EXISTS) arises when the target file already exists.
Their remedies overlap—check permissions, paths, and locks.
.
No. Any command that moves table files, including OPTIMIZE TABLE and DROP TABLE, can trigger it.
Ignoring it risks metadata mismatch and future corruption. Fix immediately.
Production systems often have stricter permissions, backup locks, or multiple partitions, increasing the chance of EE_LINK.
Galaxy surfaces OS errno details inline, suggests permission fixes, and enforces peer review of DDL scripts to prevent unsafe renames.
.avif)
.avif){kind=logo}
