On 19-03-15 21:16, Simon wrote:
What im trying to understand is why is the SUM of curmail_size is
approx 110GB, yet the database size (even dump'ed) is 400GB. Surely
dbmail does not have that much overhead in its database?
As Reindl stated, why still use dbmail 2.2 without the
Am 19.03.2015 um 10:13 schrieb Casper Langemeijer:
On 19-03-15 04:21, Simon wrote:
If the later, I would really appreciate some pointers to deal with
reclaiming the space...?
As others suggested, optimize table (or the mysqloptimize command line
utility) can help you 'reclaim' space.
But
On 19-03-15 04:21, Simon wrote:
If the later, I would really appreciate some pointers to deal with
reclaiming the space...?
As others suggested, optimize table (or the mysqloptimize command line
utility) can help you 'reclaim' space.
But you shouldn't use it unless you really need to
mailinglist dbmail@dbmail.org
Betreff: [Dbmail] curmail_size vs innodb disk usage
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
Am 19.03.2015 um 04:21 schrieb Simon:
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..
On Thu, Mar 19, 2015 at 10:27 PM, Reindl Harald h.rei...@thelounge.net
wrote:
1. Optimize table rewrites the entire table into a new file. This means
you'll need about 110G-150G of storage space to be able to perform this
action in the first place
sadly yes, maybe it's too late
I can
Am 19.03.2015 um 21:16 schrieb Simon:
What im trying to understand is why is the SUM of curmail_size is approx
110GB, yet the database size (even dump'ed) is 400GB. Surely dbmail does
not have that much overhead in its database?
mailsize has barely to do with database size
completly different
On Fri, Mar 20, 2015 at 9:31 AM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 19.03.2015 um 21:16 schrieb Simon:
What im trying to understand is why is the SUM of curmail_size is approx
110GB, yet the database size (even dump'ed) is 400GB. Surely dbmail does
not have that much overhead in
Am 19.03.2015 um 21:54 schrieb Simon:
On Fri, Mar 20, 2015 at 9:31 AM, Reindl Harald wrote:
Am 19.03.2015 um 21:16 schrieb Simon:
What im trying to understand is why is the SUM of curmail_size
is approx
110GB, yet the database size (even dump'ed) is 400GB. Surely
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
10 matches
Mail list logo
