# MysQL and InnoDB

**URL:** <https://forums.percona.com/t/mysql-and-innodb/1990>\
**Category:** Other MySQL® Questions\
**Created:** [February 13, 2013, 11:59am UTC](https://forums.percona.com/t/mysql-and-innodb/1990 "2013-02-13T11:59:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![silence](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/silence/32/909_2.png) [@silence](https://forums.percona.com/u/silence)\
**Post date:** [February 13, 2013, 11:59am UTC](https://forums.percona.com/t/mysql-and-innodb/1990/1 "2013-02-13T11:59:14Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![miguelangelnieto](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@miguelangelnieto](https://forums.percona.com/u/miguelangelnieto)\
**Post date:** [February 14, 2013, 2:39am UTC](https://forums.percona.com/t/mysql-and-innodb/1990/2 "2013-02-14T02:39:35Z")

</div>

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.