When I run the ipfs in windows Command line console with the ipfs cat peers command, an api is not running echo to me;
Then I try to use the command ipfs daemon to start a long run daemon process, Error comes again, showing that can't acquire lock: file "C'\Users\MyPC\.ipfs\repo.lock" already locked.
What happened in this process?
I check the root dirctory of the .ifps, and find that there are a repo file and a repo.lock file there. I open both file with notepad++, which shows me someting like that"{OwnerPID:11xxx}".
PS: What I installed on my PC is the go-ipfs v0.4.8. My PC OS is win7 Ultimate x64.
The text was updated successfully, but these errors were encountered:
When you see the message repo.lock is already locked, you should run ipfs repo fsck after making sure the repo is not in use.
On Windows there seems to be an issue, where sometimes the lock is not released after an IPFS command finishes, but this will not happen if the ipfs daemon is running.
jeddah-liu commentedApr 14, 2017
When I run the ipfs in windows Command line console with the ipfs cat peers command, an api is not running echo to me;
Then I try to use the command ipfs daemon to start a long run daemon process, Error comes again, showing that can't acquire lock: file "C'\Users\MyPC\.ipfs\repo.lock" already locked.
What happened in this process?
I check the root dirctory of the .ifps, and find that there are a repo file and a repo.lock file there. I open both file with notepad++, which shows me someting like that"{OwnerPID:11xxx}".
PS: What I installed on my PC is the go-ipfs v0.4.8. My PC OS is win7 Ultimate x64.
The text was updated successfully, but these errors were encountered: