Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zarr backend - lmdb default size 1TB sparce #9

Open
owilinux opened this issue Jun 1, 2023 · 1 comment
Open

Zarr backend - lmdb default size 1TB sparce #9

owilinux opened this issue Jun 1, 2023 · 1 comment

Comments

@owilinux
Copy link
Member

owilinux commented Jun 1, 2023

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

@owilinux
Copy link
Member Author

owilinux commented Jun 1, 2023

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant