- 論壇徽章:
- 0
|
請問造成崩潰的原因。
錯誤日志如下：
-----------------------------
101110 23:52:14 InnoDB: Page checksum 3123610979, prior-to-4.0.14-form checksum 1090887538
InnoDB: stored checksum 641667391, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 501 2805892917, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 218281,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 123
InnoDB: Page may be an index page where index id is 0 303
InnoDB: (index "PRIMARY" of table "customers"."name")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 218281.
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.
101110 23:52:14 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=33554432
read_buffer_size=8388608
max_used_connections=949
max_threads=151
threads_connected=32
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1939154 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
101110 23:52:15 mysqld_safe Number of processes running now: 0
101110 23:52:15 mysqld_safe mysqld restarted
101110 23:52:16 [Note] Plugin 'FEDERATED' is disabled.
101110 23:52:16 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 1053 388313431
101110 23:52:19 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 1053 393555968
InnoDB: Doing recovery: scanned up to log sequence number 1053 398798848
InnoDB: Doing recovery: scanned up to log sequence number 1053 404041728
....... |
|
免費注冊
發(fā)表于 2010-11-11 17:28
