MYSQL 中的一个表查询数据的时候，MYSQL直接挂掉。但是能正常插入数据。
开始我以为是硬盘有坏道，但是把数据拷贝出来后，重新查询拷贝出来的数据，还是挂掉。日志信息如下
30219 16:55:13 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 643921955.
InnoDB: Doing recovery: scanned up to log sequence number 0 643921955
130219 16:55:13 InnoDB: Started; log sequence number 0 643921955
130219 16:55:13 [Note] D:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.26-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1181.
InnoDB: You may have to recover from a backup.
130219 16:55:47 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000303134323431367c3230313330313031313133313233340000000469ed0000000440061667616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee786b10f8000124ee786b12a1104082301000140006b38393836303030343036303833303134323431367c3230313330313031313731363030000000046ad500000004400e8767616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee78795c88000124ee78797341104082401040148006c38393836303030343036303833303134323431367c3230313330313038313034343539330000000485b5000000044028f267616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee7f15ef18000124ee7f16037110408240100015026d038393836303030343036303833303134323431367c3230313330313131313235303635360000000494430000000457140c67616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee81f761b8000124ee81f76fd0e02080b2400000158007338393836303030343036303834303139373537317c3230313231323031313532323231380000000401bd00000004400821313539343237393434313467616d653130303259594d423532352c31302c322e332e37800000018000124cd50c10e48000124cd50c11c31104080e2400000160007b38393836303030343036303835303033363939387c32303132313131383136353433353900000003d243000000044023f12b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd019c9b58000124cd01a17da1104080e2400050168007b38393836303030343036303835303033363939387c32303132313131383139333734303600000003d2670000000440143a2b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd01a385c8000124cd01a3c3b1104080e2400000170007b38393836303030343036303835303033363939387c32303132313132313132303035393300000003dc8900000004420d992b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd046df048000124cd046e2b0110308002400000178006c38393836303030343036303835303037333039347c32303132313131343033343339353300000003c11a000000044009a167616d65313030325a535047542d4e373030302c31302c322e332e35800000018000124ccfdac0a98000124ccfdb0ecf120308002400000180006d38393836303030343036303835353138383834367c323031323132303431323031333930000000040c2200000004420b7a67616d65313030325a535047542d5335383330692c31302c322e332e36800000018000124cd5395a2a8000124cd539a84f120308002300040188006c38393836303030343036303835353138383834367c3230313231323034313230313738000000040c2200000004420bc267616d65313030325a535047542d5335383330692c31302c322e332e36800000018000124cd5395a2c8000124cd539a851110408002400000190006c38393836303030343036303835353337303132397c32303132313132353138333635363200000003ecaa0000000440164667616d65313030325a53503447542d49393030332c31302c322e332e35800000018000124cd084e0788000124cd0852e9d1404082401000198007038393836303030343036303835353431373530327c323031323038313631363430363235000000037f5d8000000458333267616d6531303031636d63635a54452d542055393630732c31302c322e332e37800000018000124cbe199cd48000124cbe199f791104080024000001a0006c38393836303030343036303835353531383334367c32303132313p6 4v2 1D/ - , *g( & %6#v! B h ` n ] $ c _ $!U;InnoDB: End of page dump
130219 16:55:47 InnoDB: Page checksum 2356945576, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 2136983808
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 539238741
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1181.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.mysql
开始我以为是硬盘有坏道，但是把数据拷贝出来后，重新查询拷贝出来的数据，还是挂掉。日志信息如下
30219 16:55:13 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 643921955.
InnoDB: Doing recovery: scanned up to log sequence number 0 643921955
130219 16:55:13 InnoDB: Started; log sequence number 0 643921955
130219 16:55:13 [Note] D:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.26-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1181.
InnoDB: You may have to recover from a backup.
130219 16:55:47 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000303134323431367c3230313330313031313133313233340000000469ed0000000440061667616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee786b10f8000124ee786b12a1104082301000140006b38393836303030343036303833303134323431367c3230313330313031313731363030000000046ad500000004400e8767616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee78795c88000124ee78797341104082401040148006c38393836303030343036303833303134323431367c3230313330313038313034343539330000000485b5000000044028f267616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee7f15ef18000124ee7f16037110408240100015026d038393836303030343036303833303134323431367c3230313330313131313235303635360000000494430000000457140c67616d6531303031636d636347542d53373536382c31352c342e302e34800000018000124ee81f761b8000124ee81f76fd0e02080b2400000158007338393836303030343036303834303139373537317c3230313231323031313532323231380000000401bd00000004400821313539343237393434313467616d653130303259594d423532352c31302c322e332e37800000018000124cd50c10e48000124cd50c11c31104080e2400000160007b38393836303030343036303835303033363939387c32303132313131383136353433353900000003d243000000044023f12b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd019c9b58000124cd01a17da1104080e2400050168007b38393836303030343036303835303033363939387c32303132313131383139333734303600000003d2670000000440143a2b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd01a385c8000124cd01a3c3b1104080e2400000170007b38393836303030343036303835303033363939387c32303132313132313132303035393300000003dc8900000004420d992b3836313539343238303336313167616d65313030325a53503547542d49393330302c31352c342e302e34800000018000124cd046df048000124cd046e2b0110308002400000178006c38393836303030343036303835303037333039347c32303132313131343033343339353300000003c11a000000044009a167616d65313030325a535047542d4e373030302c31302c322e332e35800000018000124ccfdac0a98000124ccfdb0ecf120308002400000180006d38393836303030343036303835353138383834367c323031323132303431323031333930000000040c2200000004420b7a67616d65313030325a535047542d5335383330692c31302c322e332e36800000018000124cd5395a2a8000124cd539a84f120308002300040188006c38393836303030343036303835353138383834367c3230313231323034313230313738000000040c2200000004420bc267616d65313030325a535047542d5335383330692c31302c322e332e36800000018000124cd5395a2c8000124cd539a851110408002400000190006c38393836303030343036303835353337303132397c32303132313132353138333635363200000003ecaa0000000440164667616d65313030325a53503447542d49393030332c31302c322e332e35800000018000124cd084e0788000124cd0852e9d1404082401000198007038393836303030343036303835353431373530327c323031323038313631363430363235000000037f5d8000000458333267616d6531303031636d63635a54452d542055393630732c31302c322e332e37800000018000124cbe199cd48000124cbe199f791104080024000001a0006c38393836303030343036303835353531383334367c32303132313p6 4v2 1D/ - , *g( & %6#v! B h ` n ] $ c _ $!U;InnoDB: End of page dump
130219 16:55:47 InnoDB: Page checksum 2356945576, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 2136983808
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 539238741
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1181.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.mysql
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货