No input on this one?
-Original Message-
From: Bryan Cantwell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 11:51 AM
To: mysql@lists.mysql.com
Subject: Crashed InnoDB
We had a power outage, now the mysql wont start at all. Here is the err file
output... Any help on how
:
No input on this one?
-Original Message-
From: Bryan Cantwell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 11:51 AM
To: mysql@lists.mysql.com
Subject: Crashed InnoDB
We had a power outage, now the mysql wont start at all. Here is the err file
output... Any help on how
distribution on how to do that.
Number of processes running now: 0
From: Dan Rogart [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 12:27 PM
To: Bryan Cantwell; mysql list
Subject: Re: Crashed InnoDB
Have you tried starting mysqld with innodb_force_recovery = x ? (where
, 2008 12:27 PM
To: Bryan Cantwell; mysql list
Subject: Re: Crashed InnoDB
Have you tried starting mysqld with innodb_force_recovery = x ? (where x =
values defined below)
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
That might get you past the corruption that's killing
We had a power outage, now the mysql wont start at all. Here is the err file
output... Any help on how to recover?
080212 11:35:50 mysqld started
080212 11:35:50 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd
Hi,
MySQL 4.0.16 running on Red Hat Linux release 8.0
with 4 Intel XEON 2.40 GHz with InnoDB tables.
This is the stack trace :
0x81077c6 handle_segfault + 474
0x4002a929 _end + 935891041
0x8272ff8 sync_array_print_long_waits + 580
0x81a7328 srv_error_monitor_thread + 96
0x40024ada _end +
