MySQL Forums
Forum List  »  Data Recovery

InnoDB “corruption” ?
Posted by: Ingmar Sandberg
Date: September 18, 2012 05:24AM

Hallo!

I am a newbie in using MySQL and I face a problem with InnoDB.

I use

5.1.63-0ubuntu0.11.10.1 Apache/2.2.20 (Ubuntu) MySQL client version: 5.1.63

and receive continosly the following error during reading data from a localy installed mySQL db.

InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 387794.

After rebooting the system, I can gain access again to the db and I can read continuously the "corrupted" data w/o any problem at all (for few minutes or several hours) until the same problem re-appears (for different data read attempts)

Any idea on the source of the problem?

Thanks in advance,

I.



Here is the error.log:

I have checked the HDD with S.M.A.R.T utility and I could not find any problem
I deactivate apprmor w/o any result
I also tried SQL_NO_CACHE option in the query w/o any result
120918 13:07:06 InnoDB: Page checksum 3504102879, prior-to-4.0.14-form checksum 1216630776 InnoDB: stored checksum 2100325079, prior-to-4.0.14-form stored checksum 1216630776 InnoDB: Page lsn 2 1168743501, low 4 bytes of lsn at page end 1168743501 InnoDB: Page number (if stored to page already) 387794, 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 175 InnoDB: (index "PRIMARY" of table "OII"."dataset_cs_1") InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 387794. 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-innodb-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 120918 13:07:07 [Note] Plugin 'FEDERATED' is disabled. 120918 13:07:07 InnoDB: Initializing buffer pool, size = 64.0M 120918 13:07:07 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 2 2380293142 120918 13:07:07 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... InnoDB: Doing recovery: scanned up to log sequence number 2 2380293162 120918 13:07:07 InnoDB: Started; log sequence number 2 2380293162 120918 13:07:07 [Note] Event Scheduler: Loaded 0 events 120918 13:07:07 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.63-0ubuntu0.11.10.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

Options: ReplyQuote


Subject
Views
Written By
Posted
InnoDB “corruption” ?
5394
September 18, 2012 05:24AM
1982
September 25, 2012 11:34PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.