Could it be getting larger than 2G on a filesystem with a 2G/file limit?

Jon Wagoner wrote:

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]



Reply via email to