By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,911 Members | 1,209 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,911 IT Pros & Developers. It's quick & easy.

mysqlcheck: Table is marked as crashed and last repair failed

P: n/a
Hi everyone,

I'm using the command "mysqlcheck --all-databases --auto-repair --silent"
and I see these warnings and errors (listed below) on a daily occurrence.
What could cause these indexes to be out of order? Another thing I don't
understand is why an increase in the number rows constitutes a warning?

Hoping to here from MySQL users who have came across this. I'm using the
MyISAM storage engine and MySQL 4.1.11 on Red Hat Enterprise Linux.

Thanks,
Matt

DatabaseA.customer
warning : Table is marked as crashed and last repair failed
warning : Size of indexfile is: 516096 Should be: 315392
warning : Size of datafile is: 11271400 Should be: 11271380
error : Found 21681 keys of 11054
error : Corrupt
DatabaseA.customer
warning : Number of rows changed from 11054 to 21681
Jul 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.