Hi There,
We are using dbmail (2.2.18) on debian with a (separate) mysql 5.1 backend
(master/slave with innodb_file_per_table enabled). We use innobackupex for
nightly backups.
Currently a SUM(curmail_size) of all mailboxes gives us about 110GB.. yet
our dbmail_messageblks.ibd file is nearly 500GB and the mysql data space is
just about full.
Is this something that dbmail is not reporting correctly "curmail_size" or
is this just innodb (e.g. does not reclaim the space).
If the later, I would really appreciate some pointers to deal with
reclaiming the space...?
Many thanks,
Simon
We are using dbmail (2.2.18) on debian with a (separate) mysql 5.1 backend
(master/slave with innodb_file_per_table enabled). We use innobackupex for
nightly backups.
Currently a SUM(curmail_size) of all mailboxes gives us about 110GB.. yet
our dbmail_messageblks.ibd file is nearly 500GB and the mysql data space is
just about full.
Is this something that dbmail is not reporting correctly "curmail_size" or
is this just innodb (e.g. does not reclaim the space).
If the later, I would really appreciate some pointers to deal with
reclaiming the space...?
Many thanks,
Simon