MysQL and InnoDB

Hi,

I’m having some problems with corrupted tables in some databases.

The manual page at contains
information that should help you find out what is causing the crash.
130213 20:30:18 mysqld_safe Number of processes running now: 0
130213 20:30:18 mysqld_safe mysqld restarted
130213 20:30:18 [Warning] The syntax ‘–log-slow-queries’ is deprecated and will be removed in a future release. Please use ‘–slow-query-log’/’–slow-query-log-file’ instead.
130213 20:30:18 [Note] Plugin ‘FEDERATED’ is disabled.
130213 20:30:18 InnoDB: The InnoDB memory heap is disabled
130213 20:30:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130213 20:30:18 InnoDB: Compressed tables use zlib 1.2.3
130213 20:30:18 InnoDB: Using Linux native AIO
130213 20:30:18 InnoDB: Initializing buffer pool, size = 128.0M
130213 20:30:18 InnoDB: Completed initialization of buffer pool
130213 20:30:18 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 199920979264
130213 20:30:18 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: Doing recovery: scanned up to log sequence number 199920979274
130213 20:30:19 InnoDB: Waiting for the background threads to start
130213 20:30:20 InnoDB: 1.1.8 started; log sequence number 199920979274
130213 20:30:20 InnoDB: !!! innodb_force_recovery is set to 4 !!!
130213 20:30:20 [Note] Server hostname (bind-address): ‘0.0.0.0’; port: 3306
130213 20:30:20 [Note] - ‘0.0.0.0’ resolves to ‘0.0.0.0’;
130213 20:30:20 [Note] Server socket created on IP: ‘0.0.0.0’.
130213 20:30:20 [Note] /usr/sbin/mysqld: ready for connections.

I’ve set the recover to 4 and move everything to a VPS with the same MySQL version.

Can you help me out try to dump databases?

thanks.

If you have a corrupted table then you need to do a logical backup using mysqldump and avoid any binary backup like lvm snapshot or xtrabackup. So, just try to run the following:

mysqldump --all-databases > dump.sql

If it crash while reading some rows, ty to increase innodb_force_recovery to 6. Also, Do you use percona server?

Regards.