On 07/25/14 12:45, Richard Fox wrote: > On Fri, 25 Jul 2014, Ken Mandelberg wrote: >> I've >> seen generic mysql postings about ibdata1 expanding because of bad >> transactions and the inability to shrink it. I'm not sure how this fits >> in with Bacula. > > I'm sorry, I can't comment on this part except I understand that you can't > reclaim the disk space used by these files except for anything but innodb > data. That is, when you free up space by truncating or dropping innodb > tables, it frees up space within these files but only MySQL can use it for > new innodb data. It doesn't change their size on disk.
The thing to remember is that the InnoDB tablespace is an embedded filesystem. Just like any other filesystem, it is easy to grow it, but difficult and expensive to compact free space and shrink it. The only tool I am aware of that can, effectively, compact and shrink the InnoDB tablespace file is Percona XtraBackup, and it's not the easiest tool in the world to use. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: 603.293.8485 ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
