-
Notifications
You must be signed in to change notification settings - Fork 874
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
cannot acquire lock: Lock FcntlFlock of {location}/.ipfs/repo.lock failed: operation not supported #1507
Comments
Thank you for providing such a detailed issue. My first suspection is related to permissions. Can you please tell me what are the read & write permissions you have set up for your NAS mount? |
I suspect the problem may be due to the protocol used for mounting NAS on macOS. Drobo docs suggest they can use AFP or SMB
|
Full admin permissions.
… On 2020 May 18, at 03:23 , Rafael Ramalho ***@***.***> wrote:
Thank you for providing such a detailed issue.
My first suspection is related to permissions. Can you please tell me what are the read & write permissions you have set up for your NAS mount?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1507 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTYUQRY7L2CD6GPCTDEOZLRSD5AHANCNFSM4NCVMFJA>.
|
Default connection is SMB.
… On 2020 May 18, at 05:12 , Marcin Rataj ***@***.***> wrote:
I suspect the problem may be due to the protocol used for mounting NAS on macOS.
Drobo docs <https://supportportal.drobo.com/retrieve/s3/knowledge/AA/AA-01304.html> suggest they can use AFP or SMB
First step is to figure out which one is used – @EricLScace <https://github.com/EricLScace> do you know?
Then, look for protocol-specific fix for file locking (I am not familiar, just guessing)
perhaps locks are held per app (AFP?) and can be cleared by a dedicated command etc
it is also possible the protocol/ipfs-desktop combo does not support locking, then the only option is to manually move repo location back and update ipfsConfig / path in config.json
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1507 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTYUQUEALTLSZYBRWGLIOTRSEJYFANCNFSM4NCVMFJA>.
|
Yup, having the same issue, also with the repo being on a SMB share. I can read, create, delete, remove and files all fine, the permissions are all correct - is there something else that |
@tmladek - as some core team members are away for winter holidays, I'd suggest checking and/or asking in the forums at discuss.ipfs.io to see if other folks in the larger community using NAS have experienced similar, or solved. Thanks! |
A discussion about this problem has been started here: https://discuss.ipfs.io/t/error-cannot-acquire-lock-lock-fcntlflock-of-path-to-repo-repo-lock-failed-operation-not-supported/10620/3 This is not an ipfs-desktop issue per se, and it has yet another duplicate here: ipfs/kubo#8005. Thus, closing. |
Describe the bug
Fails at startup. Fails again when restart attempted.
To Reproduce
0. Install clean version. Works fine with IPFS volume mounted on local storage.
Move volume to a NAS, using the utility within IPFS Desktop. In my case, it's a Drobo 5N2 share. A .ipfs folder is viewable in the share after the IPFS volume move was performed.
IPFS restarts but immediately errors out. Error.log attached.
error.log
Note: At this point the volume cannot be moved back to its original location.
Expected behavior
Expected
Screenshots
![image](https://user-images.githubusercontent.com/6785602/82105545-1c97c700-96d9-11ea-8475-8ecee9edd4a7.png)
Additional context
config.json contains:
The
path
is correct.CLI command
ipfs config show
returns:There is no
Datastore.Path
entry, although some documentation suggests there should be one. I don't know if that's relevant/helpful.The text was updated successfully, but these errors were encountered: