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 On Wed, May 5, 2010 at 7:01 AM, Craig White wrote: > On Tue, 2010-05-04 at 18:35 -0700, Mark Phillips wrote: > > I have a very small mysql database that uses innodb tables. I just > > started getting the following error when I try to access the tables: > > > > ERROR 1033 (HY000): Incorrect information in file: > > './mailserver/virtual_users.frm' > > > > I google the error and it seems to have something to do with either > > the error logs being too large or the database being too large. When > > I 'show VARIABLES' at the mysql prompt I found: > > > > innodb_data_file_path ibdata1:10M:autoextend > > innodb_log_file_size 5242880 > > innodb_log_files_in_group 2 > > > > I looked in /var/lib/mysql and found > > > > li84-151:/home/mark# ls -al /var/lib/mysql > > total 10276 > > drwxr-xr-x 4 mysql mysql 4096 2010-05-04 17:15 . > > drwxr-xr-x 26 root root 4096 2009-10-26 08:28 .. > > -rw-r--r-- 1 mysql mysql 0 2009-10-14 15:40 debian-5.0.flag > > -rw-rw---- 1 mysql mysql 10485760 2010-04-15 09:00 ibdata1 > > drwx------ 2 mysql mysql 4096 2009-08-31 07:09 mailserver > > drwxr-xr-x 2 mysql mysql 4096 2009-10-14 15:40 mysql > > -rw------- 1 mysql mysql 7 2009-06-26 13:13 mysql_upgrade_info > > -rw-rw---- 1 mysql mysql 5242880 2010-04-15 09:00 ib_logfile0 > > -rw-rw---- 1 mysql mysql 5242880 2009-07-12 09:25 ib_logfile1 > > > > Based on some reading on the mysql site (version 5.0 on Debian Lenny) > > I removed the two ib_logfile and restarted mysql. I still get the same > > error. Based on the mysql docs, I thought the autoextend for the > > innodb_data_file_path would automatically take care of the data file > > growing beyond the file size limit. Is this correct? Do I have to > > increase the size of the innodb_data_file to make this error go away? > > How do I do that? Also, these tables have not changed since they were > > created, so I am pondering how the data file has grown. Any > > suggestions? > ---- > check out... > > http://www.danielschneller.com/2007/09/error-1033-hy000-on-innodb.html > > Craig > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > --------------------------------------------------- > 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 >