https://bugs.kde.org/show_bug.cgi?id=449102
--- Comment #5 from tagwer...@innerjoin.org ---
(In reply to iten from comment #4)
> ... added "first run=true" ...
Good news that it has stopped reindexing.
I've never managed to get the "first run" option to behave as I think it "ought
to" but here setting to true could explain the reindexing.
It's perhaps worth thinking that baloo does a "quick" scan to make a list of
what it needs to content index. The indexing itself then happens "slowly", as
you see, 40 files in a batch. If you've got 1.5TB, that could be a long job.
It's possible you are seeing "reindexing" still running, some days after your
rsync (and it does not matter if you've closed down and restarted in the
middle, Baloo keeps the list of what it has to do in its index)
If we want to dig further, we'd need to know if rsync generates an "iNotify"
notification when looking at a file, even it if does not overwrite it. My
suspicion is that if baloo sees an iNotify notification, it reindexes the file
even if the modification time has not changed. I can do something like:
touch -a -m -t 201108120033.58 "801 001.jpg"
that opens the file but does not change it and then resets the access and
modifications times to your 2011 date; baloo reindexes the file after the
"touch". It's a cautious approach...
--
You are receiving this mail because:
You are watching all bug changes.
