https://bugs.kde.org/show_bug.cgi?id=498876
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to A. D. Cramer from comment #0)
> 1. Copy the entire /home directory to a folder on a different drive.
> 2. Make the main partition on that drive mount as /home, moving some
> directories around to make this feasible
You are reindexing everything... If you've copied to a different drive the
files will have a different FilesystemID/inode and Baloo will consider them
"new".
> Here is the output of balooctl6 status:
> Baloo File Indexer is running
> Indexer state: Indexing file content
> Total files indexed: 5,551,335
> Files waiting for content indexing: 1,568,892
You've got a lot of files, Baloo is working through them.
All the same, it would be best to delete the index and start again (pkill
baloo_file; balooctl6 purge), Baloo is remembering everything it indexed on its
"old" disc. You don't need that and it will make the indexing slower and more
disk and RAM intensive. The index file itself if pretty large...
> ...and balooctl6 running for one minute
> Press ctrl+c to stop monitoring
> File indexer is running
> Indexing file content
> : Ok
> - 358 repeating lines removed for brevity -
> : Ok
> ^C
Could be you've got loads of code in your $HOME. The monitor is not so good at
telling the Baloo has looked at a file and decided it's on the mimetype
exclusion list.
--
You are receiving this mail because:
You are watching all bug changes.
