Christian, do you mean that even if you recreate the whole tablespace, you will get corruption on some data page rather quickly?
Please send to me the whole .err log for analysis. The printout below shows that the start and the end of the page are ok, but in the middle there is some change that has happened since InnoDB wrote the page to the ibdata file. Thus, this is probably an OS/drivers/hardware bug. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Register now for the 2004 MySQL Users Conference! http://www.mysql.com/events/uc2004/index.html ----- Original Message ----- From: "Christian Rabe" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Wednesday, March 10, 2004 2:11 PM Subject: checksum error in innodb - what can do to find the reason ? > Hello together, > > I'm getting the following error every few hours. I can force it by > trying to dump the db. > Even if I drop the named table and create an empty one the error still > occurs after some time. > > I tried both, raw-device and normal. But nothing solves this problem. > The data is stored on a raid and the discs should be faultless. > > Running debian sarge with kernel 2.4.25 > 2x2.4 GHz Xeon > 2GB RAM > RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01) > > -------------------------------------------------------------------------- -------------- > InnoDB: Database page corruption on disk or a failed > InnoDB: file read of page 105283. > InnoDB: You may have to recover from a backup. > 040310 1:01:09 InnoDB: Page dump in ascii and hex (16384 bytes): > len 16384; hex > 9f84195800019b4300019a3000019b5500000001c8b03f3545bf000000000000000000000000 001a3f5a00d324091f95000000020002006800000000000000000000000000000 > 040310 1:01:09 InnoDB: Page checksum 3314471633, prior-to-4.0.14-form > checksum 2546962952 > InnoDB: stored checksum 2676234584, prior-to-4.0.14-form stored checksum > 2546962952 > InnoDB: Page lsn 1 3366993717, low 4 bytes of lsn at page end 3366993717 > InnoDB: Page may be an index page where index id is 0 22 > InnoDB: and table adserver/banner_stats_running index PRIMARY > InnoDB: Database page corruption on disk or a failed > InnoDB: file read of page 105283. > 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.html about > InnoDB: forcing recovery. > InnoDB: Ending processing because of a corrupt database page. > -------------------------------------------------------------------------- -------- > > mysql> show table status like 'banner_stats_running'; > +----------------------+--------+------------+----------+----------------+-- -----------+-----------------+--------------+-----------+----------------+-- -----------+-------------+------------+----------------+-------------------- --------------------------------+ > | Name | Type | Row_format | Rows | Avg_row_length > | Data_length | Max_data_length | Index_length | Data_free | > Auto_increment | Create_time | Update_time | Check_time | Create_options > | Comment | > +----------------------+--------+------------+----------+----------------+-- -----------+-----------------+--------------+-----------+----------------+-- -----------+-------------+------------+----------------+-------------------- --------------------------------+ > | banner_stats_running | InnoDB | Fixed | 11750021 | 154 > | 1812987904 | NULL | 3481616384 | 0 | > NULL | NULL | NULL | NULL | | InnoDB > free: 43975680 kB; InnoDB free: 15213568 kB | > +----------------------+--------+------------+----------+----------------+-- -----------+-----------------+--------------+-----------+----------------+-- -----------+-------------+------------+----------------+-------------------- --------------------------------+ > 1 row in set (0.52 sec) > Note: the first Innodb-free is from a dump > > mysql> \s > -------------- > mysql Ver 12.22 Distrib 4.0.18, for pc-linux (i686) > Connection id: 173011 > Current database: > Current user: [EMAIL PROTECTED] > SSL: Not in use > Current pager: stdout > Using outfile: '' > Server version: 4.0.18 > Protocol version: 10 > Connection: Localhost via UNIX socket > Client characterset: latin1 > Server characterset: latin1 > UNIX socket: /tmp/mysql.sock > Uptime: 42 min 18 sec > > Threads: 23 Questions: 10700857 Slow queries: 0 Opens: 244 Flush > tables: 1 Open tables: 238 Queries per second avg: 4216.256 > -------------- > > > Any help appreciated :) > > Regards, > Christian Rabe > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
