Michael Jay Lissnerhttps://michaeljaylissner.com/2010-04-26T11:26:38-07:00How to Recover a Broken Drupal Install Resulting from a Full Hard Drive2010-04-26T11:26:38-07:00Mike Lissnertag:michaeljaylissner.com,2010-04-26:posts/2010/04/26/recover-a-broken-drupal-install-from-full-hd/<p>This is amazingly, the second time I’ve filled my server’s hard drive, and the results are becoming predictable. One moment, things are working fine, the next, cron alerts you with something like this:</p>
<div class="highlight"><pre><span class="n">Table</span> <span class="p">[</span><span class="n">tablename</span><span class="p">]</span> <span class="n">is</span> <span class="n">marked</span> <span class="n">as</span> <span class="n">crashed</span> <span class="n">and</span> <span class="n">last</span> <span class="p">(</span><span class="n">automatic</span><span class="o">?</span><span class="p">)</span> <span class="n">repair</span> <span class="n">failed</span> <span class="n">query</span>
</pre></div>
<p>This is a bad warning to get, and running df on the server confirms that indeed my hard drive is full. Fixing this is a matter of doing some minor MySQL hacking to clean up all the tables:</p>
<div class="highlight"><pre>mysql -u<span class="s1">'drupalusername'</span> -p
> use drupal_DB_name;
> check table tablename;
> repair table tablename;
</pre></div>
<p>Then, simply iterate this for each broken table reported by cron.php, and you will soon have a repaired <span class="caps">DB</span>. Whew.</p>