List:General Discussion« Previous MessageNext Message »
From:Suresh Kuna Date:October 12 2010 4:00pm
Subject:Re: InnoDB Crash
View as plain text  
Hey Willy - Install the new binaries and start mysql with new binary as
basedir and see whether innodb has enabled or not. Check the error log why
the innodb is getting disabled, make a copy of it here too.

On Tue, Oct 12, 2010 at 2:57 PM, Willy Mularto <sangprabv@stripped> wrote:

> Hi List,
> Last night accidentally one of my InnoDB table crash. And cause client can
> not connect to MySQL, it always said cannot connect to socket, even the
> daemon is launched. I tried to set innodb_force_recovery from 0 to 6 and
> only number 3 bring back the connection. After that I dump the data and drop
> the table. I recreate it as MyISAM and inject the dumped data. After that I
> stop MySQL and remove innodb_force_recovery and restart. And clients start
> complaining can not connect. Then I enable innodb_force_recovery again. I
> tried to create a new InnoDB table test and MySQL complaint cannot create
> the table due to the engine type is not supported. The question is how to
> solve this problem? How to bring back InnoDB to my server without reinstall
> the OS or MySQL itself? I have also tried to drop the database and remove
> the data folder from mysql data dir and recreate the database but still no
> luck. Thanks for any help.
> sangprabv
> sangprabv@stripped
> --
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

Suresh Kuna

InnoDB CrashWilly Mularto12 Oct
  • Re: InnoDB CrashSuresh Kuna12 Oct
    • Re: InnoDB CrashWilly Mularto13 Oct