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

Error when calling lmdb.open() #100

Closed
piergiaj opened this issue Oct 4, 2015 · 7 comments
Closed

Error when calling lmdb.open() #100

piergiaj opened this issue Oct 4, 2015 · 7 comments

Comments

@piergiaj
Copy link

piergiaj commented Oct 4, 2015

Whenever I call open, whatever string I pass in as the path, it gives the following error:

lmdb.open('trainingData')
Traceback (most recent call last):
File "", line 1, in
lmdb.Error: trainingData: Function not implemented

The error line always matches the string I pass in. The folder is created and a lock file is created, but I always get this error. Any ideas how to fix this?

@dw
Copy link
Collaborator

dw commented Oct 4, 2015

Hi there. What OS and filesystem are you using?

@piergiaj
Copy link
Author

piergiaj commented Oct 4, 2015

OS: Linux 3.0.101-0.31.1_1.0502.8394-cray_gem_c

File system is dvs

@dw
Copy link
Collaborator

dw commented Oct 4, 2015

Hi again,

I'm going to guess there's a 90% chance dvs doesn't support mmap, but in order to confirm this, can you upload a gist containing the output of strace -s 100 python your/script.py. If it is mmap, then we can't support LMDB on that filesystem, however if it's another system call returning the error, it might be possible to work around it

@hyc
Copy link

hyc commented Oct 4, 2015

The Cray documentation confirms, they only support read-only mmap on DVS. http://docs.cray.com/books/S-0005-5204/ page 39 caveats.

@dw dw closed this as completed Oct 4, 2015
@dw
Copy link
Collaborator

dw commented Oct 4, 2015

Hi there,

hbf suggests you might be fine running with writemap=False, since DVS supports read-only mmaps, however be aware that this still does not allow opening the database from multiple nodes in your cluster, as DVS does not provide any coherency between the in-memory database file and its current representation on disk, and even if it did, LMDB does not support any kind of locking that would work in this scenario.

@amaeme
Copy link

amaeme commented May 13, 2017

sbatch --gres=gpu:1 tr.sh
Where tr.sh is my test script

@aiyulu
Copy link

aiyulu commented Jun 1, 2020

I have met the same problem, which caused by system lock, like notebook cpfs_data folder has system lock, but nas_data folder has not.

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

5 participants