View Single Post
  #6 (permalink)  
Old 01-28-2009, 08:24 PM
fizi fizi is offline
Senior Member
 
Posts: 66
Default

So it looks like all of the database tables were corrupt. This could explain a few things.

I've run repairs on all of them except for 'zimbra_logger.raw_logs' which is still running (been a few hours). It's a 4GB table so I'll give it a little while longer.

The other table I'm having problems with is 'zimbra_logger.mta'. Here is the output I'm getting.

Code:
mysql> check table mta;
+-------------------+-------+----------+-------------------------------------------------------------------+
| Table             | Op    | Msg_type | Msg_text                                                          |
+-------------------+-------+----------+-------------------------------------------------------------------+
| zimbra_logger.mta | check | error    | Table upgrade required. Please do "REPAIR TABLE `mta`" to fix it! |
+-------------------+-------+----------+-------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> REPAIR TABLE `mta`;
+-------------------+--------+----------+--------------------------------------------------------------------------------------+
| Table             | Op     | Msg_type | Msg_text                                                                             |
+-------------------+--------+----------+--------------------------------------------------------------------------------------+
| zimbra_logger.mta | repair | Error    | Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed |
| zimbra_logger.mta | repair | Error    | Table 'mta' is marked as crashed and last (automatic?) repair failed                 |
| zimbra_logger.mta | repair | status   | Table is already up to date                                                          |
+-------------------+--------+----------+--------------------------------------------------------------------------------------+
3 rows in set (0.02 sec)
Reply With Quote