MyISAM index corruption
I have a webserver running a few websites. During last two days, indexes in my databases often became corrupt. I get errors like this in error log:
050804 15:40:41 [ERROR] /usr/local/libexec/mysqld: Can't open file: 'rasstext.MYI' (errno: 145)
There are 36 databases (including mysql), total size of data/index files is only about 150 megs.
OS I use is FreeBSD 5.4 Release. Mysql version is 4.1.12, installed from port, with linuxthreads support.
I couldn't find any pattern in those errors - looks like that random tables that get inserted into have their indexes corrupted.
First I thought that delayed key writes may cause this - turning them off didn't help. Also I tried setting table cache size to very small value, so server closes/opens table files almost any time it needs to access them. Didn't help either.
mysqld never crashed. Table indexes get repaired on the fly (I have myisam_recover = BACKUP,FORCE), though I lost some records when repairing one of the tables:
050804 4:26:01 [ERROR] /usr/local/libexec/mysqld: Can't open file: 'banner_adstats.MYI' (errno: 145)
050804 4:26:01 [Warning] Checking table: './jewelry/banner_adstats'
050804 4:26:01 [Warning] Recovering table: './jewelry/banner_adstats'
050804 4:26:01 [Note] Retrying repair of: './jewelry/banner_adstats' with keycache
050804 4:26:02 [Note] Found 3663 of 3674 rows when repairing './jewelry/banner_adstats'
So, my questions are:
What should I do to determine what is causing problems and give a better report?
Is switching to InnoDB until this bug gets found and fixed a good idea?
Thanks.
Alexey
Subject
Views
Written By
Posted
MyISAM index corruption
10078
August 04, 2005 08:19AM
3393
August 05, 2005 01:13AM
3130
August 05, 2005 05:22AM
2971
August 08, 2005 04:34AM
2967
August 29, 2005 12:56PM
3038
August 30, 2005 02:24AM
3075
August 30, 2005 03:40AM
2854
March 27, 2006 12:32PM
2697
March 28, 2006 02:42AM
2758
March 28, 2006 05:18PM
2944
March 29, 2006 03:35AM
2886
June 04, 2007 11:51AM
3041
July 15, 2007 04:10PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.