[SOLVED] problem with innodb corruption

[Insanity5902]

after trying to migrate to 5.0.4 and now 5.0.5, I am having the same issues. That latest version I've tried migrating to is Release 5.0.5_GA_2201.UBUNTU6 UBUNTU6 FOSS edition.

Attached is my hostname.err that was cleaned out before a couple of attempts are repair, I have tried setting innodb force recovery to 1 and 4 and mysql won't stay up log enough to do anything with.

I've already restored my backup of 5.0.2, which runs without problems.

Also during the install/upgrade I run the DB integerity upgrade. During the install the only errors start with trying to migrate the wiki documents which fail b/c it can't connect to the database.

I've deleted the Hex out of the file.

Any Ideas?

EDIT :: I did backup the dir of the bad install of 5.0.5 so I can get files out of it.

[Insanity5902]

anybody have an idea? I've seen similar things, but most people are able to keep the mysql up long enought ot dump the DB and reload them.

[randall]

Did you try to login directly to mySQL and repair the DB manually?

[jholder]

INNODB can be very difficult to repair. It's best to just dump it and reimport it.

Try this:
Mysql Crash Recovery - Zimbra :: Wiki

[Insanity5902]

I haven't seen this, I will give this a shot over the weekend. I've tried something similar by setting innodb_force_recovery to 1 or 4, but not three.

Thanks.

[Insanity5902]

Sorry for the delay in follow up, but with the 5.0.6 and the wiki post by jholder, things are fixed now.

I accidently usedd the recovery option 4, isntead of 3, but things worked the same. All is well and I am not running 5.0.6

[Insanity5902]

After running the server 30 minutes the innodb corruptions came back

Edit : 1/10/2009 Problem fixed in 5.0.11, posting more info in http://www.zimbra.com/forums/migrati...orruption.html