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.
Thanks!
Mark
On Wed, May 5, 2010 at 8:38 AM, Alex Dean <
alex@crackpot.org> wrote:
>
> On May 5, 2010, at 9:55 AM, Mark Phillips wrote:
>
> Craig,
>>
>> I saw that particular article, and it is not the cause of my problem. My
>> tables were setup with the "autoextend" parameter, so they grow as then need
>> to, at least according to the mysql docs. Thanks for looking for that.
>>
>> I have even tried to repair the tables, but with no success:
>>
>> mysql> repair table mailserver.virtual_aliases, mailserver.virtual_users,
>> mailserver.virtual_domains;
>>
>> +----------------------------+--------+----------+-------------------------------------------------------------------+
>> | Table | Op | Msg_type | Msg_text
>> |
>>
>> +----------------------------+--------+----------+-------------------------------------------------------------------+
>> | mailserver.virtual_aliases | repair | Error | Incorrect information
>> in file: './mailserver/virtual_aliases.frm' |
>> | mailserver.virtual_aliases | repair | error | Corrupt
>> |
>> | mailserver.virtual_users | repair | Error | Incorrect information
>> in file: './mailserver/virtual_users.frm' |
>> | mailserver.virtual_users | repair | error | Corrupt
>> |
>> | mailserver.virtual_domains | repair | Error | Incorrect information
>> in file: './mailserver/virtual_domains.frm' |
>> | mailserver.virtual_domains | repair | error | Corrupt
>> |
>>
>> +----------------------------+--------+----------+-------------------------------------------------------------------+
>> 6 rows in set (0.00 sec)
>>
>> It seems the tables are corrupt, so i will have to drop them and then
>> rebuild them.
>>
>> Thanks for the reference!
>>
>> Mark
>>
>
> The .frm file is the basic table definition, like what columns are in the
> table, what storage engine to use, etc. Try to determine how these got
> corrupted/changed. I've never seen MySQL itself corrupt a .frm, so I'd
> suspect some other process or user was mucking with them. Did you perhaps
> restore a backup .frm which had a table definition which doesn't match
> what's in the InnoDB data files? (Wild guess)
>
> http://forge.mysql.com/wiki/MySQL_Internals_File_Formats
>
> 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
>
---------------------------------------------------
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
(text/plain)