https://bugs.kde.org/show_bug.cgi?id=467865
gerrit.huebb...@gmail.com changed:
What|Removed |Added
CC||gerrit.huebb...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #12 from Aaron Williams ---
I'm not entirely sure it's PDFs. Unfortunately when I get a stack trace it
doesn't report the file that it died on. In the monitor I see it failing even
on some html files.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #11 from tagwer...@innerjoin.org ---
(In reply to Aaron Williams from comment #9)
> ... I am getting this error again when it hits certain files like some of the
> large PDF documents I have...
I have seen trouble with a PDF generated by:
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #10 from Aaron Williams ---
I also have not backed up the index file. It typically quickly grows fairly
large so I specifically do not back it up with my backup system.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #9 from Aaron Williams ---
I reset the index. It looks like the database became corrupted. Even after
recreating the database, I am getting this error again when it hits certain
files like some of the large PDF documents I have. One PDF
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
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #7 from Aaron Williams ---
./baloo-checkdb.py
Loading DB from /home/aaronw/.local/share/baloo/index...
Traceback (most recent call last):
File "/fast2/aaronw/programming/kde/./baloo-checkdb.py", line 265, in
db.check()
File
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to Aaron Williams from comment #2)
> ... hence I use XFS.
It might still be worth the "sanity check" of running, for a file you know has
been indexed:
baloosearch -i filename:the-file-name
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #5 from Aaron Williams ---
balooctl indexSize
File Size: 8.18 GiB
Used: 3.94 GiB
PostingDB: 1.12 GiB28.433 %
PositionDB: 1.91 GiB48.445 %
DocTerms: 641.15 MiB15.887 %
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #4 from Aaron Williams ---
While I had been seeing these periodic failures earlier, something definitely
got goofed up.
balooctl status
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid:
"Unknown" msgid_plural: ""
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #3 from Aaron Williams ---
I might add that I do not think it is memory constrained. The system this is
running on has 128GiB of RAM and significant swap. I do not see baloo consuming
excessive memory, though the index file is a bit over 60
https://bugs.kde.org/show_bug.cgi?id=467865
--- Comment #2 from Aaron Williams ---
I am not running BTRFS. I've had too many bad experiences with it and lost too
many BTRF filesystems in the past to trust it, plus it has this habit of
suddenly going out to lunch to do some processing. I have
https://bugs.kde.org/show_bug.cgi?id=467865
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
13 matches
Mail list logo
