mysqldump: Got error: 130: Incorrect file format

Bashy

Well-Known Member
Feb 20, 2011
67
3
58
Well, that dint go down too well


Code:
The metadata database is corrupt. Scheduling a rebuild.
[2018-02-28 02:05:29 +0000] brecklan_alldata: mysqldump: Got error: 130: Incorrect file format 'alldata' when using LOCK TABLES
warn [pkgacct] ********_alldata: mysqldump: Got error: 130: Incorrect file format 'alldata' when using LOCK TABLES
I should mention that that database is now a big fat 0mb and my weather site no longer has any data that was acquired over the last year'ish, 107mb worth..............
 
Last edited:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,203
363
Hello @Bashy,

I moved this post to it's own separate thread, as the mysqldump error message doesn't appear related to the metadata rebuild. Here's the error message in-question:

[2018-02-28 02:05:29 +0000] brecklan_alldata: mysqldump: Got error: 130: Incorrect file format 'alldata' when using LOCK TABLES
warn [pkgacct] ********_alldata: mysqldump: Got error: 130: Incorrect file format 'alldata' when using LOCK TABLES
To clarify, are you saying the database referenced in the backup log is now at 0MB after the backup process? That shouldn't happen, as the backup attempt should only attempt to copy the MySQL database as opposed to it modifying the database itself.

Instead, the error message suggests one of the tables in that database is corrupt. MySQL documents how to repair tables at:

MySQL :: MySQL 5.7 Reference Manual :: 2.11.3 Rebuilding or Repairing Tables or Indexes

Thank you.