Hi
A client of ours has experienced some rather serious hardware failures
resulting in disk errors and therefore corrupted InnoDB files.
We could not get mysql to restart unless the innodb_force_recovery was set to
5. In this situation we encountered failure when attempting to read from
On May 25, 2005, at 9:34 AM, David Brewster wrote:
A client of ours has experienced some rather serious hardware
failures resulting in disk errors and therefore corrupted InnoDB
files.
We could not get mysql to restart unless the innodb_force_recovery
was set to 5. In this situation we
information that should help you find out what is causing the crash.
Number of processes running now: 0
-Original Message-
From: Ware Adams [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 15:58
To: David Brewster
Cc: mysql@lists.mysql.com
Subject: Re: Restoring InnoDB databases from backups causing
On May 25, 2005, at 10:06 AM, David Brewster wrote:
Here is the log dump :-
Thanks
David
050525 13:24:10 InnoDB: Started
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.15-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306
050525 13:24:11 InnoDB: Assertion failure in thread
-
From: Ware Adams [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 17:31
To: David Brewster
Cc: mysql@lists.mysql.com
Subject: Re: Restoring InnoDB databases from backups causing problems
On May 25, 2005, at 10:06 AM, David Brewster wrote:
Here is the log dump :-
Thanks
David
050525 13:24:10
