解决方案 »
- 求助:html文件用js调用php内容但数字无法显示?
- 关于WANem的使用问题
- 获取某一元素问题,急
- for莱鸟问题.
- 求phpchina邀请码,那位仁兄给发邮箱[email protected]
- 求php+mssql企业网站,送分
- 关于yahoo统计,把代码放进去了,就是统计不出来.
- 服务器2003 apache php codeigiter框架访问无法cookie写入
- html getJSON 无效
- smarty如何过滤掉多余的代码
- 求Discuz_X 1.5RC GBK版 跟 最土网utf8版本的用户整合
- 用UCenter Home上传头像时出错:Action not found.急急急急急!!!
MYSQL:v5.1101103 9:47:21 InnoDB: Started; log sequence number 0 1652990916
101103 9:47:21 [Note] Event Scheduler: Loaded 0 events
101103 9:47:21 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.32-community' socket: '' port: 3306 MySQL Community Server (GPL)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3722.
InnoDB: You may have to recover from a backup.
101103 9:53:04 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
中间一大段地址省略……
InnoDB: End of page dump
101103 9:53:04 InnoDB: Page checksum 636929620, prior-to-4.0.14-form checksum 1113392956
InnoDB: stored checksum 1665170788, prior-to-4.0.14-form stored checksum 1113392956
InnoDB: Page lsn 0 1652640275, low 4 bytes of lsn at page end 1652640275
InnoDB: Page number (if stored to page already) 3722,
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 83
InnoDB: (index "PRIMARY" of table "etaxsmg"."t_taxpayer_mtsmg")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3722.
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.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
101103 9:54:31 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...