为了能快速了解并处理您的问题,请提供以下基础信息:
问题描述:mysqld无法启动
相关截图(日志、错误): Barracuda. 2023-05-15 22:25:48 15263 [Note] InnoDB: Log scan progressed past the checkpoint lsn 10125035617 2023-05-15 22:25:48 15263 [Note] InnoDB: Database was not shutdown normally! 2023-05-15 22:25:48 15263 [Note] InnoDB: Starting crash recovery. 2023-05-15 22:25:48 15263 [Note] InnoDB: Reading tablespace information from the .ibd files... 2023-05-15 22:25:48 15263 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace www_007xbw_com/wp_ocw_contact_content uses space ID: 10 at filepath: ./www_007xbw_com/wp_ocw_contact_content.ibd. Cannot open tablespace www_guziyuanw_co/wp_cao_ref_log which uses space ID: 10 at filepath: ./www_guziyuanw_co/wp_cao_ref_log.ibd 2023-05-15 22:25:48 2b5b1a658cc0 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 ./www_guziyuanw_co/wp_cao_ref_log.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.
|
|