The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

InnoDB corruption failing recovery

Discussion in 'Database Discussions' started by aegis, May 17, 2012.

  1. aegis

    aegis Well-Known Member

    Joined:
    Jul 6, 2003
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Help!

    I had a RAID drive fail and the datacenter replaced the drive. However, now that's been done the server is up and running, the database won't start. InnoDB isn't recovering.

    I've tried setting innodb_force_recovery, first to 4, then 6.

    I get this error...

    Failed to locate MySQL socket. Please check the mysql configuration.
    -- Startup Output --
    Starting MySQL.................................... ERROR! Manager of pid-file quit without updating file.
    120518 01:49:37 mysqld started
    InnoDB: Log scan progressed past the checkpoint lsn 234 3217300651
    120518 1:49:38 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 234 3219402752
    120518 1:50:12 InnoDB: Error: page 7 log sequence number 234 3219549798
    InnoDB: is in the future! Current system log sequence number 234 3219402737.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: MySQL :: ::
    InnoDB: for more information.
    120518 1:50:12 InnoDB: Error: page 6 log sequence number 234 3219978305
    InnoDB: is in the future! Current system log sequence number 234 3219402737.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: MySQL :: ::
    InnoDB: for more information.
    InnoDB: Error: trying to access page number 1475812224 in space 0,
    InnoDB: space name /var/lib/mysql/ibdata1,
    InnoDB: which is outside the tablespace bounds.
    InnoDB: Byte offset 0, len 16384, i/o type 10.
    InnoDB: If you get this error at mysqld startup, please check that
    InnoDB: your my.cnf matches the ibdata files that you have in the
    InnoDB: MySQL server.
    120518 1:50:12InnoDB: Assertion failure in thread 47310678943696 in file fil0fil.c line 3959
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to MySQL Bugs.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: MySQL :: ::
    InnoDB: about forcing recovery.
    120518 1:50:12 - mysqld got signal 11 ;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    We will try our best to scrape up some info that will hopefully help diagnose
    the problem, but since we have already crashed, something is definitely wrong
    and this may fail.

    key_buffer_size=0
    read_buffer_size=2097152
    max_used_connections=0
    max_connections=400
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1638400 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd=(nil)
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    frame pointer is NULL, did you compile with
    -fomit-frame-pointer? Aborting backtrace!
    The manual page at MySQL :: MySQL 5.5 Reference Manual :: C.5.4.2 What to Do If MySQL Keeps Crashing contains
    information that should help you find out what is causing the crash.
    120518 01:50:12 mysqld ended

    -- End Startup Output --

    Any ideas at recovering from this ?
     
  2. ravibagul

    ravibagul Member

    Joined:
    Mar 16, 2006
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
  3. aegis

    aegis Well-Known Member

    Joined:
    Jul 6, 2003
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Tried that - no go. I've kept the corrupt data but after trying a number of things to recover it, it looks like it's toast.

    So, it's drop all the InnoDB tables and restore those from the backup which thankfully wasn't too long ago. 223 databases.
     
Loading...

Share This Page