MySQL Forums
Forum List  »  Data Recovery

Posted by: Ido Katz
Date: October 04, 2010 09:20AM

Hello Guys,

My name is Ido Katz and I didn't know where excatly should I go so I'm trying here.

I have a little problem.

When i'm trying to start the mysqld service it failed time and time again.
I'm getting this in the log file:

mysqld started
InnoDB: Log scan progressed past the checkpoint lsn 22 3513937721
101004 17:32:56 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...
InnoDB: Doing recovery: scanned up to log sequence number 22 3514013682
101004 17:32:56 InnoDB: Error: page 1589273 log sequence number 22 3514035878
InnoDB: is in the future! Current system log sequence number 22 3514013682.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: for more information.
101004 17:32:56 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 101004 17:32:56 - 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 5242880 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at contains
information that should help you find out what is causing the crash.
42 43 44 45 101004 17:32:56 mysqld ended

Do you have any suggetions?

Thanks in advance,
Ido Katz

Options: ReplyQuote

Written By
October 04, 2010 09:20AM
October 04, 2010 10:16AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.