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

Discussion in 'Database Discussions' started by TND, Aug 2, 2016.

Tags:
  1. TND

    TND Member

    Joined:
    Jul 9, 2012
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    DataCenter Provider
    Dear cPanel,

    Thank you for your respon, i was upgrade to 10.0.25-MariaDB and using Percona-XtraDB.

    Today my server has been shut down abruptly because electric power is off.

    when server is starting, my Mysql can't start

    in .err file. I got some error like this.

    160802 9:42:32 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace xxx_xxx/news uses space ID: 167 at filepath: ./xxx_xxx/news.ibd. Cannot open tablespace xxx_xxx/product_features_sets which uses space ID: 167 at filepath: ./xxx_xxx/product_features_sets.ibd
    2016-08-02 09:42:32 7f24ba4a17e0 InnoDB: Operating system error number 2 in a file operation.
    InnoDB: The error means the system cannot find the path specified.
    InnoDB: If you are installing InnoDB, remember that you must create
    InnoDB: directories yourself, InnoDB does not create them.
    InnoDB: Error: could not open single-table tablespace file ./xxx_xxx/product_features_sets.ibd
    InnoDB: We do not continue the crash recovery, because the table may become
    InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
    InnoDB: To fix the problem and start mysqld:
    InnoDB: 1) If there is a permission problem in the file and mysqld cannot
    InnoDB: open the file, you should modify the permissions.
    InnoDB: 2) If the table is not needed, or you can restore it from a backup,
    InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
    InnoDB: crash recovery and ignore that table.
    InnoDB: 3) If the file system or the disk is broken, and you cannot remove
    InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
    InnoDB: and force InnoDB to continue crash recovery here.

    My mysql can't start with innodb_force_recovery, i was delete ib* file for starting mysql service.
    all InnoDB database is losing and then i was recovery that database from the backup.


    Do you have any idea to fix this in future?

    Thank you
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,807
    Likes Received:
    667
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  3. TND

    TND Member

    Joined:
    Jul 9, 2012
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    DataCenter Provider
    Hi,

    I had previously read this article, my question is how to stop InnoDB Corruption in future.

    Thank you :(
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,807
    Likes Received:
    667
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page