List:General Discussion« Previous MessageNext Message »
From:Todd Lyons Date:January 25 2012 2:45pm
Subject:Re: RES: Force drop table
View as plain text  
On Wed, Jan 25, 2012 at 6:42 AM, Todd Lyons <tlyons@stripped> wrote:

> For example, I shut down my mysql daemon, I make a copy of my
> corrupted database at /var/lib/mysql/ into /var/lib/mysql_tmp/, and
> then manually start the mysql daemon in the foreground with this:
> su - mysql -c '/usr/libexec/mysqld --innodb_force_recovery=6 --datadir
> /var/lib/mysql_tmp/'

I forgot to mention that when you do this, there will be copious
amounts of debug output that are spit out and it will give really ugly
warnings about tables that it finds but metadata doesn't match up.
But usually it can get the data out, though if you're not processing
any undo/redo logs, there's a chance that the most recent data written
to the table will not be retrievable.

Regards...              Todd
-- 
SOPA: Any attempt to [use legal means to] reverse technological
advances is doomed.  --Leo Leporte
Thread
Force drop tableSuporte Avanutri24 Jan
  • RE: Force drop tableShafi AHMED24 Jan
  • RES: Force drop tableSuporte Avanutri24 Jan
    • Re: RES: Force drop tableJohan De Meersman24 Jan
      • RES: RES: Force drop tableSuporte Avanutri24 Jan
        • Re: RES: Force drop tableSuresh Kuna25 Jan
          • RES: RES: Force drop tableSuporte Avanutri25 Jan
            • Re: RES: RES: Force drop tableJohan De Meersman25 Jan
              • RES: RES: RES: Force drop tableSuporte Avanutri26 Jan
                • Re: RES: RES: Force drop tableTodd Lyons26 Jan
                  • Re: RES: RES: Force drop tableJohan De Meersman26 Jan
                    • RES: RES: RES: Force drop tableSuporte Avanutri26 Jan
        • Re: RES: Force drop tableTodd Lyons25 Jan
          • Re: RES: Force drop tableTodd Lyons25 Jan