good evening;
On 2020-05-29, at 20:19:02, Howard Chu hyc@symas.com wrote:
James Anderson wrote:
good evening;
i am looking for an explanation for a situation which we encountered with an lmdb database and library version is 0.9.17-3. the database's condition was such that all attempts to open it for reading failed. in at least some cases the error appears to have occurred during the operation which looked for stale leaders. a problem was also evident when attempting to copy the database:
@nl12:~# mdb_copy /srv/dydra/catalog/repositories/d2141030-9495-c040-b1a7-9e19edbeb491/ /srv/dydra/backups/public-data__rev mdb_copy: copying failed, error 131 (State not recoverable)
131 is not an LMDB error code. Most likely your underlying storage system failed.
which would mean, where that storage system is zfs, i should turn to it. ok.
is there anything to be said, independent of that, about the other two questions?
best regards, from berlin,
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/