MySQL Forums
Forum List  »  InnoDB

Re: Problem of data corruption
Posted by: Benjamin Gonay
Date: February 17, 2005 03:40AM

Hi Heikki,

Thanks for your help. Here's part of the error server file : (part because it's cyclic).
i've cut hex dump, only a part of the first and last line left. The problem is on the table ORDER.historic . A table description is below.

050131 23:36:44 InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.0.21-standard-log' socket: '/tmp/mysql.sock' port: 3306 Official MySQL-standard binary
050201 8:06:03 Aborted connection 601 to db: 'WHO' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:08:49 Aborted connection 593 to db: 'ORDER' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 12319.
InnoDB: You may have to recover from a backup.
050201 8:22:41 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 564b2d94000

t t t9 7 5 3 1 / - ) $N! 1 z Y } k B - e(\ { Z ;InnoDB: End of page dump
050201 8:22:41 InnoDB: Page checksum 1801016824, prior-to-4.0.14-form checksum 677160827
InnoDB: stored checksum 1447767444, prior-to-4.0.14-form stored checksum 677160827
InnoDB: Page lsn 2 2501466656, low 4 bytes of lsn at page end 2501466656
InnoDB: Page may be an index page where index id is 0 4763
InnoDB: (index `PRIMARY` of table `ORDER/historic`)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 12319.
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: Look also at section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about
InnoDB: forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
050201 8:22:41 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2548360978
InnoDB: Doing recovery: scanned up to log sequence number 2 2550428178
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 27943 row operations to undo
InnoDB: Trx id counter is 0 1194240
050201 8:22:41 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 4
9 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 1193846, 27943 rows to undo
InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 1193846 completed
InnoDB: Rollback of uncommitted transactions completed
InnoDB: Last MySQL binlog file position 0 10683147, file name ./cluster-bin.070
050201 8:22:45 InnoDB: Flushing modified pages from the buffer pool...
050201 8:22:48 InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.0.21-standard-log' socket: '/tmp/mysql.sock' port: 3306 Official MySQL-standard binary
050201 8:33:16 Aborted connection 56 to db: 'SESAM' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:34:04 Aborted connection 65 to db: 'ORDER' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:35:47 Aborted connection 30 to db: 'SESAM' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:36:42 Aborted connection 23 to db: 'WHO' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:37:47 Aborted connection 54 to db: 'NOTIF' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
050201 8:39:16 Aborted connection 42 to db: 'SESAM' user: 'lib_usr' host: `localhost' (Got an error reading communication packets)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 12319.
InnoDB: You may have to recover from a backup.
050201 8:40:55 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 564b2d9400003

t t t9 7 5 3 1 / - ) $N! 1 z Y } k B - e(\ { Z ;InnoDB: End of page dump
050201 8:40:55 InnoDB: Page checksum 1801016824, prior-to-4.0.14-form checksum 677160827
InnoDB: stored checksum 1447767444, prior-to-4.0.14-form stored checksum 677160827
InnoDB: Page lsn 2 2501466656, low 4 bytes of lsn at page end 2501466656
InnoDB: Page may be an index page where index id is 0 4763
InnoDB: (index `PRIMARY` of table `ORDER/historic`)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 12319.
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: Look also at section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about
InnoDB: forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
050201 8:40:56 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2599680687
InnoDB: Doing recovery: scanned up to log sequence number 2 2604266262
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 13560 row operations to undo
InnoDB: Trx id counter is 0 1195008
050201 8:40:56 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 4
9 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 1194591, 13560 rows to undo
InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 0 1194591 completed
InnoDB: Rollback of uncommitted transactions completed
InnoDB: Last MySQL binlog file position 0 13420801, file name ./cluster-bin.071
050201 8:41:03 InnoDB: Flushing modified pages from the buffer pool...
050201 8:41:06 InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.0.21-standard-log' socket: '/tmp/mysql.sock' port: 3306 Official MySQL-standard binary

<----CUT---->

Here the : show create table 'historic' , it was that table causing this problem :
*************************** 1. row ***************************
Table: historic
Create Table: CREATE TABLE `historic` (
`order_number` varchar(10) NOT NULL default '',
`order_item` char(3) NOT NULL default '',
`order_count` smallint(5) unsigned NOT NULL default '0',
`mat_number` varchar(10) NOT NULL default '',
`mat_desc` varchar(50) NOT NULL default '',
`wbs` varchar(21) NOT NULL default '',
`cost_number` varchar(6) NOT NULL default '',
`creator` varchar(6) default NULL,
`goods_recipient` varchar(6) default NULL,
`c_quant` smallint(6) unsigned NOT NULL default '0',
`d_quant` smallint(6) unsigned NOT NULL default '0',
`c_delivery` date default NULL,
`d_date` date default NULL,
`d_delivery` date default NULL,
`r_date` date default NULL,
`r_completed` char(1) default NULL,
`completed_date` date default NULL,
`plant_receiver` varchar(4) NOT NULL default '',
`wo` varchar(255) default NULL,
PRIMARY KEY (`order_number`,`order_item`,`order_count`),
KEY `mat_number` (`mat_number`)
) TYPE=InnoDB COMMENT='Gestion des commandes.'
1 row in set (0.00 sec)

It's since that day i'm checking all tables from all databases nightly.... :-)

Thanks.
Benjamin

Options: ReplyQuote


Subject
Views
Written By
Posted
4320
January 21, 2005 07:49AM
2730
January 21, 2005 07:53AM
2676
January 21, 2005 03:52PM
2615
January 25, 2005 04:57PM
2850
January 27, 2005 02:55AM
2756
February 16, 2005 07:58AM
2548
February 25, 2005 06:54AM
2567
March 03, 2005 03:07AM
2771
February 16, 2005 11:15AM
Re: Problem of data corruption
3527
February 17, 2005 03:40AM
2579
February 17, 2005 03:25PM
2577
March 17, 2005 01:55AM
2571
March 18, 2005 11:19AM
2899
March 31, 2005 01:04PM
2614
April 04, 2005 08:21AM
2794
April 04, 2005 09:24AM
2970
April 04, 2005 11:38PM
2611
April 19, 2005 09:47AM


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.