https://bugs.kde.org/show_bug.cgi?id=481101
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to MarkW from comment #0)
> `baloo_file` should be permanently disabled and the `Enable File Search`
> should not be automagically re-enabled.
There has to be something else messing with it, this is not the usual
behaviour...
If it is disabled it generally stays disabled, and you can see the option in
the
.config/baloofilerc
file as
[Basic Settings]
Indexing-Enabled=false
Keep an eye on this, see if it is being changed back. You could try setting the
config to "read only"...
> 1. `systemctl --user disable kde-baloo.service` doesn't help. It still
> starts up again at reboot.
I'll check to see whether this does anything more than the "balooctl disable".
I think not as it would not set the "indexing-enabled-false"
> 2. Deleting the index after disabling `Enable File Search` makes no
> difference.
No, that would be a purge and you'd start again.
> 3. I need to disable `baloo_file` as my system is using `BTRFS` COW with
> scheduled snapshots enabled. This causes `baloo_file` to re-index every time
> a new snapshot is created, consuming large amounts of CPU and doing a lot of
> fs reads (slowing other opartions down) and performing writes that
> negatively impact SSD wear.
That's interesting. I've not played with that. The question is why Baloo sees
the files as new files.
* Do you see the snapshots "elsewhere" in the filesystem?
* If you do a "stat one-of-your-files.txt", do you see the device number and
inode of the file change (after the snapshot/reboot)?
* If you do a "balooshow one-of-your-files.txt" do you see the DocID change?
(the Id is built from the device number and inode. The way this is done has
recently been changed to avoid reindexing, specifically in the BTRFS case)
* If you do a "baloosearch -i one-of-your-files.txt" do you get a single
result or many?
The "DocId" is the 16 character hex string that comes first in the balooshow
and at the beginning of the line in baloosearch.
--
You are receiving this mail because:
You are watching all bug changes.
