> You'll have to be more specific (commit ID). And understand that since
you're running a dev branch, it's likely to be unstable at various points.
# git log  

commit 52bc29ee2efccf09c650598635cd42a50b6ecffe       
Author: Howard Chu <[email protected]>                 
Date:   Thu Feb 11 11:34:57 2021 +0000                
                                                      
    ITS#9461 fix typo                                 
                                                      
I repeated the same mdb_stat -a operation on a different Ubuntu system on
the same database file (copied the uncompactified data.mdb there, then
removed Free pages with mdb_copy -c ), using its stock lmdb-tools that I
installed with apt install lmdb-tools, but got the same Segmentation fault:

alecm@bigram:/fusionio1/lmdb/db.0.2.1$ mdb_copy -c
/fusionio1/lmdb/db.0.2.1/dbgraph/vx_to_edg_to_compress
/fusionio1/lmdb/db.0.2.1/dbgraph/vx_to_edg
alecm@bigram:/fusionio1/lmdb/db.0.2.1$ mdb_stat -fear
/fusionio1/lmdb/db.0.2.1/dbgraph/vx_to_edg

Environment Info

  Map address: (nil)

  Map size: 1200000000000

  Page size: 4096

  Max pages: 292968750

  Number of pages used: 11577185

  Last transaction ID: 1

  Max readers: 126

  Number of readers used: 0

Reader Table Status

(no active readers)

Freelist Status

  Tree depth: 0

  Branch pages: 0

  Leaf pages: 0

  Overflow pages: 0

  Entries: 0

  Free pages: 0

Status of Main DB

  Tree depth: 1

  Branch pages: 0

  Leaf pages: 1

  Overflow pages: 0

  Entries: 1

Segmentation fault (core dumped)  
 

# mdb_stat -V

LMDB 0.9.21: (June 1, 2017)


# apt install lmdb-utils

Reading package lists... Done

Building dependency tree

Reading state information... Done

lmdb-utils is already the newest version (0.9.21-1ubuntu0.1).

Ubuntu 18.04.3 LTS 
Linux bigram 4.15.0-91-generic
Ext4 fs 

-----Original Message-----
From: Howard Chu [mailto:[email protected]] 
Sent: Monday, March 15, 2021 6:00 AM
To: Alec Matusis <[email protected]>; [email protected]
Subject: Re: Segmentation fault from mdb_stat -a after successful mdb_copy
-c

Alec Matusis wrote:
> I have an environment with one database:

> #mdb_copy -V
> 
> LMDB 0.9.70: (December 19, 2015)

This is not an actual LMDB version, it's the generic number assigned to the
mdb.master development branch.
You'll have to be more specific (commit ID). And understand that since
you're running a dev branch, it's likely to be unstable at various points.
> 
> Linux db0 3.13.0-95-generic
> 
> XFS filesystem
> 
>  
> 


--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Reply via email to