https://bugs.kde.org/show_bug.cgi?id=438434
Bug ID: 438434
Summary: Baloo appears to be indexing twice the number of files
than are actually in my home directory
Product: frameworks-baloo
Version: 5.82.0
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: stefan.bru...@rwth-aachen.de
Reporter: mar...@lichtvoll.de
CC: baloo-bugs-n...@kde.org, n...@kde.org
Target Milestone: ---
SUMMARY
After I thought Baloo completed the initial indexing run on my new laptop, I
copied over my home directory and purged the Baloo database, it appeared to
just index all of those files again
STEPS TO REPRODUCE
I have no idea.
OBSERVED RESULT
With "balooctl monitor" I saw that Baloo indexes files it must have seen during
the first indexing run.
% balooctl status
Die Baloo-Dateiindizierung läuft
Indizierungsstatus: Indexing file content
Gesamtzahl der indizierten Dateien: 1.102.793
Dateien, die noch indiziert werden: 260.161
Dateien, deren Indizierung fehlgeschlagen ist: 0
Der aktuelle Index hat eine Größe von 7,27 GiB
EXPECTED RESULT
But I only have:
find . -not -path '*/\.*' | wc -l
580550
Please never ever index the same files again unless their contents actually
changed.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Devuan Ceres with KDE packages from Debian Experimental
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.8.2
Qt Version: 5.15.2
ADDITIONAL INFORMATION
"/home" is on a single BTRFS filesystem which is located in top of an LVM on
top of a LUKS encrypted partition.
In case this again is something to do with a changing identification of the
filesystem, please add an option to tell Baloo: "My $HOME is my $HOME, it is
always the same filesystem. Do not ever re-index anything on it, unless it has
changed. Thanks."
Actually this should be the default. There is no reason whatsoever to assume
that $HOME on an usual desktop PC or laptop will at one point be a completely
different filesystem with completely different contain. It should be the
default that $HOME is *not* on a removeable device.
Baloo and Akonadi Search managed to somewhat bog down even my new ThinkPad T14
with 8-core AMD Ryzen 7 PRO 4750U and a 2 TiB Samsung 980 Pro. That is just not
right. This machine is ridiculously and still that search thing the machine be
on quite a load for hours and hours and hours to come. There is something
definitely not right here.
--
You are receiving this mail because:
You are watching all bug changes.
