MySQL has a known "table full" issue when a table reaches 4GB. We thought running 64-bit software we'd be unaffected, but this morning we exceeded the maximum number of rows allowed by a table, and that prevented people from posting. It appears only one post was lost and that person has been notified.
It was corrected by running a backup and then an SQL command:
mysql> ALTER TABLE ibf_posts MAX_ROWS=1000000000 AVG_ROW_LENGTH=3411;
Query OK, 1259009 rows affected, 3 warnings (1 hour 26 min 57.10 sec)
Records: 1259009 Duplicates: 0 Warnings: 0
Thanks for your understanding and patience as we resolved this issue.
Your Geeks to Go admin team