Quoting Kishore Jalleda ([EMAIL PROTECTED]): > That usually means the table is corrupt beyond repair and nothing is really > fixing it or there is something one cannot easily comprehend ( this usually > happens with inconsistency among deleted records and some kind of mismatch > that occurs) -----anyway what I would really advice in this case is to > rebuild the table from a working/clean backup and start-over, if this is a > slave then thats very easy to do, if not it depends on your latest clean > backup available ..
Amazing. Amazing that even the tools can't tell me it's unfixable. I mean, i tried everything. :) I'll restore the databases from the master (this isn't a slave, but it's a machine i want to switch to when it finally becomes stable...) and see where we get from that... The machine didn't crash. Nor did mysql. Any clue what might cause this to happen? Disk looks fine too, no read or write errors whatsoever... Thanks, Sander. -- | Just remember -- if the world didn't suck, we would all fall off. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
