https://bugs.kde.org/show_bug.cgi?id=449102
Bug ID: 449102
Summary: baloo is re-indexing all /home files whereas the files
did not change.
Product: frameworks-baloo
Version: 5.88.0
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: i...@free.fr
Target Milestone: ---
SUMMARY
***
I'm not sure its a bug. I did rsync my old /home to a new disk, and since,
baloo is re-indexing same files again and again with messages like this:
" id seems to have changed. Perhaps baloo was not running, and this file was
deleted + re-created".
But the files didn't changed since the last indexing. I'm wondering if its not
because rsync did create files with time attributes that maybe disrupts baloo
algorithm. The files created with rsync have modified time attributes that are
prior to creation time. An example:
# LANG=C stat 801\ 001.jpg
File: 801 001.jpg
Size: 1923181 Blocks: 3760 IO Block: 4096 regular file
Device: 10305h/66309d Inode: 110231652 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1026/ mathieu) Gid: ( 100/ users)
Access: 2022-01-07 02:04:30.899118806 +0100
Modify: 2011-08-12 00:33:58.000000000 +0200
Change: 2022-01-07 02:04:30.918118365 +0100
Birth: 2022-01-07 02:04:30.899118806 +0100
That file has been modified in 2011, and was created by rsync in 2022.
***
STEPS TO REPRODUCE
1. rsync your /home directory to a new disk
2. use the new disk as your /home
3. delete baloo settings and baloo index
4. let baloo index all your content as new content
OBSERVED RESULT
next time baloo will start, he will reindex everything with "id seems to have
changed" messages.
EXPECTED RESULT
baloo should index files that are not modified only once.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.16/5.88.0
(available in About System)
KDE Plasma Version: 5.88.0
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
ext4 filesystem
--
You are receiving this mail because:
You are watching all bug changes.
