The default behaviour of mysql is to store all innodb tables in a single file/tablespace. This file does not shrink when rows, tables or schemas are removed making it impossible to reclaim space when a virtual host is removed.
I believe this also makes it impossible for virtualmin to correctly report the size of a virtual hosts database if it uses innodb tables.
See http://code.openark.org/blog/mysql/reasons-to-use-innodb_file_per_table for an explanation.
I know this isn't strictly a virtualmin issue, but i think it has enough potential impact to warrant setting this when installing virtualmin or checking the system config. Also its worth noting that this setting may not be optimal for systems that are intended for use primarily as a database server, but thats not likely to be a server setup with Virtualmin.
Comments
Submitted by JamieCameron on Tue, 11/10/2009 - 14:43 Comment #1
That's a good suggestion .. although most apps virtualmin installs don't create innodb tables, it makes sense to put them in separate files anyway so that quota enforcement works.
I will update the installer to set this up by default.
Submitted by Issues on Thu, 11/26/2009 - 17:20 Comment #2
Automatically closed -- issue fixed for 2 weeks with no activity.