severity 343639 normal
tag 343639 + moreinfo upstream
thanks

Hello Olaf

On 2005-12-16 Olaf van der Spek wrote:
> After a restart I got 'Incorrect key file for table' errors and 'Table '...'
> is marked as crashed and should be repaired' errors.
I've got these kind of errors a couple of times in the last few years. Mostly
a "REPAIR TABLE" fixed it.

Such a bug has not been reported in the last couple of months at least which
makes a general problem in this version at least not likely.

To help, you could send a copy of the data files to mysql via
http://bugs.mysql.com and ask them to investigate them to find the cause of
the corruption.

Also likely is bad memory/bad cpu, the usual suspects, but I guess you know
them..

Or is there any possibility to reproduce this table crash after repairing the
table once? This would clearly indicate a bug in MySQL.

See http://dev.mysql.com/doc/refman/5.0/en/crashing.html

> I'm wondering, is the crashed table checker safe to run without external
> locking (and a busy server)?
As long as there is only one MySQL on your server, yes.
See http://ftp.osuosl.org/pub/mysql/doc/refman/5.0/en/system.html for an
explanation of this option.

bye,

-christian-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to