https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #8 from tagwer...@innerjoin.org ---
(In reply to Aaron Williams from comment #7)
> Tracking it down it looks like LMDB is returning MDB_PAGE_NOTFOUND,
> indicating the database is corrupt.
That seems conclusive :-(
I've noticed times where "having to index" a *very* large number of new files
pushed baloo over the edge. At the moment it makes its internal list of files
to index (in memory) and commits only when it's done. That can be a demanding
on memory. I'm suspicious abut whether this works if extending into swap but
could not reproduce the issue though...
Probably a not a problem for you with the amount of RAM you've got available.
Maybe time to dig up a backup and find an earlier
.local/share/baloo
--
You are receiving this mail because:
You are watching all bug changes.
