List:General Discussion« Previous MessageNext Message »
From:Eric Bergen Date:September 21 2006 3:33pm
Subject:Re: InnoDB Crash RECOVERY HELP (Urgent)
View as plain text  
The error message says to go to
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html to learn
how to set the different recovery options for innodb.

On 9/21/06, Sayed Hadi Rastgou Haghi <hadi.rastgou@stripped> wrote:
> Dear all,
> our DB server crashed and when I try to start Mysql
> /etc/init.d/mysql/start
> I get these lins in my error log
>
> 060921 13:00:14  mysqld started
> 060921 13:00:14  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...
> 060921 13:00:14  InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 3 3546172175.
> InnoDB: Error: tried to read 65536 bytes at offset 0 2173440.
> InnoDB: Was only able to read 54784.
> InnoDB: Fatal error: cannot read from file. OS error number 17.
> 060921 13:01:24InnoDB: Assertion failure in thread 3086943936 in file
> os0file.c line 2107
> InnoDB: We intentionally generate a memory trap.
> InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
> InnoDB: If you get repeated assertion failures or crashes, even
> InnoDB: immediately after the mysqld startup, there may be
> InnoDB: corruption in the InnoDB tablespace. Please refer to
> InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
> InnoDB: about forcing recovery.
> mysqld got signal 11;
> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly built,
> or misconfigured. This error can also be caused by malfunctioning hardware.
> We will try our best to scrape up some info that will hopefully help
> diagnose
> the problem, but since we have already crashed, something is definitely
> wrong
> and this may fail.
>
> key_buffer_size=0
> read_buffer_size=536866816
> max_used_connections=0
> max_connections=550
> threads_connected=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
> 2094947 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> thd=(nil)
> Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> Cannot determine thread, fp=0xbffe3d4c, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x814cbfb
> 0x8d28b8
> 0x10000
> 0x8355aed
> 0x835c659
> 0x835ce73
> 0x829ba01
> 0x81d3af3
> 0x81c5cb2
> 0x815028a
> 0x773e33
> 0x80e0c71
> New value of fp=(nil) failed sanity check, terminating stack trace!
> Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and
> follow instructions on how to resolve the stack trace. Resolved
> stack trace is much more helpful in diagnosing the problem, so please do
> resolve it
> The manual page at http://www.mysql.com/doc/en/Crashing.html contains
> information that should help you find out what is causing the crash.
> 060921 13:01:24  mysqld ended
>
> when I add skip-innodb in my.cnf, it startsup but my innodb tables could not
> be accessed.
>
> How can I start MySQL server again?
>
> --
> Sincerely,
> Hadi Rastgou
> A Google Account is the key that unlocks the world of Google.
> <a href= "http://www.spreadfirefox.com/?q=affiliates&amp;id=0&amp;t=1">
> Get
> Firefox! </a>
>
>


-- 
Eric Bergen
eric.bergen@stripped
http://www.provenscaling.com
Thread
InnoDB Crash RECOVERY HELP (Urgent)Sayed Hadi Rastgou Haghi21 Sep
  • Re: InnoDB Crash RECOVERY HELP (Urgent)Eric Bergen21 Sep