https://bugs.kde.org/show_bug.cgi?id=474973
Stefan Brüns <stefan.bru...@rwth-aachen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefan.bruens@rwth-aachen.d
| |e
See Also| |https://bugs.kde.org/show_b
| |ug.cgi?id=477068
--- Comment #31 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
(In reply to tagwerk19 from comment #27)
> Maybe I'm a step further. I have a system where I see the same behaviour,
> something I consider a remarkable step forward 8-/
>
> Bad news is it's a "bashed about" Neon Unstable, not something I can
> reproduceably rebuild. Further bad news is that if I leave the configuration
> and test files untouched, do a "balooctl6 purge" and reindex, the behaviour
> goes away.
>
> That would help explain why the issue is so slippery. It also means that
> when you have the issue, copy your .local/share/baloo/index somewhere safe
> so you can go back to it.
>
> It's also quite possible that this is one cause of the problem rather then
> "the" cause, but what I see is:
>
> $ baloosearch -i test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba610000fc01 /home/test/testfiles
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.297092 msecs
>
> [...]
>
> $ baloosearch -i test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.410179 msecs
>
> $ baloosearch -i -d /home/test/testfiles test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.307979 msecs
>
> The index has two records for the /home/test/testfiles folder with different
> DocIDs and the "test.txt" file was created with the new format DocID and it
> was not found in the search. After the reindex, it was found.
("WARNING: term points to unknown document 5698695752383489 (/???)" - that is
143eef0000fc01 in hex, so it points to the same problem)
@tagwerk19 Thanks for investigating this.
I think the conclusion this is caused by the change of the FSID generation
(https://invent.kde.org/frameworks/baloo/-/merge_requests/131) is spot on, and
shows that the MR is missing the required safety measures. (Although the MR
mentioned this problem explicitly.)
The change was obviously not tested and analyzed for possible side effect. But
my reservations were unfortunately just ignored, and the change merged
nevertheless, without prior notice (24 minutes from removing the Draft status,
"resolving" all comments and merging it).
After the change, the DB contents are semantically garbage, and the DB has to
be purged (You have noticed this before, I know). This should have been done
automatically, but nobody implemented it. Nobody announced the breakage to the
broader public.
--
You are receiving this mail because:
You are watching all bug changes.
