https://bugs.kde.org/show_bug.cgi?id=493364
--- Comment #2 from [email protected] --- (In reply to tagwerk19 from comment #1) > There's a very good chance that Baloo is reindexing everything. There's was a > patch to fix issues with BTRFS, sometime over a year back: Using EXT4 partitions > You might be indexing a *load* of files you don't want to, everything under > .cache for example. Have a look at Bug 434705. That is why i turned off content > Did you start with indexing content and then switch to no content? Baloo > might have make itself a list of files it needed to index before that change. yes, i suspect the same > Baloo might have make itself a list of files it needed to index before that > change. when i hit play and it started to run is shows alot of files going by then stopped on this one, it should not be hanging on such a small file regardless of what it is doing ----- $cat -v /path/to/file B B ^@^@^@^@^@^@^FM-M ----- well i think this is a contributing factor (note this drive is 1TB 7200RPM HDD) $ls -lah .local/share/baloo/ total 5.4G drwxrwxr-x 2 chad chad 4.0K Sep 19 11:22 . drwxrwxr-x 62 chad chad 4.0K Sep 19 11:55 .. -rw-rw-r-- 1 chad chad 5.4G Sep 19 11:33 index -rw-rw-r-- 1 chad chad 8.0K Sep 19 11:58 index-lock maybe there should be a max index size setting or something i did notice on other thing, but i feel that would fall under feature request, will make a separate issue for that -- You are receiving this mail because: You are watching all bug changes.
