mysql5几天后无法运行问题

xiaobaiaA 发布于 2014/12/20 20:54
阅读 743
收藏 0

错误代码  大家看看什么问题  谢谢大家啦  

information that should help you find out what is causing the crash.
141220 14:40:19 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141220 14:40: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...
141220 14:40:19  InnoDB: Started; log sequence number 0 644389606
141220 14:40:19 [Note] Event Scheduler: Loaded 0 events
141220 14:40:19 [Note] D:\AHXX\AHXXSRV\MySQL5\bin\mysqld.exe: ready for connections.
Version: '5.1.37-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 00000000000000c4000000000576ffffffff000000000004aaaaaaaaaaaaaaaaaaaaaaaaaaaaaeaa; asc              v                          ;
InnoDB: Serious error! InnoDB is trying to free page 633
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
141220 14:40:21  InnoDB: Assertion failure in thread 4732 in file .\fsp\fsp0fsp.c line 3007
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
141220 14:40:21 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=524288
max_used_connections=0
max_threads=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 531540 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...
006DF323    mysqld.exe!???
006DF4DD    mysqld.exe!???
00711A1C    mysqld.exe!???
006D8EF5    mysqld.exe!???
01E6BC80    
032F4000    
006FFFD5    
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

加载中
OSCHINA
登录后可查看更多优质内容
返回顶部
顶部