Re: curmail_size vs innodb disk usage

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..
> 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
> 
Hi.
Not an expert on mysql, but on postgres you run vacuumdb to reclaim
space. A quick search gave me this:

http://dev.mysql.com/doc/refman/5.1/en/optimize-table.html

Should be about what you need, but I am sure the mysql/mariadb users can
help you more on that if needed.

Regards,
  Thomas R

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJVCoBOAAoJEM5rhUtKyvU6lqUP/ihAH569MS30upl03DSfkIkQ
cTqZa6GjudNphDUuGWMrVsGwxphfKy0bWRRJy+kRNpHqmoZ9OZaC4GzOumJ43IDq
s4wiEjBV8zBWA6GnlFdlC4fDtLXpWowSJRGrSXPSOsIaGp9G9P3+SAFdrY2aPPs5
9OAb2OMs1VHt4p/b6Pm2du5ZMgVdiGtjoWIazxBX8CTnEi/tO0Xtnyilm3ziWsnY
IT9Qrkuub0wx47R2FcMEBA7FAbdJA7BzRjlTM5V2mzHF+ZjiATiWbjWNO+Xpds4z
J7+WftoZx7gNB+FZWvNEO27m2KBHQUDwWuuftYy7Ymej34k3UH0yGd6Ua08jLij+
Cyj8v35F71jHSZTBWKQZSLRzR4l7oFDpbQaeOfJMznJPflxNrHybS5G0W5v8yeXd
h8oHuJ0+hKwuONOPFMdxZxOc9I7DXq2QEV5RY+CEK8hWs7DJp1PjMfuq3QMlIemH
1hSFIrEgv/54lzwrBQhZCNYV/RLPUMb/IXPsNIVOAooqA0pj5T2sR6bqvvQK3PBP
U9tNf5fbcG0laAJ5pVhGCSO6hBOVWfboLq36P45hpM3YPAwmtMzo4yThzULneBnx
JzJYZ2rTcWMZ1mDUdz59ie7GTBJcONbpbGkg9MBz8nLJhrn5VVrb6ZH4f51w4alG
lq4ZttUtFXyV8T458aQI
=nrU7
-----END PGP SIGNATURE-----