When using Clustering with ezdbfile eZ Publish adds an enormous amount of trashed-data with recursive trashed-directories
into ezdbfile, e.g. var/ezwebin_site/storage/images/.../trashed/trashed/trashed/trashed/..._medium.jpg
Although the website is only about 250 MB of size, ezdbfile_data contained over 2 GB of data in trashed-directories
within one week. The problem is that InnoDB-files never shrink, so you will run into storage-problems sooner or later.

Temporary solution:
delete from ezdbfile_data where name_hash in (select name_hash from ezdbfile where name like "%/trashed/%");
delete from ezdbfile where name like "%/trashed/%";
Dump whole database, delete the InnoDB-files manually, initialise MySQL, recreate database and import.

Steps to reproduce

Use ezdbfile
Delete objects within CMS