About 3 weeks ago, the POST table went corrupt with:
mysql error: Got error 127 from table handler
mysql error number: 1030
The specific errors vary. I repaired the table via mysqlcheck. Since then, every day, the same error occurs and the same table goes corrupt at least once a day. I've been repairing it daily, but it keeps corrupting. I shut down the DB yesterday and ran myisamchk on the index files of the post.myi but just a few minutes ago the errors began. Most of the time, the errors go away on their own, however, other times, users are no longer able to post and get DB errors diplayed. A few times, the postindex table corrupted as well. As far as I know, NOTHING changed to the system when the errors starting happening. I've been running vB 3.0.7 w/ mySQL 4.0.16 for some time now without a hiccup and now this. It's a dedicated Windows server and I have full control of it. The DB is maybe 700mb.
Can anyone assist with what may be happening here? I read about the bug in mySQL 4.0.12, but that's not the version I'm running and as I mentioned, I've been running 4.0.16 for a VERY long time without issues. TIA!!
mysql error: Got error 127 from table handler
mysql error number: 1030
The specific errors vary. I repaired the table via mysqlcheck. Since then, every day, the same error occurs and the same table goes corrupt at least once a day. I've been repairing it daily, but it keeps corrupting. I shut down the DB yesterday and ran myisamchk on the index files of the post.myi but just a few minutes ago the errors began. Most of the time, the errors go away on their own, however, other times, users are no longer able to post and get DB errors diplayed. A few times, the postindex table corrupted as well. As far as I know, NOTHING changed to the system when the errors starting happening. I've been running vB 3.0.7 w/ mySQL 4.0.16 for some time now without a hiccup and now this. It's a dedicated Windows server and I have full control of it. The DB is maybe 700mb.
Can anyone assist with what may be happening here? I read about the bug in mySQL 4.0.12, but that's not the version I'm running and as I mentioned, I've been running 4.0.16 for a VERY long time without issues. TIA!!
Comment