MySQL table .MYI file keeps crashing/getting corrupted

I recently moved a traffic tracking database, with the primary table being about 1GB in size, from a dedicated server (2GB RAM) to a VPS (2GB burst RAM, nothing else on the VPS except for this database).

I didn't have any problems while it was on the dedicated server, but now the primary table's .MYI file is being continually corrupted. I repair it using myisamchk, but each time it becomes corrupted after a short period of time (under an hour I would guess; not sure of the exact frequency), rendering the table unusable. I get a "Can't open file: 'table_name.MYI' (errno: 144)" message.

The traffic tracking script regularly ANALYZEs and OPTIMIZEs the main table after a certain number of row inserts; I suspect it is during this step that the table is crashing and the index file is being corrupted. However I don't think it's a good idea for me to disable this functionality. Also, it worked fine for months at the other installation without any problems.

The only thing I could think of that might be causing the issue is some setting in the my.cnf file. Here's the contents of my.cnf:
Code:
[mysqld]
set-variable = max_connections=1000
connect_timeout=15
key_buffer=32M
join_buffer=1M
record_buffer=1M
sort_buffer=2M
table_cache=1028
thread_cache_size=286
max_allowed_packet=16M
wait_timeout=15
query_cache_limit=2M
query_cache_size=64M
query_cache_type=1
thread_concurrency=2
Could any of these settings be causing the problem? Or might it be something else?

 

 

 

 

Top