InnoDB“腐败”

Question

我用：

• 5.1.63-0ubuntu0.11.10.1
• Apache/2.2.20 (Ubuntu)
• MySQL客户端版本：5.1.63

在从MySQL数据库读取数据时，系统不断显示以下错误：

InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 387794.

重新启动系统后，我可以重新访问数据库并读取“有问题”的数据几分钟或几小时没有任何问题，直到再次出现相同的问题（针对不同的数据读取尝试）。

关于问题根源的任何想法？

1. 我已经使用 SMART 实用程序检查了硬盘，但没有发现任何问题。
2. 我停用AppArmor没有任何结果。
3. 我还尝试SQL_NO_CACHE了查询中的选项，但没有任何结果

120918 13:07:06  InnoDB: Page checksum 3504102879, prior-to-4.0.14-form checksum 1216630776
InnoDB: stored checksum 2100325079, prior-to-4.0.14-form stored checksum 1216630776
InnoDB: Page lsn 2 1168743501, low 4 bytes of lsn at page end 1168743501
InnoDB: Page number (if stored to page already) 387794,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 0 175
InnoDB: (index "PRIMARY" of table "OII"."dataset_cs_1")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 387794.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
120918 13:07:07 [Note] Plugin 'FEDERATED' is disabled.
120918 13:07:07  InnoDB: Initializing buffer pool, size = 64.0M
120918 13:07:07  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 2 2380293142
120918 13:07:07  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 2 2380293162
120918 13:07:07  InnoDB: Started; log sequence number 2 2380293162
120918 13:07:07 [Note] Event Scheduler: Loaded 0 events
120918 13:07:07 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.63-0ubuntu0.11.10.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)

Answer 1

重新启动可以暂时解决问题，并且错误会四处移动......这强烈表明系统 RAM 有缺陷，导致操作系统缓存损坏。

InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.

您可能已经知道这一部分，但在 Ubuntu 中，启动时选择“内存测试 (memtest86+)”进行验证。如果您通常看不到 GRUB 启动菜单，则应该能够在首次启动时按住左移键。