BINLOG and Corrupt Tables

  • i used Nuke to delete 30,000 orders (not at one time) and i ended up with a DB CONNECTION ERROR. It seems my disk space ran out. I am hosting WordPress on AWS EC2 instance and had to increase my virtual disk to 30GB to get it restarted. The MySQL/data folder is now filled with MySQL BINLOG files (~17GB).

    Also, the wp_comments table is now corrupt i get an error 

    [Table './bitnami_wordpress/wp_comments' is marked as crashed
 and shouldbe repaired]

    Have you ever seen either of these issues before?

    • This topic was modified 5 years, 3 months ago by shackbill.
Viewing 1 replies (of 1 total)
  • Thread Starter shackbill

    (@shackbill)

    Yup this is definitely the culprit – at least on this install. I was able to clean out all the Binlog files and get this working again. After a few rounds of Nuking, im back to about 8GB of these BinLog files. Also, i was able to fix the crashed tables using phpMyAdmin. I’d say beware of using this utility…

Viewing 1 replies (of 1 total)
  • The topic ‘BINLOG and Corrupt Tables’ is closed to new replies.