From: Suporte Avanutri
Date: January 26 2012 5:04pm
Subject: RES: RES: RES: Force drop table
List-Archive: http://lists.mysql.com/mysql/226675
Message-Id: <003101ccdc4c$86b473a0$941d5ae0$@avanutri.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Mysqld crashes when I try to dump everything at once. I made a test by =
extracting information from only one table, and it worked. I will try =
yet with another tables. But I guess that is it... Thanks a lot, people. =
You were great. =3D)

-----Mensagem original-----
De: Johan De Meersman [mailto:vegivamp@stripped]=20
Enviada em: quinta-feira, 26 de janeiro de 2012 14:53
Para: Todd Lyons
Cc: MySQL Help; Suporte Avanutri
Assunto: Re: RES: RES: Force drop table


----- Original Message -----
> From: "Todd Lyons" <tlyons@stripped>
>=20
> It doesn't matter what you set in innodb_force_recovery.  If you do=20
> not have the obras.frm file (which contains the schema definition of=20
> the table), I don't know if you can retrieve the info.  Put that file

I recommended he delete that file since he was trying to delete the =
table anyway, and the log said there was no metadata for that table.

Mateus, I see in the last bit of logs that the recovery sequence number =
remains constant. Does the server still crash at that point even though =
there are no more error messages? What happens if you remove the =
innodb_force_recovery setting?

If it keeps crashing without errors, you may be up shit creek :-) You =
can try running it through strace, but the output of that is going to be =
long and confusing. If you can't just do a clean install and restore =
from backups, a good consultant might be your best bet at this point.


--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel