I think I have tracked the problem down to deletes. In an environment with many deletes I've noticed that the rate of table corruption across my cluster of db server increases for the boxes with many deletes.
I've been able to get around this issue by periodically checking tables on off hours and repairing them as the issue develops. - Dathan Vance Pattishall - Sr. Programmer and mySQL DBA for FriendFinder Inc. - http://friendfinder.com/go/p40688 -->-----Original Message----- -->From: Jon Wagoner [mailto:[EMAIL PROTECTED] -->Sent: Monday, November 03, 2003 11:48 AM -->To: [EMAIL PROTECTED] -->Subject: table gets corrupted often --> -->I have a table that tends to get corrupted and needs to be repaired every -->few days. It is used for logging various messages in my web app. The -->structure is: --> -->CREATE TABLE log ( --> log_id int(11) unsigned NOT NULL auto_increment, --> log_type tinyint(1) unsigned NOT NULL default '0', --> when datetime NOT NULL default '0000-00-00 00:00:00', --> msg text NOT NULL, --> PRIMARY KEY (log_id) -->) TYPE=MyISAM; --> -->I am running MySQL 4.0.16 on a Red Hat 7.3 server. There are about 200 -->other tables in the database, and none of the rest have a problem. --> -->The table has about 200,000-300,000 records added daily, and is cleaned -->out -->every week or so. I have tried dropping and recreating the table, but -->that -->does not seem to help. The table is almost exclusively accessed by -->INSERTs. --> -->Any ideas why this particular table would be so unstable? --> --> -->-- -->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]
