Hi!
On Aug 01, Keith Thompson wrote:
> Thanks Mike,
>
> I've always ignored CHECK TABLE because I always thought it was
> just for MyISAM.
>
> Then, I decided to run CHECK TABLE on all my tables (which for the
> ones with 125 million rows will probably be running for a while).
> The problem now is that all of my larger tables are reported as
> being corrupt--every single table with more than say 500,000
> records is reported as corrupt. Wow! Could this be true? The
> tables all access fine and only these two smaller tables had these
> count(*) mismatch problems (and were the only two smaller tables
> that came up corrupt).
>
> How did this happen? I've never gotten an error in my .err file,
> never had a hardware access failure in the system logs, and have
> done very little with this server beyond initially loading it
> (by replaying mysqldump output in the first place) and letting it
> stay up to date with replication.
Just a thought - if you upgraded, be sure to read all changelog entries
carefully, there were few bugfixes that would require to dump/reload
innodb tables (otherwise they'll be corrupted).
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
