"optimize table" is your friend in case you have files per table enabled - before mysql 5.6 the table is locked while rebuild is running - innodb never reclaims space
-------- Ursprüngliche Nachricht -------- Von: Simon <grem...@gmail.com> Gesendet: 19. März 2015 04:21:52 MEZ An: DBMail 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 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 ------------------------------------------------------------------------ _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail -- Reindl Harald (mobile) the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / CISO / Software-Development +43 (676) 40 221 40 http://www.thelounge.net _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
