[ERROR] InnoDB: Attempted to open a previously opened tablespace

短命女 2023-06-09 15:21 15阅读 0赞

启动时遇到以下报错：  
`[ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace xxx/xxxx uses space ID: 4 at filepath: ./xxx/xxxx.ibd. Cannot open tablespace mysql/gtid_slave_pos which uses space ID: 4 at filepath: ./mysql/gtid_slave_pos.ibd`  
后面还有一段说明：

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 ./mysql/gtid_slave_pos.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.

大概意思就是mysql/gtid\_slave\_pos这个表损坏了，无法应用redo日志来进行实例恢复。  
那么只能设置innodb\_force\_recovery=1来跳过实例启动时检查表损坏情况。  
启动时就有以下提示：  
`[Note] InnoDB: innodb_force_recovery was set to 1. Continuing crash recovery even though we cannot access the .ibd file of this table.`  
实例可以正常启动，但是mysql.gtid\_slave\_pos并没有修复。后续需要将数据逻辑导出迁移到一个正常的实例上。

顺便学习一下innodb\_force\_recovery，顾名思义就是强制innodb的实例恢复，可以取值1-6：  
1(SRV\_FORCE\_IGNORE\_CORRUPT)：实例恢复时忽略检测到的页损坏、表损坏等；  
2(SRV\_FORCE\_NO\_BACKGROUND)：实例恢复时不运行master thread和purge thread；  
3(SRV\_FORCE\_NO\_TRX\_UNDO)：实例恢复后不运行undo回滚；  
4(SRV\_FORCE\_NO\_IBUF\_MERGE)：实例恢复时不进行insert buffer的合并操作，这个级别会对数据文件造成永久的损坏，启动后应该重建所有二级索引。  
5(SRV\_FORCE\_NO\_UNDO\_LOG\_SCAN)：实例恢复时对于未完成的事务不进行回滚。  
6(SRV\_FORCE\_NO\_LOG\_REDO)：实例恢复时不应用redo