Alex,

Repair tables failed with a similar error message. So I dropped the tables,
recreated them, SAVED a backup copy ;-), and everything is working now. I
created a small python script to check the size of mysql.err nightly and
send me an email if it starts to log errors with the database.

Cheers!

Mark

On Wed, May 5, 2010 at 8:35 PM, Alex Dean <alex@crackpot.org> wrote:

>
>
> On May 5, 2010, at 12:13 PM, Mark Phillips wrote:
>
>  Alex,
>>
>> Thanks for the link. I have no idea how the tables were
>> corrupted......They were created about 9 months ago to define some virtual
>> host, aliases, and users for a postfix email server. Postfix only reads
>> them, and they have not been written to since they were created. I have
>> paper copies, so I will just recreate them by hand. I am not sure how to
>> keep it from happening again.
>>
>
> Have you tried 'REPAIR TABLE virtual_aliases', etc?  The data files may be
> fine, and MySQL may be able to fix whatever is wrong with the FRM file for
> you.  Worth a try if your next step is to drop and recreate.  If it doesn't
> work, you're no worse off than now.  Good luck, and let us know how it goes!
>
> alex
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>