Mads,

please post the WHOLE .err log. Or is there sensitive information there?

If you have taken backups and the .err log does not show any crashes in
them, how is it possible that the backups are now corrupt?

How did you take the backups? I assume that you did not simply copy the
ibdata files from a running server, which very probably creates corrupt
backups?

Best regards,

Heikki
Innobase Oy
http://www.innodb.com
InnoDB - transactions, foreign keys, and a hot backup tool for MySQL
Order MySQL support from http://www.mysql.com/support/index.html

...................

Subject: RE: InnoDB crash - recover + bug
From: Mads Jørgensen
Date: Thu, 7 Aug 2003 16:06:27 +0200



>> Greetings all.
>>
>> I have a bit of a problem here, a database i'm administering was somehow
=
>> corrupted, and i'm unable to recover it in any way.
>
>what happened? A power outage? You deleted the ib logfiles? Modified
my.cnf?
>Hard disk broke?

Thats the weird thing, nothing abnormal happened, i just saw the mysqld
using a lot
of resources and shut it down. I suppose it must have been a query, or the
database
beeing to large or something.

>What does uname -a say about the Linux kernel in Debian-unstable?

It says its running a 2.4.19 kernel, i686 on GNU/Linux

>> Is there any way at =
>> all to recover a corrupt InnoDB database? (I read on innodb.com that it =
>> is impossible, but hope it is not)
>
>You should always take backups of valuable data, and also keep the MySQL
>binlog so that you can replay the modifications after the backup.

So i understand, i'm used to running MyISAM tables, and have never had any
problems
with data corruption before now. Nothing a good myisamchk couldent fix
anyhow.

I do have a backup, just not old enough. I've been on vacation, so therefore
the data
got rotate out the system and overwritten. I only have corruptet backups.

>> When I run a query from any InnoDB table in the database MySQL crashes =
>> with the following stack trace and errors.=20
>
>Did you resolve the stack trace with the right mysqld.sym file? The trace
>below is nonsensical.

I think so, but i'll have to get back to you with that.

>What is the query?

What query? The one that triggers the segfault below is any SELECT, SHOW
TABLE STATUS
or what ever reads the files.

>What is the complete .err log?

I cannot find any entry in the error before i restartet the mysql process,
then it complained
the below.

> I'm running a GNU/Linux system and MySQL 4.0.13 from the Debian =
> unstable.
>


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to