[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-24 Thread Martin Schnitkemper
https://bugs.kde.org/show_bug.cgi?id=333514

--- Comment #7 from Martin Schnitkemper  ---
Thank you for your response, Daniel.  Is it at least safe to delete the content
of the folder after indexing without the risk to lose mails etc?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-24 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=333514

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Daniel Vrátil  ---
Ok, that sounds like a problem caused by our indexer workaround. Simply put:
the indexer will force-load the data every time into Akonadi, so that it can
index them (it's hard to index something you don't have ;-)). It shouldn't be
that aggressive though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-23 Thread Martin Schnitkemper
https://bugs.kde.org/show_bug.cgi?id=333514

Martin Schnitkemper  changed:

   What|Removed |Added

 CC||martin.schnitkemper@nexgo.d
   ||e

--- Comment #5 from Martin Schnitkemper  ---
I confirm that problem.  Folder has currently a size of over 1 GB and 5100+
files.  Problem started after upgrading to kde-4.13 and the introduction of the
baloo indexer.  After the initial indexing the folder grew to this size. 
Sometimes the files vanish after a few days (not 1 minute as stated in the
folder properties) but come back after any search.  I would like to get rid of
it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-23 Thread Markus
https://bugs.kde.org/show_bug.cgi?id=333514

--- Comment #4 from Markus  ---
EnableCleaner is not set at all in ~/.config/akonadi/akonadiserverrc .

Is there a way to start this cleaner manually?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-23 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=333514

Daniel Vrátil  changed:

   What|Removed |Added

Version|4.13|1.12.1

--- Comment #3 from Daniel Vrátil  ---
To clarify:
- "keep locally" is relative to "Akonadi server", not the actual storage.
- data are always initially imported into Akonadi (necessary for various
reasons), but if the cache expiration policy is activated, they should be
removed from Akonadi and ~/.local/share/akonadi/file_db_data again after some
period of time.

Just to make sure: please check that in ~/.config/akonadi/akonadiserverrc,
EnableCleaner is set to True (or is not set at all). If it is set to False,
stop Akonadi, remove the line and start Akonadi again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-22 Thread Markus
https://bugs.kde.org/show_bug.cgi?id=333514

Markus  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WORKSFORME  |---

--- Comment #2 from Markus  ---
I already have that option set as you described it.
So if that should help, it seems to be broken. (Akonadi 1.12.1)

(And "keep locally"... they are always locally in ~/.local/share/local-mail!)

I already made a complete backup, stopped akonadi and removed akonadis files
and dbs... it was rebuilding it completly for every mail! (I did not open any
mail in kmail!) The cache was nearly as big as before. And did not shrink after
some time (hours without hdd activity).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 333514] akonadi file_db_data grows too big

2014-04-22 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=333514

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@redhat.com
  Component|general |server
 Resolution|--- |WORKSFORME

--- Comment #1 from Daniel Vrátil  ---
You can specify cache expiration policy for each folder (or for entire folder
tree) by right-clicking a folder, and opening Folder Properties -> Retrieval. 
Then check "Retrieve message bodies on demand" and set "Keep message bodies
locally for" to 1 minute.

This will cause that every email in that folder and all it's subfolders will be
removed from Akonadi cache after 1 minute and it will be loaded again on-demand
from ~/.local/share/local-mail when you try to open it. Note that after you set
this option, the initial "cleanup" will take some time (and disk activity).

Because the cache expiration policy pretty much covers your original request,
I'm closing this as WORKSFORME. However if the approach above does not work
(disk space is not reclaimed within ~30 minutes), feel free to reopen (or open
a new bug about cache expiration being broken) and provide Akonadi server
version (akonadictl --version).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs