Results 1 to 7 of 7

Thread: [SOLVED] problem with innodb corruption

  1. #1
    Insanity5902 is offline Intermediate Member
    Join Date
    Dec 2007
    Posts
    20
    Rep Power
    7

    Default [SOLVED] problem with innodb corruption

    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.
    Attached Files Attached Files

  2. #2
    Insanity5902 is offline Intermediate Member
    Join Date
    Dec 2007
    Posts
    20
    Rep Power
    7

    Default

    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.

  3. #3
    randall is offline Advanced Member
    Join Date
    Jun 2007
    Location
    Philippines
    Posts
    193
    Rep Power
    8

    Default

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

  4. #4
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

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

    Try this:
    Mysql Crash Recovery - Zimbra :: Wiki

  5. #5
    Insanity5902 is offline Intermediate Member
    Join Date
    Dec 2007
    Posts
    20
    Rep Power
    7

    Default

    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.

  6. #6
    Insanity5902 is offline Intermediate Member
    Join Date
    Dec 2007
    Posts
    20
    Rep Power
    7

    Default

    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

  7. #7
    Insanity5902 is offline Intermediate Member
    Join Date
    Dec 2007
    Posts
    20
    Rep Power
    7

    Default

    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
    Last edited by Insanity5902; 01-10-2009 at 09:38 PM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. MySQL error, seems to be one specific mailbox
    By staufj22 in forum Administrators
    Replies: 8
    Last Post: 03-03-2008, 04:37 PM
  2. Replies: 7
    Last Post: 02-27-2008, 05:17 PM
  3. Replies: 11
    Last Post: 06-22-2007, 01:32 PM
  4. Upgrade 4.5.1 -> 4.5.2 Network Edition on RH Failed
    By CJ.deb in forum Installation
    Replies: 7
    Last Post: 03-01-2007, 07:05 AM
  5. Replies: 2
    Last Post: 10-02-2006, 08:44 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •