Forum Moderators: phranque
I'm running an Invision forum (1.3), with PHP 4.3.3 Apache 1.3.28 and MySQL 4.0.15.
This morning I awoke to a MySQL error on a table (8 hours later! ugh!). This isn't the first time, although it's been a while since the last one. I did a MySQL REPAIR on the table and it brought it back up.
It turns out this error last occurred immediately after (or during) a run of the mill MySQLDump of the database. Related?
I have two questions:
1. Is there a relationship between doing a MySQLDump and getting a corrupted table?
2. IMPORTANTLY: Is there a script around that I can set up that checks for errors and then automatically repairs the tables? I was just reading about MYISAMCHK and checks for errors and repairs them. Does it work? Can someone help me set up a script that runs every so often to check? Does it really use the resources heavily so I can't have it run very often?
I just did another MySQLDump and got another error after that. I just don't get it. The MySQLDump seems to work fine. Then, when I get back into my forum, I get an error, and only on my biggest table. This time the error referenced an index associated with that table.
Is there something wrong with MySQLDUMP? Maybe there is, since I also noticed that a forum topic got posted incompletely about the time I got the error. Coincidence? I'll bet not. Maybe MySQLDUMP should not be run when the forum is active, although I'm not really worred about an incomplete backup so much as generating errors.
Is there a better command I should use to backup? Maybe that is it?
