Results 1 to 10 of 12

Thread: raw_logs mysql table corruption - how to recover?

Hybrid View

  1. #1
    Join Date
    Mar 2007
    Posts
    33
    Rep Power
    8

    Default raw_logs mysql table corruption - how to recover?

    Hello all,

    Recently, I noticed I was having issues with the Zimbra logger. As a result, I found this wiki page.

    So I issued a REPAIR TABLE statement, and after 5+ hours wait, I decided to investigate, and found I'd run into the exact same issue as outlined in this MySQL bug report. My du/df returns exactly the same results as outlined in that bug (an empty and yet full /tmp/ directory)

    Doing a tail servername.com.err returns several lines similar to the below..
    Code:
    071219 15:56:04 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Disk is full writing '/tmp/STYAnvMQ' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
    Any thoughts? Right now, I'm EXTREMELY loath to abort the "REPAIR TABLE" process, yet I am pretty sure it's stuck...

    TIA!

  2. #2
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Are you out of space in /tmp?

  3. #3
    Join Date
    Mar 2007
    Posts
    33
    Rep Power
    8

    Default

    Quote Originally Posted by jholder View Post
    Are you out of space in /tmp?
    No.

    Code:
    # df
    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/sda1             51625340   2993668  46010232   7% /
    none                   1046016         0   1046016   0% /dev/shm
    /dev/sda3             51614140  25925372  23067328  53% /opt
    /dev/sda4              2015824   2004140         0 100% /tmp
    # du -s /tmp
    52      /tmp

  4. #4
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Look closer.

    Yes you are.

  5. #5
    Join Date
    Mar 2007
    Posts
    33
    Rep Power
    8

    Default

    Quote Originally Posted by jholder View Post
    Look closer.

    Yes you are.
    So how come du -s (at the bottom of my paste in my previous post) reports only 52K used up?

    In any case, if I AM out of space, how should I progress? Kill "REPAIR TABLE"?

  6. #6
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Not sure on the -s switch. Man indicates:
    "-s Display an entry for each specified file. (Equivalent to -d 0)"

    /tmp isn't a file, it's a directory. It's possible that i'm wrong on that (actually it's likely), but your df clearly indicates that /tmp is 100% full.

    Can you free up space in /tmp? If you do, it should redo the operation, fixing it.

Similar Threads

  1. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 01:42 AM
  2. Replies: 7
    Last Post: 10-05-2007, 04:14 PM
  3. Replies: 18
    Last Post: 03-20-2006, 02:22 PM
  4. Installation on FC3 under Xen
    By andreground in forum Installation
    Replies: 9
    Last Post: 11-14-2005, 10:29 AM
  5. Can't start MySQL to init db - Gentoo
    By fak3r in forum Installation
    Replies: 3
    Last Post: 10-10-2005, 07:59 PM

Posting Permissions

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