MySQL Forums
Forum List  »  InnoDB

Power outage db down - need help
Posted by: Bob Bankay
Date: February 23, 2005 07:17PM

We had a contractor cut the power lines to our building. The new Opteron server crashed badly but came up when power was restored.

mysqld would only come up with my.cnf containing
'innodb_force_recovery=6'
as was suggested in the server.err log when the first attempt failed.

It also contained dumps of corrupted pages and a mesage saying the double-buffer data was corrupted.

I was able to check and repair all the myisam tables. However, when I attempted anything with respect to medium to large innodb tables the mysql client would disconnect:

***************************************
Database changed
mysql> check table team;
ERROR 2013: Lost connection to MySQL server during query
*******************************************
However at the terminal session where I started mysqld the following messages appeared:

*******************************
[mysql@jocelyn ~]$ bin/mysqld_safe start
Starting mysqld daemon with databases from /mydisks/a/apps/mysql/data/

Number of processes running now: 0
050223 16:14:36 mysqld restarted

Number of processes running now: 0
050223 16:19:56 mysqld restarted

Number of processes running now: 0
050223 16:20:39 mysqld restarted

Number of processes running now: 0
050223 16:20:51 mysqld restarted

Number of processes running now: 0
050223 16:21:02 mysqld restarted
************************************

Each of these correspond to the 'server diconnected' msg.

Here is the corressponding server.err log entry
***********************************
050223 16:40:40InnoDB: Assertion failure in thread 1147926896 in file ../../innobase/include/buf0buf.ic line 286
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.
******************

Question: How can I verify which innodb tables are bad if I cannot check them because of the continous crashes/disconnects?

How can I do anything in
'innodb_force_recovery=6'
which is the most restricted level. If this is causing the server disconnects (while I am running from localhost) then what processes can I use?

Would setting recovery=4 make a difference?

BTW, a 'show table status' returns 0 rows for small Innodb tables and of course disconnects for the same query for large innodb tables. It fails for any status query that lasts longer than 1 sec.

Any all suggestions would be appreciated.

Bob

Options: ReplyQuote


Subject
Views
Written By
Posted
Power outage db down - need help
6261
February 23, 2005 07:17PM
2892
February 24, 2005 10:09AM
2854
February 24, 2005 11:26AM
2659
February 24, 2005 11:57AM
2660
February 24, 2005 07:09PM
3065
February 24, 2005 07:54PM
3342
February 25, 2005 03:30AM
2665
February 25, 2005 01:46PM


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.