----- Original Message ----- > From: "Suresh Kuna" <sureshkumar...@gmail.com> > > The permanent solution is to convert the table into Innodb engine.
Wonderful advice, especially without even bothering to try and find out what is actually causing the corruption. Well done, that man. You *are* aware that not all tables can be converted to InnoDB? Full text indices come to mind, for one. One way of establishing wether or not the table is on a bad block (it probably isn't, or you'd see something in the syslog) would be to ensure it goes on a completely different set of blocks: create an identical table with a different name, copy the contents with insert as select, and then swap out the tables using alter table rename. The "old" table will remain on the blocks it is, and the new one will have all the content on "fresh" blocks. Note that a repair table is also very likely to already have copied the entire table using roughly the same process, so that's probably not it; but it may be worth a shot anyway. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
