Bug 384209 - Confusing error message when mmap() fails
Summary: Confusing error message when mmap() fails
Status: RESOLVED INTENTIONAL
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.37.0
Platform: Debian unstable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-31 07:26 UTC by Marc Mezzarobba
Modified: 2018-11-09 11:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Mezzarobba 2017-08-31 07:26:08 UTC 
It would be nice it the following could give a more helpful error:

$ ulimit -Sv $((6*1024*1024))
$ balooctl enable
Failed to create database, removing corrupted database.
Failed to create database after deleting corrupted one.

(Probably related to bug 364042.)
Comment 1 Stefan Brüns 2018-10-29 19:48:01 UTC 
Why are you limiting the address range? baloo needs sufficient address space to mmap the db.
Comment 2 Marc Mezzarobba 2018-10-31 09:17:50 UTC 
It wasn't intentional. Baloo was failing to start, and it took me a while to understand what was going on. It is a minor point in any case.
Comment 3 Christoph Feck 2018-11-09 11:11:01 UTC 
Changing baloo not to use the mmap-based LMDB would entail a complete rewrite, which is not planned at this moment.