Re: Akonadi cache size 5 times too large with Kontact kolab_resource

Martin Steigerwald <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Organization Proact Deutschland GmbH
Message-ID <77468788.lTgqNC1tvC@merkaba>
Bernhard Reiter - 31.01.19, 15:36:
> Am Donnerstag 31 Januar 2019 14:52:24 schrieb Martin Steigerwald:
> > Older versions of Akonadi leaked files. "akonadictl fsck" would move
> > those to the files lost+found directory, which you can empty afterwards.
> 
> Martin, thanks for the response!
> 
> I did run "akonadictl fsck", but I did not know about cleaning out
> the lost+found directory manually. There was a lot of output of the command,
> which I did not check line by line. So now I cannot say.
> 
> Maybe an entry in one of the prominent Akonadi trouble shooting lists/wikis
> can be improved to have this information.
> 
> See one other thread were users thought that "vacuum" would clean entries
> out. https://forum.kde.org/viewtopic.php?t=125009

I am not entirely sure anymore, but I thought `akonadictl vacuum` just removed 
unused entries from MySQL tables, while `akonadictl fsck` would check whether 
all external payloads (i.e. files) are still referenced by the database.

Ciao,
-- 
Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.