openldap-bugs May 2026

openldap-bugs@openldap.org

1 participants
84 discussions

[Issue 9619] New: mdb_env_copy2 with MDB_CP_COMPACT in mdb.master3 produces corrupt mdb file
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=9619 Issue ID: 9619 Summary: mdb_env_copy2 with MDB_CP_COMPACT in mdb.master3 produces corrupt mdb file Product: LMDB Version: 0.9.29 Hardware: All OS: Windows Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: kriszyp(a)gmail.com Target Milestone: --- When copying an LMDB database with mdb_env_copy2 with the MDB_CP_COMPACT with mdb.master3, the resulting mdb file seems to be corrupt and when using it in LMDB, I get segmentation faults. Copying without the compacting flag seems to work fine. I apologize, I know this is not a very good issue report, as I haven't had a chance to actually narrow this down to a more reproducible/isolated case, or look for how to patch. I thought I would report in case there are any ideas on what could cause this. The segmentation faults always seem to be memory write faults (as opposed to try fault on trying to read). Or perhaps the current backup/copying functionality is eventually going to be replaced by incremental backup/copying anyway (https://twitter.com/hyc_symas/status/1315651814096875520). I'll try to update this if I get a chance to investigate more, but otherwise feel free to ignore/consider low-priority since the work around is easy. -- You are receiving this mail because: You are on the CC list for the issue.

1 12

[Issue 9291] New: Detection of corrupted database files
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=9291 Issue ID: 9291 Summary: Detection of corrupted database files Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: markus(a)objectbox.io Target Milestone: --- Let's assume we have to deal with a corrupted database for whatever reason (e.g. broken hardware or file system). Current behavior seems to be mostly undefined, which is understandable as it's not known what is broken (e.g. there are no checksums). For example, I'm seeing a SIGBUS in mdb_page_touch because the cursor's top page (mp) is pointing to invalid memory (0x7f99cf004000) during a commit: mdb_page_touch mdb.c:2772 mdb_page_search mdb.c:6595 mdb_freelist_save mdb.c:3575 mdb_txn_commit mdb.c:4060 Cursor data at that point: mc_snum = 1, mc_top = 0; myki[0] = 0 A SIGBUS is troublesome as it crashes the process, and I wonder if there are other ways to detect such inconsistencies. If that be possible there could be user-specific handling in place. E.g. a user might start a new database file. This issue was reported by our users, which also provided DB files: https://github.com/objectbox/objectbox-java/issues/859 I did not find a lot of consistency checks besides MDB_PAGE_NOTFOUND and MDB_CORRUPTED. Also, I think there's no current way to thoroughly check a DB file (e.g. like fsck for the DB file)? My first idea other than checksums was to walk through the branch pages from the root and check if the referenced pages are within reasonable bounds. Also check the page content (e.g. nodes, flags). Additionally (optionally?), it should be possible to check that the key values are actually sorted. So, it boils down to 3 points in summary: 1.) If there no way to check the DB file for consistency yet(?), which approach do you think would make sense? There might be two modes; one for a through check through all data, and a quick check that does not take long and could be e.g. done when opening the DB. Goal is to avoid process crashes and let users handle the situation. 2.) In general, is it possible to add more consistency checks in regular DB operations? 3.) Could the the particular situation (for which I provided the stack trace) detected (e.g. is myki[0] = 0 legal here?) I'd be happy to provide a patch if you provide some direction where you want to take that. -- You are receiving this mail because: You are on the CC list for the issue.

1 27

[Issue 8335] MDB_MULTIPLE issues
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8335 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |0.9.36 Assignee|bugs(a)openldap.org |hyc(a)openldap.org --- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.RE/0.9: • 8029fc6f by Howard Chu at 2026-04-27T18:44:21+01:00 ITS#8335 LMDB: reject MDB_MULTIPLE put with 0 items mdb.master: • 6888aa47 by Howard Chu at 2026-04-27T18:43:52+01:00 ITS#8335 LMDB: reject MDB_MULTIPLE put with 0 items mdb.master3: • 0ff5b99e by Howard Chu at 2026-04-27T18:42:49+01:00 ITS#8335 LMDB: reject MDB_MULTIPLE put with 0 items -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9388] New: mdb_stat for DupSort DBI shows incorrect data
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=9388 Issue ID: 9388 Summary: mdb_stat for DupSort DBI shows incorrect data Product: LMDB Version: 0.9.26 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: AskAlexSharov(a)gmail.com Target Milestone: --- It doesn't include pages pages used for values. -- You are receiving this mail because: You are on the CC list for the issue.

1 3

[Issue 10454] New: O_DSYNC is busted on macos
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=10454 Issue ID: 10454 Summary: O_DSYNC is busted on macos Product: LMDB Version: unspecified Hardware: All OS: Mac OS Status: UNCONFIRMED Keywords: needs_review Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: pyry.kovanen(a)gmail.com Target Milestone: --- LMDB relies on O_DSYNC for writing the meta page, unfortunately it doesn't work on macos. Previous discovery by the tigerbeetle guys: https://github.com/tigerbeetle/viewstamped-replication-made-famous#leaderbo…, some more context at https://x.com/jorandirkgreef/status/1532314169604726784. I discovered this during benchmarking and was wondering why lmdb writes were twice as fast as macos as on linux. -- You are receiving this mail because: You are on the CC list for the issue.

1 7

[Issue 7772] liblmdb sub-page growth when adding existing data
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=7772 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs(a)openldap.org |hyc(a)openldap.org Target Milestone|--- |0.9.36 --- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.master: • 143ce300 by Howard Chu at 2026-04-27T15:02:14+01:00 ITS#7772 LMDB: fix sub-page growth mdb.RE/0.9: • 510aa4b8 by Howard Chu at 2026-04-27T15:02:25+01:00 ITS#7772 LMDB: fix sub-page growth mdb.master3: • 134e5ace by Howard Chu at 2026-04-27T14:59:00+01:00 ITS#7772 LMDB: fix sub-page growth -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8803] [PATCH] Add -L option for using external locking
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8803 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.0.0 Assignee|bugs(a)openldap.org |hyc(a)openldap.org --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.master3: • 7a1f36d5 by Nir Soffer at 2026-04-24T20:19:46+01:00 ITS#8803 LMDB: add tool option to disable locking -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8192] liblmdb confuses Windows error code with errno values
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8192 --- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.master3: • ba6e0018 by Howard Chu at 2026-04-24T18:07:42+01:00 ITS#8192 fix prev commit -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8192] liblmdb confuses Windows error code with errno values
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8192 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.0.0 Assignee|bugs(a)openldap.org |hyc(a)openldap.org --- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.master3: • bf5c4e0f by Howard Chu at 2026-04-24T16:05:40+01:00 ITS#8192 LMDB: define new error codes to avoid errno abuse -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8579] LMDB: me_fd should be O_CLOEXEC on POSIX systems
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8579 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs(a)openldap.org |hyc(a)openldap.org --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb.master3: • cf52db2b by Howard Chu at 2026-04-23T18:55:06+01:00 ITS#8579 LMDB: all descriptors should have O_CLOEXEC -- You are receiving this mail because: You are on the CC list for the issue.

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs May 2026