Paul J Stevens wrote:
Run it twice to get rid of all deleted messages. If this deletes a lot
of messages you should probably also run
OPTIMIZE_TABLE <tablename>;
for - at least - dbmail_messages and dbmail_messageblks
All of this will take a long time to run.
I've run
dbmail-util -c -t -u -p -d -y
twice and this is what came out:
first time:
------------------------------------------------------------------------------------
Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
Repairing DBMAIL physmessage integrity...
Ok. Found [1] unconnected physmessagesOk. Orphaned physmessages deleted.
Repairing DBMAIL message integrity...
Ok. Found [0] unconnected messages.
Repairing DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
Repairing DBMAIL for NULL messages...
Ok. Found [0] NULL messages.
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
Deleting messages with DELETE status...
Ok. [13051] messages deleted.
Setting DELETE status for deleted messages...
Ok. [10739] messages set for deletion.
Re-calculating used quota for all users...
Ok. Used quota updated for all users.
Vacuuming and optimizing database...
Ok. Database cleaned up.
Maintenance done. No errors found.
------------------------------------------------------------------------------------
second time:
------------------------------------------------------------------------------------
Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
Repairing DBMAIL physmessage integrity...
Ok. Found [0] unconnected physmessages.
Repairing DBMAIL message integrity...
Ok. Found [0] unconnected messages.
Repairing DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
Repairing DBMAIL for NULL messages...
Ok. Found [0] NULL messages.
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
Deleting messages with DELETE status...
Ok. [10739] messages deleted.
Setting DELETE status for deleted messages...
Ok. [0] messages set for deletion.
Re-calculating used quota for all users...
Ok. Used quota updated for all users.
Vacuuming and optimizing database...
Ok. Database cleaned up.
Maintenance done. No errors found.
------------------------------------------------------------------------------------
the I did:
optimize table dbmail_messages:
------------------------------------------------------------------------------------
+------------------------+----------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------------+----------+----------+----------+
| dbmail.dbmail_messages | optimize | status | OK |
+------------------------+----------+----------+----------+
1 row in set (35.71 sec)
------------------------------------------------------------------------------------
and
optimize table dbmail_messageblks:
------------------------------------------------------------------------------------
+---------------------------+----------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+---------------------------+----------+----------+----------+
| dbmail.dbmail_messageblks | optimize | status | OK |
+---------------------------+----------+----------+----------+
1 row in set (14 min 46.35 sec)
------------------------------------------------------------------------------------
All of the above commands took no more than 25 minutes...
Unfortunately there are still a lot of rows in dbmail_messageblks:
mysql> select count(*) from dbmail_messageblks;
+----------+
| count(*) |
+----------+
| 515261 |
+----------+
1 row in set (1 min 11.88 sec)
Everything seems to work fine, but as today is Saturday there is
no high traffic and can't say if thigs have improved or not...
If you say that dbmail_messageblks shouldn't have all those messages,
tell me how I should correct this.
Thanks.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
