MySQL 3.23.33:
This morning, one of my tables suddenly reported index corruption. I locked
the table, fixed with myisamchk -o, unlocked, and thought the problem was
solved. But it keeps on re-corrupting (I'm not even writing anything to it
first). Plus any query on that table which uses a "where" clause takes an
*extremely long time to execute. Queries that normally take .01 seconds are
taking 10-15 *minutes*. Or more.
DESC TABLE shows that the indexes are all still in place. I even tried
dropping and re-creating an index, but that didn't seem to make a
difference. EXPLAIN on the queries shows that MySQL still knows to use the
indexes that are there. Yet obviously something is quite wrong. One other
odd thing: after one of the (many) repair operations, I started getting
"disk quota filled" errors. It turned out that a 142M file with the prefix
"#sql" had surfaced in /tmp. I deleted it, and things went back to
semi-normal after that (everything working, but the table still extra slow).
Where did that big file come from? My whole db is only 8M, the corrupted
table is only 4M, so does it sound right that a 142M temp file was somehow
generated..?
Odd. Anyway, I'm hoping someone recognizes this problem and can point me
toward the right section of the manual to learn how to fix it. <fingers
crossed that the table is still recoverable...>
Thank you!
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
