Somehow managed to crash perch2_content_index

Was wondering if anyone else had a problem where the perch2_content_index table becomes corrupted and is marked as 'crashed', thereby making perch_content_custom() return 0 results. I'm not quite sure what was going on (it might have just been a permissions issue on my machine, but I don't think so…). myisamchk reported something like 9 requests that hadn't exited cleanly.

I was able to repair the table and perch_content_custom() works as expected again. I was basically just wondering if 1) anyone else had seen this before and 2) if there were any steps I could take to mitigate this in the future.

Cheers, Michael