At our company we keep our home directories on NFS. When i recently tried KDE again (4. i noticed that first Nepomuk was useing all my cpu, and 2nd filling up my fs quota within a few minutes (seemed to be virtuoso log files with sizes of multiple GB), but since my quota was used up system was dead and only way to recover was to have the admin delete all those logs. he told me he deleted more than 6GB from .kde4/share/apps/nepomuk/repository/main/data/virtuosobackend directory.

This definitely does not look like a wanted behavior.

quaiky wrote:At our company we keep our home directories on NFS. When i recently tried KDE again (4. i noticed that first Nepomuk was useing all my cpu, and 2nd filling up my fs quota within a few minutes (seemed to be virtuoso log files with sizes of multiple GB), but since my quota was used up system was dead and only way to recover was to have the admin delete all those logs. he told me he deleted more than 6GB from .kde4/share/apps/nepomuk/repository/main/data/virtuosobackend directory.

This definitely does not look like a wanted behavior.

You can limit indexed directories in Nepomuk's entry in "Configure Desktop". If your storage is big, and you have many files, Nepomuk's database will be big.

what version of KDE? over time there have been many changes to Nepomuk.

did you look at the head and tail of the log files to see if virtuoso was finding errors?
the commands head and tail run in Konsole on a file will, by default, show the first and last 10 lines in a file - to increase this numbe use the -n option

Code: Select all

head -n 20 filename
tail -n 20 filename

kde version is 4.8.1. no i did not check the file contents but guess i could enable nepomuk again sometime when i am less busy to check it.