Skip to content

Zarr backend - lmdb default size 1TB sparce #9

Description

@owilinux

Following Problem: the data.mdb files are sparce with file size 1TB - this causes a lot of troubles when backuping data - rsync fails to recognise the sparce file type and reads 1TB to transfer, other file related tools show 1TB as real filesize - this is causing a lot of problems along the way - most software tools using lmdb files had to patch this problem later on. (see e.g. caffe BVLC/caffe#3731)

please consider to fix this by using lmdb.open with writemap=True this avoids the wrong super large 1TB filesize for this normally small files. or limit map_size to much less than 1TB (see https://www.programcreek.com/python/example/106501/lmdb.open example 6)

regards
oliver

Activity

  1. owilinux commented on Jun 1, 2023

    @owilinux
    MemberAuthor

    this fails also on 32bit Windows machines - not large enough address space...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions