Summary: | DATA LOSS - Nepomuk eats disk space and kde freezes/crashes | ||
---|---|---|---|
Product: | nepomuk | Reporter: | Matthias Gies <matthiasgies> |
Component: | fileindexer | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Matthias Gies
2012-02-08 18:33:28 UTC
I found some hint, maybe. Today I went to /home/matthias/.kde/share/ to remove all nepomuk related files to reset it again. I looked a little closer, to see where the space of 149G was wasted. Turned out the file /home/matthias/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log consumes all of it. My actual index db /home/matthias/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.db only has 2.5G. Something wrong here? Also I found that all these files exist a second time in /home/matthias/.kde/share/apps/nepomuk/repository/main/soprano-virtuoso.* but are either empty or consume only 2-8M. So what's the deal with the logfile consuming 149G? So, I have reset the whole thing by deleting all nepomuk folders and cfgs in my home-dir. After logging back in, nepomuk is configured with defaults, strigi turned off. Logfile contains nothing, only after another reboot contains following message: Thu Feb 09 2012 11:59:02 Unable to remove /home/matthias/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.lck (No such file or directory) The 149G logfile I couldn't open due to it's size. I'll keep an eye on this. If nothing happens after few days of leaving the pc inactive at night, I'll turn on strigi again, to see if that's the source for infinite log-spam. What I already noticed though: when I had strigi activated, dolphin used to return bogus search results. Now, after resetting and having nepomuk run without strigi, dolphin returns accurate results, even about file contents. Leads me to the question: why does the systemsettings module for nepomuk tell me, that I need strigi to search contents of files, if nepomuk itself already seems to do that? *** This bug has been marked as a duplicate of bug 264465 *** |