XAMPP / MySQL：无法打开单表表空间文件。\mysql\innodb_index_stats.ibd重新启动MySQL后 [英] XAMPP/MySQL: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd after restart of MySQL

问题描述

我在我的本地XAMPP服务器上安装了Drupal。它工作所有罚款，没有问题，包括和使用数据库/网站，直到我重新启动XAMPP。从那时起，我在我的日志文件中获得以下内容：

2013-09-02 16:18:46 2544 [Note]插件'FEDERATED'已禁用。

2013-09-02 16:18:46 3e8 InnoDB：警告：使用innodb_additional_mem_pool_size是DEPRECATED。此选项可能会在未来版本中与选项innodb_use_sys_malloc和InnoDB的内部内存分配器一起删除。

2013-09-02 16:18:46 2544 [Note ] InnoDB：禁用InnoDB内存堆

2013-09-02 16:18:46 2544 [注意] InnoDB：Mutexes和rw_locks使用Windows互锁函数

2013-09-02 16:18:46 2544 [注意] InnoDB：压缩表使用zlib 1.2.3

2013-09-02 16:18:46 2544 [注意] InnoDB：不使用CPU crc32指令

2013-09-02 16:18:46 2544 [注意] InnoDB：初始化缓冲池，大小= 16.0M

2013-09-02 16:18:46 2544 [注意] InnoDB：完成缓冲池的初始化

2013-09-02 16:18:46 2544 [注意] InnoDB：最高支持的文件格式是Barracuda。

2013 -09-02 16:18:47 2544 [注意] InnoDB：ibdata文件中的日志序列号1600614和1600614与ib_logfiles！中的日志序列号1600644不匹配。

2013-09-02 16:18:47 2544 [注意] InnoDB：数据库没有正常关闭！

2013-09-02 16:18:47 2544 [注意] InnoDB：开始崩溃恢复。

2013-09-02 16:18:47 2544 [注意] InnoDB：从.ibd文件读取表空间信息。 。

2013-09-02 16:18:47 2544 [错误] InnoDB：尝试打开以前打开的表空间。上一个表空间drupal /变量使用空间ID：2在filepath：.\drupal\variable.ibd。无法打开在文件路径使用空间ID：2的表空间mysql / innodb_index_stats：.\mysql\innodb_index_stats.ibd

InnoDB：错误：无法打开单表表空间文件.\mysql\innodb_index_stats.ibd

InnoDB：我们不会继续崩溃恢复，因为表可能会变成

InnoDB：如果我们无法将InnoDB日志中的日志记录应用到InnoDB，则会损坏。

InnoDB：解决问题并启动mysqld：

InnoDB：1）如果文件中存在权限问题，mysqld无法

InnoDB：打开文件应修改权限。

InnoDB：2）如果不需要该表，或者您可以从备份还原，则

InnoDB：然后你可以删除.ibd文件，InnoDB将执行一个正常的

InnoDB：崩溃恢复并忽略该表。

InnoDB：3）如果文件系统或磁盘损坏，并且您无法删除

InnoDB：.ibd文件，您可以在my.cnf

InnoDB中设置innodb_force_recovery> 0，并强制InnoDB在这里继续崩溃恢复。

我通过google寻找一个解决方案，但它似乎是一个问题只是与drupal数据库，因为它能够连接MySQL，如果我删除数据库。

我希望有人能帮助我：（。

解决方案

dev_khan，

1. 使用此行重新启动MySQL服务在Config-文件使
   MySQL引擎修复本身。


2. 完成后，您必须删除innodb_force_recovery-Command
   或在命令前使用＃取消注释。

来自德国的问候

重新启动MySql， >

I've installed Drupal on my local XAMPP Server. It worked all fine, no problems with including and working with the database/site till i restarted XAMPP. Since then I get the following at my logfile:

2013-09-02 16:18:46 2544 [Note] Plugin 'FEDERATED' is disabled.

2013-09-02 16:18:46 3e8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.

2013-09-02 16:18:46 2544 [Note] InnoDB: The InnoDB memory heap is disabled

2013-09-02 16:18:46 2544 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2013-09-02 16:18:46 2544 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-09-02 16:18:46 2544 [Note] InnoDB: Not using CPU crc32 instructions

2013-09-02 16:18:46 2544 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2013-09-02 16:18:46 2544 [Note] InnoDB: Completed initialization of buffer pool

2013-09-02 16:18:46 2544 [Note] InnoDB: Highest supported file format is Barracuda.

2013-09-02 16:18:47 2544 [Note] InnoDB: The log sequence numbers 1600614 and 1600614 in ibdata files do not match the log sequence number 1600644 in the ib_logfiles!

2013-09-02 16:18:47 2544 [Note] InnoDB: Database was not shutdown normally!

2013-09-02 16:18:47 2544 [Note] InnoDB: Starting crash recovery.

2013-09-02 16:18:47 2544 [Note] InnoDB: Reading tablespace information from the .ibd files...

2013-09-02 16:18:47 2544 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace drupal/variable uses space ID: 2 at filepath: .\drupal\variable.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd

InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.

I looked for a solution via google but it seems to be a problem just with the drupal database because it's able to connect with MySQL if I remove the database.

I hope someone could help me :(.

解决方案

dev_khan, you have a Read-Only permission as long as "innodb_force_recovery" is enabled in your configuration file.

1. Restart the MySQL Service with this Line in the Config-File to make the MySQL engine repairing itself.
2. After it is done you have to drop the innodb_force_recovery-Command or outcomment it with a "#" before the Command.
3. Restart MySql again and you have full Access again without a Read-Only-Restriction.

Greetings from Germany

这篇关于XAMPP / MySQL：无法打开单表表空间文件。\mysql\innodb_index_stats.ibd重新启动MySQL后的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！