Description of problem: I don't know if soprano is the correct components, however several times the file ~/.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log has become *very* huge, in fact over 12GB. The added content is rather boring: 12:06:37 Reference to page with free remap dp = 1188, remap = 1188 (with the timestamp changing of course). The line is repeated 180806 times each second, so the file grows *fast*. This is good for file server benchmarks or something similar, however a disaster for file server performance and backup applications. I have my doubts in the value of such logging, please consider to disable it. Thanks in advance. Versions; soprano-2.6.0-2.fc15.x86_64
Oops, looks like we missed disabling some debug output, fixed soprano-2.6.0-3 builds on the way...
Secondarily, those errors you see seem to be coming from soprano's virtuoso-opensource db backend. One initial guess would be that your db is corrupted somehow, especially if this same ~/.kde was imported from previous versions of fedora/kde. I'm looking into implementing some sort of log rate-limiting, but in the meantime, you might want to consider renaming/backup anything that matches ~/.kde/share/apps/nepomuk/ ~/.kde/share/config/nepomuk* preferably when not logged into kde or at least when nepomuk is enabled and running, and then restarting your kde session.
Fwiw, here's the feedback I got from upstream virtuoso-opensource-users mailing list: We're looking into reducing log output in case of these repeated messages. The fix is currently scheduled for VOS 6.1.4 ... The message itself may indicate database corruption. If you receive a lot of them, it is time to either regenerate, restore from backup, or, as a last resort, perform a crash dump/restore on the db, as documented in http://docs.openlinksw.com/virtuoso/backup.html
soprano-2.6.0-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/soprano-2.6.0-3.fc15
soprano-2.7.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/soprano-2.7.2-1.fc16
soprano-2.7.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
virtuoso-opensource-6.1.4-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/virtuoso-opensource-6.1.4-2.fc16
virtuoso-opensource-6.1.4-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/virtuoso-opensource-6.1.4-2.fc15
Package virtuoso-opensource-6.1.4-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virtuoso-opensource-6.1.4-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15428 then log in and leave karma (feedback).
virtuoso-opensource-6.1.4-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/virtuoso-opensource-6.1.4-2.fc14
soprano-2.6.0-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
virtuoso-opensource-6.1.4-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
virtuoso-opensource-6.1.4-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
virtuoso-opensource-6.1.4-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.