Hi Quanah,
Yes, indeed. I've used the ./mdb_copy -v <source> <destination> to get the copy of the database. It has created 227MB file, which I've copied over to the ldap data folder and replaced the original 80GB file.
Cheers
----- Original Message -----
From: "Quanah Gibson-Mount" quanah@symas.com To: "Andrei Mikhailovsky" andrei@arhont.com, "Howard Chu" hyc@symas.com Cc: "openldap-technical" openldap-technical@openldap.org Sent: Thursday, 14 February, 2019 01:04:26 Subject: Re: help with mdb database recovery after crash
--On Wednesday, February 13, 2019 6:37 PM +0000 Andrei Mikhailovsky andrei@arhont.com wrote:
Hi Howard,
You could try using the preceding transaction and see if it's in any better shape. The code for this is not released in LMDB 0.9. You can compile the mdb.master branch in git to obtain it. Then use the "-v" option with mdb_copy and see if that copy of the database is usable.
I have compiled liblmdb using the mdb.master branch and used the mdb_copy as you've suggested. It didn't produce any errors. However, when I copy the data.mdb back to the Zimbra server it still produces the same error:
Did you use mdb_copy with the -v flag as Howard noted? It is helpful to be precise about exactly what steps you took.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com