kolab_cache_event contact & file huge

[Stelios A.]

Hi Daniel,

Thanks for the reply. I end up doing the following to solve the issue:

I've empty all cache tables (had a backup before that just in case that it
doesn't work) and then I dropped both roundcube and kolab which use innodb
structure.

After that I shutdown mysql and deleted the
ib_logfile0 and ib_logfile1 along with ibdata1.

Then I edit the my.cnf and added:

innodb_file_per_table
innodb_flush_method=O_DIRECT
innodb_log_file_size=1G
innodb_buffer_pool_size=4G

and started again mysql.

Everything worked great and size is minimal now:

root at kolab1:/var/lib/mysql# ls -la
total 2117696
drwx------  7 mysql mysql       4096 Mar  8 09:36 .
drwxr-xr-x 46 root  root        4096 Mar  7 02:40 ..
-rw-r--r--  1 root  root           0 Feb 23 04:38 debian-5.5.flag
-rw-rw----  1 mysql mysql 1073741824 Mar  8 13:44 ib_logfile0
-rw-rw----  1 mysql mysql 1073741824 Mar  8 03:05 ib_logfile1
-rw-rw----  1 mysql mysql   18874368 Mar  8 13:44 ibdata1
drwx------  2 mysql mysql       4096 Mar  7 04:56 kolab
drwx------  2 mysql root        4096 Feb 23 04:38 mysql
-rw-------  1 root  root           6 Feb 23 04:38 mysql_upgrade_info
drwx------  2 mysql mysql       4096 Feb 23 04:38 performance_schema
drwx------  2 mysql mysql       4096 Mar  7 02:40 phpmyadmin
drwx------  2 mysql mysql       4096 Mar  7 04:58 roundcube

Thanks

Stelios


On 7 March 2015 at 12:19, Daniel Hoffend <dh at dotlan.net> wrote:

> nope they have relations to kolab_folders
>
> it's safe to delete stuff from kolab_folders which then descenent to
> delete kolab_cache_*
> but the cache will fill up again at some point.
>
> or use the modcache script
>
> cd /usr/share/roundcubemail/
> plugins/libkolab/bin/modcache.sh clear
>
> ------ Originalnachricht ------
> Von: "Stelios A." <stelios.a at gmail.com>
> An: "users at lists.kolab.org" <users at lists.kolab.org>
> Gesendet: 07.03.2015 08:53:46
> Betreff: kolab_cache_event contact & file huge
>
>
>  Hi all,
>>
>> I've got a huge ibdata1 file under mysql (32G)
>> After checking the tables I've noticed that those that consume that disk
>> space are:
>>
>> kolab_cache_event
>> kolab_cache_contact
>> kolab_cache_file
>> kolab_cache_task
>>
>> Is it safe to empty them?
>>
>> Stelios
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20150308/6b1c4e51/attachment.html>