https://bugs.kde.org/show_bug.cgi?id=455179
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #2 from tagwer...@innerjoin.org ---
Somewhere along the line, someone would have recommended deleting the index and
starting again from scratch. Quite often by saying to try "balooctl purge"
There *are* still instances of MDB_BAD_TXN reported but thankfully far, far
fewer than a couple of years back. It's a report from LMDB library and suggests
a corruption of the index. The "markFailed" seen in the dump should generate a
"Not able to commit to DB, DB likely is in a bad state. Exiting" failure - but
the process crashes first.
You are on Arch, do you have it set up using BTRFS?
If so, there's a test you can do that might give a hint (baloo can struggle
with BTRFS and multiple subvols), see:
https://bugs.kde.org/show_bug.cgi?id=402154#c12
If you are running into this, baloo will be reindexing your files after each
reboot (not fully reindexing every time, but will be thinking it has 8 to 10
different discs that appear and disappear again and it needs to do a lot of
"catching up"). This can make the index, and memory usage, pretty large...
--
You are receiving this mail because:
You are watching all bug changes.
