So I did a
mysqldump of a pretty huge db and I'm trying to restore it now using:
mysql db_test < db_test.sql
but it looks like it's not gonna end by the end of this year. It's been about an hour now and still "restoring". Making the backup took about 10 minutes so I'm afraid something bad is going on.
- I've checked that
mysqldis consuming my cpu (up to 80% sometimes).
- There's nothing relevant to it in the logs.
I can see the database created and filled with a ton of tables (not everything tho). Also, when I execute
use db_test;, I get the following message:
Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A
- Original db files where around 25GB, after the whole hour,
df -hreturns the same free space as before. So I guess it's not doing anything on disk.
Something weird here is that, when checking
top, I found out that
kworker was consuming up to 100% of cpu sometimes, which shouldn't be happenning
Any idea or anything I could do to see what's going on?