Hi,

I have a very strange problem whereby one particular table in our database is repeatedly (on average, every couple of days) generating errors stating that the table is crashed and needs to be repaired. Running a repair fixes it.

What makes it strange (and something that I've never encountered before) is the following:

1. There is one particular table which it happens to a lot, and a few other tables where it happens occasionally. Everything else is fine.

2. None of the tables where it happens are among the most heavily used or commonly updated.

3. There is no shortage of disk space.

4. The disk system reports no errors.

5. We have multiple databases with an identical structure but different content (we are an online retailer and each database is a separate storefront), but the problem occurs in all the databases - but the same tables in each database. It doesn't always happen to each database at the same time - it seems to be random.

6. (This is the really strange one) We have two separate servers with identical copies of the databases, one for production use and one for development use, and it happens independently on both of them - but still the same tables (and, specifically, the same table that it happens to more often than any other).

7. And, of course, the obvious statement: we haven't changed the structure of this database recently (it hasn't changed for months, if not years).

We are running MySQL 5.0.77 on Centos. All the databases use MyISAM exclusively.

Given the above, can anyone suggest any possible causes?

Thanks

Mark
--
http://mark.goodge.co.uk

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=arch...@jab.org

Reply via email to