MySQL startet nach Crash nicht mehr mit InnoDB

nasenmann
Posts: 13
Joined: 2006-02-19 23:52

MySQL startet nach Crash nicht mehr mit InnoDB

Post by nasenmann »

Gestern ist mein Server mit MySQL 5.0.27 abgestürzt und nach einem reboot startet nun der MySQL Daemon nicht mehr. Auf dem Server läuft eine große InnoDB Datenbank. Folgendes steht im MySQL Log:

Code: Select all

070618 20:56:52  mysqld started
070618 20:56:52  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...
070618 20:56:53  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 18 733632564.
070618 20:56:53  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 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 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=2093056
max_used_connections=0
max_connections=300
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1227597 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=0xb4be53f8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8178043
0x83fc16a
0x83fce24
0x83c16a6
0x83c36f6
0x83b1309
0x83dc1eb
0x8322b38
0xbb2433
0xa88a1e
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
Mit skip_innodb startet er durch. Ich habe ihn schon versucht mit allen innodb_force_recovery Parametern wenigstens zum starten zu überreden, allerdings hatte ich keinen Erfolg. Hat noch jemand eine Idee?

Grüße
Top

rpq
Posts: 15
Joined: 2004-05-25 09:02
Location: Lübeck

Re: MySQL startet nach Crash nicht mehr mit InnoDB

Post by rpq »

Hast Du eine Lösung gefunden?
Oder steht der Dienst noch?
Top