innodb crash.

jason0127

我的mysql 在做mysqldump的時候會出現(xiàn)以下錯誤，已經(jīng)出現(xiàn)過幾次了，這些錯誤前面會有一堆的亂碼。



                                                                                                                                                                               p. ( "            c    N  T;InnoDB: End of page dump
090805 16:05:18  InnoDB: Page checksum 2131925968, prior-to-4.0.14-form checksum 2896155678
InnoDB: stored checksum 90718654, prior-to-4.0.14-form stored checksum 2896155678
InnoDB: Page lsn 90 1322256212, low 4 bytes of lsn at page end 1322256212
InnoDB: Page number (if stored to page already) 8233,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 769
InnoDB: Page may be an index page where index id is 0 2864
InnoDB: (index "PRIMARY" of table "m4n"."DASHBOARD_HISTORICAL")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 8233.
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-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
090805 16:05:19 mysqld_safe Number of processes running now: 0
090805 16:05:19 mysqld_safe mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090805 16:05:20  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: Last MySQL binlog file position 0 6554325, file name ./mysql-bin.000137
090805 16:05:25  InnoDB: Started; log sequence number 119 3031521402
090805 16:05:25 [Note] Recovering after a crash using mysql-bin
090805 16:05:25 [Note] Starting crash recovery...
090805 16:05:25 [Note] Crash recovery finished.
090805 16:05:45 [Note] Event Scheduler: Loaded 0 events
090805 16:05:45 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.33-community-log'  socket: '/var/backup/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)

jason0127

沒人頂下么？

Coolriver

出面了葉損壞了。建義設(shè)置innodb_force_recovery
如：
innodb_force_recovery ＝ 3
試一下。
Dump出來完畢了。把那個庫備份起來，然后重新導(dǎo)入。

祝你好運。

jason0127

mysql自己重起后又好了呢，，而且那張表又能重新dump出來，很奇怪的。而且前面所說的出現(xiàn)過幾次并不是同個mysql,有兩三個mysql 出現(xiàn)過這種情況，都是在不同機器上。所幸的還好都不是生產(chǎn)庫。

Keeff

have a try

http://keeff.bluekee.com/read.php?9