Hi Michael, We have been informed about this issue by Arch Linux. There are two steps that must be done: 1. Adjust Knot to be able to work with new LMDB. This patch seems to solve it https://gitlab.nic.cz/knot/knot-dns/-/commit/e39ad2a6071966084ebf1a9e539378ce83ffc59b 2. Convert LMDB databases from version 0.9.x to 1.x. This step is more challenging and will require some work to be seamless, as you need old LMDB for database export and new LMDB for database import :( I have a plan, though. For distributions it might be better to provide LMDB 1.x as a different packages for migration reasons.
Stay tuned! Daniel On 7/4/26 17:32, Michael Grimm via knot-dns-users wrote:
Hi, I do want to point out: http://www.lmdb.tech/doc/upgrading.html tl;dr dump your databases *before* upgrading. I got bitten by this on FreeBSD and had had to fall back to lmdb 0.93.5 Has anyone succeeded in this migration your knot databases to lmdb 1.0? Which knot databases are involved? (journal, timers, kasp, …?) Thanks and regards, Michael --
--
