Weird and damaging SQL event - my vb_post table just randomly emptied!

[moonclamp]

Earlier on my site was running very strangely - I kept getting the following SQL error on the forum index and a couple of other pages:

MySQL Error : Got error 12 from storage engine Error Number : 1030
Date : Monday, August 13th 2007 @ 08:03:00 PM

Not being too sure what it was I decided to repair/optimise the tables. There was another db outage in the middle of the optimisation. There were a few like this, a couple of them actually killed phpMyadmin for a while.

When the site eventually came back to life, none of my threads had any posts - I checked the vb_post table and it was empty :eek:

"MySQL returned an empty result set (i.e. zero rows). (Query took 0.0002 sec)"

Can anyone shed any light on what happened? Are all 287000+ posts just gone in the twinkling of an eye? Or are they just moved to somewhere my forum can't find them?

Can they be retrieved? :confused:

[Eikinskjaldi]

Error 12 means the OS was unable to allocate enough memory. What OS are you running, which storage engine are you using, what kind of plan are you on (shared, vps, dedicated).

I think it likely that your posts are gone, but it could instead be a really, really corrupted index file. The best way to check is to look at the file directly. Assuming you are on some kind of vanilla linux and have root access, as root type ls -l /var/lib/mysql/<your db name>/vb_post.*

If you don't have root access or are not using myisam, this will not work.

[moonclamp]

Shared linux hosting, not sure what flavour of linux though - got cpanel and sadly no root access.

[Eikinskjaldi]

Think you are stuffed mate. Even if you have a backup, there is no guarantee it wont happen again. I'd be moving hosts.

[Marco van Herwaarden]

If the current post table really don't have any rows in it anymore, then you will need to revert to a backup.

Trying to repair the tables while you receive an error 12 is probably the cause of it being emptied.

Please contact your host for the options to repair this and prevent it from happening in the future.

[moonclamp]

yeah looks like it's time to restore from a backup - I'm kicking myself now for not making them a bit more regularly.

Ah well, you live and learn (sometimes)

[deezelpope]

Damn...Poor guy!:( I feel your pain, Moonclamp! I thought I had lost my entire board last week! A nice guy from here, ZomgStuff, helped me fix it.

Good luck to you.

[moonclamp]

I changed my mind about the backup.

My last one was a bit too old (I'd been lazy) so sent out a mass email saying we needed to work together to get back to how we were.

Anyway, in less than 12 hours we've had 120 new threads and almost 900 new posts - and the atmosphere had been better than it has for a long time - I'm almost grateful it went wrong. :)

(Good job it wasn't the memberlist that broke though)

[Dismounted]

If you're too lazy to backup, just set a cron to backup into a file. It's the "Set & Forget" way :).