Re: What could cause .frm and .ibd mismatches across multiple tables?

[Herrick Peterson]

Hello

This kind of .frm and .ibd mismatch usually suggests that something happened outside of a normal MySQL operation, such as an unexpected crash, storage/filesystem issue, manual file changes, or an incomplete restore/migration.

Since the issue was already present in the backup, a successful mysqldump alone may not be enough to detect missing or orphaned tables. I would recommend regularly checking the database and filesystem for inconsistencies, and keeping more than one generation of backups.

For deeper investigation, especially to identify exactly what caused multiple tables to become inconsistent, some advanced MySQL/InnoDB troubleshooting may be required. I would need to invest more time in learning the deeper InnoDB internals to provide a definitive root cause.

Herrick
DevOps Engineer
Accuweb.cloud