MySQL accesses a data crash

Symptom: When mysqldump exports data or accesses a table or data entry, mysql directly fails. The log is as follows: InnoDB: databasepage0000uption

Symptom: When mysqldump exports data or accesses a table or data entry, mysql directly fails. The log is as follows: InnoDB: Database page upload uption

Symptom: mysql crashes when mysqldump exports data or accesses a table or data.
The log is as follows:
InnoDB: Database page upload uption on disk or a failed
InnoDB: file read of page 26400.
InnoDB: You may have to recover from a backup.
120217 15:45:53 InnoDB: Page dump in ascii and hex (16384 bytes ):
Len 16384; hex a922822af0c7bcef6d93dadcf4f63e8331d51e7a490667defbefxxxx ..................
InnoDB: End of page dump

F 6 PE a r zx3120217 15:45:53 InnoDB: Page checksum 3458627726, prior-to-4.0.14-form checksum 796906866
InnoDB: stored checksum 2837611050, prior-to-4.0.14-form stored checksum 2410301789
InnoDB: Page lsn 836050554 1225156574, low 4 bytes of lsn at page end 2266014174
InnoDB: Page number (if stored to page already) 4039621871,
InnoDB: space id (if created with> = MySQL-4.1.1 and stored already) 4222022822
InnoDB: Database page upload uption on disk or a failed
InnoDB: file read of page 26400.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has upted its own file cache
InnoDB: and rebooting your computer removes
InnoDB: error.
InnoDB: If the specified upt page is an index page
InnoDB: you can also try to fix the specified uption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the specified upt table. You can use CHECK
InnoDB: TABLE to scan your table for processing uption.
InnoDB: See also
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a temporary upt database page.
Solution: for specific reasons, see:

First D: \ cn. tsoft. system \ mysql5.1.37 \ bin> mysqlcheck-uroot-pxxxx-P3306 -- all-database to locate which table has a problem
The execution result is as follows:
Tech_soft_drp_361new.pos_tradebill_cashredeem_item OK
Mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when e
Xecuting 'check TABLE ...'

According to tech_soft_drp_361new.pos_tradebill_cashredeem_item, the next table is pos_tradebill_item.

Remove # innodb_force_recovery = 1 # In my. ini and restart the mysql service.

Then export the pos_tradebill_item data to the file (check whether the number of exported data items is correct during export !) (Record select count (*) from pos_tradebill_item comparison with the number of exported items)

Find the table creation Statement of pos_tradebill_item.

Delete the pos_tradebill_item table

Recreate the pos_tradebill_item table.

Import pos_tradebill_item data (add innodb_force_recovery = 1 and #. innodb_force_recovery = 1 mode does not support writing when importing data)

,