ถูกต้องครับ มีการเก็บ log ครับ
แต่ hdd ใช้ไปแค่ 50% เองครับ ท่าน
110701 16:00:38 InnoDB: Page checksum 3735928559 (32bit_calc: 3735928559), prior-to-4.0.14-form checksum 3735928559
InnoDB: stored checksum 3735928559, prior-to-4.0.14-form stored checksum 3735928559
InnoDB: Page lsn 124 607266492, low 4 bytes of lsn at page end 607136925
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a file space header page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
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.htmlInnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
110701 16:00:38 mysqld_safe mysqld from pid file /var/lib/mysql/HOSxPG6.pid ended