# Tables start corrupting after myisamchk repair

**URL:** <https://forums.percona.com/t/tables-start-corrupting-after-myisamchk-repair/629>\
**Category:** Other MySQL® Questions\
**Created:** [February 12, 2008, 1:05pm UTC](https://forums.percona.com/t/tables-start-corrupting-after-myisamchk-repair/629 "2008-02-12T13:05:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ktmtalk](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@ktmtalk](https://forums.percona.com/u/ktmtalk)\
**Post date:** [February 12, 2008, 1:05pm UTC](https://forums.percona.com/t/tables-start-corrupting-after-myisamchk-repair/629/1 "2008-02-12T13:05:48Z")

</div>

I have a Invision 1.2 forum.  
Linux Centos  
PHP 4.3.9  
MySql 4.1.20

The application has been running with no problems whatsoever for one year.

I wanted to “optimze” the tables to remove the overhead from deleted records. Big Mistake… that was the beginning of my problems.

I used PhpMyadmin to optimize all tables except two that were very large (2 million records).

I then shut down Mysql, and did a myisamchk repair on the two really large tables. No error were found or reported.

I then fired up MySqld and within an hour, started getting a corrupted table (errno 145). I shutdown mysql and once again ran myisamchk to repair the table. No errors are reported during the repair but a check before the repair does show that it was corrupted.

Ever since the initial PhpMyadmin optimize and the myisamchk repair on the large tables, I am getting a corrupted table within a few hours of running the forum.

There were no problems for over a year before I ran the initial optimization - after that, it is happening constantly.

Any ideas?? Need more info???

At wits end…

-pat-