>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1477060. --> Reported by: [rfay](https://www.drupal.org/user/30906) >>> <p>I had to recover a database after the tmpfs full scenario today.</p> <p>Normally the instructions for recovery from this on the <a href="http://drupal.org/project/testbot">testbot project apge</a> are adequate (stop mysql; rm -rf /tmpfs/mysql/drupaltesbotmysql/simpletest*; restart mysql; drop database drupaltestbotmysql; create database drupaltestbotmysql). </p> <p>However, on occasion, this causes some kind of disaster, and mysql's system tables are out of date.</p> <p>You might get messages like</p> <pre>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: 120310&nbsp; 8:01:35&nbsp; InnoDB: Error: table 'drupaltestbotmysql/authmap'<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: in InnoDB data dictionary has tablespace id 355290538,<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: but tablespace with that id or name does not exist. Have<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: you deleted or moved .ibd files?<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: table still exists in the InnoDB internal data dictionary.</pre><p>and like </p> <pre>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: 120310&nbsp; 8:01:35&nbsp; InnoDB: Error: page 13618 log sequence number 21588276757294<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: is in the future! Current system log sequence number 21588276444999.<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: tablespace but not the InnoDB log files. See<br>Mar 10 08:01:35 drupaltestbot659-mysql mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html</pre><p>In this case, there's a pretty easy recovery without completely reinstalling mysql. Following the ideas in <a href="http://www.softwareprojects.com/resources/programming/t-how-to-fix-mysql-database-myisam-innodb-1634.html">http://www.softwareprojects.com/resources/programming/t-how-to-fix-mysql-database-myisam-innodb-1634.html</a>, I did this and it worked (finally)</p> <ol> <li>Stop mysql (service mysql stop). If ps -ef | grep mysql still shows running processes, <code>killall mysqld_safe; killall mysqld; killall -9 mysqld_safe; killall -9 mysqld</code></li> <li>Edit /etc/mysql/my.cnf to add<br> <pre>[mysqld]<br>innodb_force_recovery = 6</pre></li> <li>Restart mysql <code>service mysql start</code></li> <li>mysqldump drupaltestbot | gzip &gt;~/tmp/drupaltestbot.sql.gz </li> <li>Stop mysqld again as in the first step, but you may have to force it with killall again</li> <li>Remove or comment out the innodb_force_recovery line in my.cnf</li> <li> <pre>cd /tmpfs/mysql<br>rm -rf drupaltestbot*<br>rm ib_log* ibdata*</pre></li> <li>Start mysqld again (service mysql start) </li> <li><code>echo "create database drupaltestbot; create database drupaltestbotmysql;" | mysql</code></li> <li>gzip -dc ~/tmp/drupaltestbot.sql.gz | mysql drupaltestbot </li> </ol> <p>You may have a working testbot at this point. You'll want to reconfirm it.</p>